Azdalen
Published
with my tweaks force-enabling / optimizing FSR 3.1+ I had smooth 60-120+ fps (non-ray-traced) less with ray-tracing enabled.
RADV_PERFTEST=localbos STAGING_SHARED_MEMORY=1 mangohud gamemoderun %command%
Add the following to the game's SteamLibrary/steamapps/compatdata/2457220/pfx/drive_c/users/steamuser/AppData/Local/Alabama/Saved/Config/Windows/Engine.ini file:
[SystemSettings]
r.FidelityFX.FSR3.Enabled=1
r.FidelityFX.FSR3.UseNativeDX12=1
r.FidelityFX.FSR3.QualityMode=2
r.FidelityFX.FI.Enabled=1
r.FidelityFX.FI.OverrideSwapChainDX12=1
r.FidelityFX.FI.AllowAsyncWorkloads=1
1st 3 force FSR3 on, and force it to use DX12 backend (which is most performant for FSR) and used a balanced quality preset (good balance). Last 3 force enable Frame Interpolation (generated frames), and tell it do do it in a very performant way given the 1st 3 settings. Additional settings can be found on AMD's GPUOpen site for UE5: https://gpuopen.com/learn/ue-fsr3/
Ray Tracing is sub-optimal (due to AMD hardware), especially with reflections, which would sometimes cause jet black faces or a kalediscope of bright colors on all water surfaces.
Use my tweaks, DON'T use Proton-GE-25 or older, as they are out of date for this game and your performance WILL be sub-par. Use Proton-Experimental. Additionally, if available for you, definitely use an LQX (Liquorix) or TKG kernel to get proper gaming optimizations and the PDS scheduler; others tend to not be as good in feeding graphics cards, easy 10-30fps boost in many games. Additionally, via testing, i've found only the Mesa3D env-vars RADV_PERFTEST=localbos flag to be worth using (with my hardware/setup), using others typically will reduce quality and/or performance (sometimes significantly). My mangohud config is setup to hard cap at 120fps w/ early mailbox frame limiting. This generally keeps things -very- smooth for me. Otherwise I have everything set to max in game, and ray-tracing OFF (its just not worth the perf cost), maybe with RDN4, it will be better in the future.
game was buttery smooth with GloriousEggroll's Proton 5.21. I suspect it should also work with normal non-GE 5.13 too
Proton-5.21-GE-1
use PULSE_LATENCY_MSEC=30 to get rid of crackling
So long as you turn off high res textures and run it under X and Proton 9+ it works quite well and remains stable.
The game appears to have issues with the high-resolution texture pack. Occasionally it will fail to load them, and they will appear black. Turning it off, resolves the issue. Turning them back on will typically crash the game, though not always.
While fullscreen works, attempting to ALT-TAB out, will crash the game
The game appears to have issues with the high-resolution texture pack. If they are enabled, loading will occasionally cause the game to crash. Turning them off appears to fix this issue.
Due to the changes with EA changing from Origin to the EA App, the game will not properly launch unless you run it from steam under X11 and utilize Proton 8 or higher (9 or Experimental recommended). Wayland causes EA App to fail to launch, every time. Steam Deck may be the only acception to the Wayland issue however. Additionally, if running under NixOS' native steam package, regardless of the above, the game will not launch, but would under Flatpak steam (I suspect a FHS related issues somewhere).
DO NOT RUN UNDER WAYLAND. Additionally, due to the way the EA App launches the game, you cannot utilize gamemode, gamescope, or any env vars to improve performance (at least with NixOS). Running steam itself under gamescope may work in some instances, but not on NixOS due to Wayland (I suspect there is some missing env var or library). Had to run under Flatpak steam.
had to use PROTON_USE_D9VK=1 %command% to get some keybinds to register
Fantastic buttery smooth performance with my customizations, significantly better performance than on Windows.
AMD_VULKAN_ICD=RADV PROTON_NO_ESYNC=1 WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_STRENGTH=0.2 RADV_PERFTEST=nggc mesa_glthread=true gamemoderun %command%
you need to tell steam to use the "gamepad" configuration for desktop controller settings
I experienced significant freeze-stuttering until i started using a customized TKG-PDS kernel
use TKG-PDS 5.16+, (adjust the customization.cfg for PDS and other appropriate features for your system) and GE-Proton7-14+. Have a NVME drive, and use IO-Scheduler of "none" for max throughput (it was noticeably slower/stuttery with BFQ/deadline-mq). CPU governor set to use "performance" via gamemode as well as re-nice-ing to 10. Use my supplied launcher string too (assuming you're using AMD). no idea if its playable w/ intel or nvidia 🤣
Note: since the game uses DX12, DXVK settings like DXVY-ASYNC or DXVK_FRAME_RATE won't have an effect. Force-disabled esync to ensure it chose to use fsync (which i think it does automagicaly, but wanted to be sure 🤷♀️)
NOSTEAM=1 RADV_FORCE_VRS_CONFIG_FILE=~/.config/vrs.conf STAGING_SHARED_MEMORY=1 RADV_PERFTEST=gpl,nv_ms,dccmsaa,nggc,cpwave32,gewave32,pswave32,rt,rtwave64,sam AMD_VULKAN_ICD=RADV DXVK_FRAME_RATE=164 DXVK_ASYNC=1 mesa_glthread=true gamescope -h 1080 -H 1440 -U --sharpness 10 -r 100 gamemoderun mangohud %command%
works flawlessly, including store
while it works well on its own, I do recommend trying some of the settings i've launched with, especially gamescope as it will greatly improve performance and makes FSR far simpler to use than GE proton since the engine is a bit old and doesn't perform some modern techniques as well as contemporaries. If you are a returning player, and are using GE proton, definitely use NOSTEAM=1 before %commands% in your launch commands, otherwise use -provider Portalafter%commands%` to get the non-steam account login
PROTON_NO_ESYNC=1 RADV_PERFTEST=gpl,sam,nggc,dccmsaa STAGING_SHARED_MEMORY=1 STAGING_WRITE_COPY=1 mangohud gamemoderun %command%
As of Oct 21st 2023, Proton Experimental is still unstable with this game, even with developer recommendations, but GE-Proton8-20 appears to be quite stable
Mangohud v0.7.0-2, gamemode v1.7-1 used. ensures system is put into perf mode for games as well as gives me details about perf during runtime :D
PROTON_NO_ESYNC is to ensure ESYNC is disabled, it should auto-detect, but this forces it since I also use a custom kernel and am not 100% certain
RADV_PERFTEST params only work with AMD cards, gpl reduces shader compiulation stutter, sam enables shared access memory (gpu can access system memory if needed), nggc is next gen geometry culling (recently was re-enabled in mesa), dccmsaa is a MSAA optimization which -may- (or maybe not) work with FSR/TSAA. NOTE: a deve comment in the patch notes seemed to indicate *wave32 options are unstable, so do not use the *wave32 settings (e.g., cswave32, pswave32, gewave32, etc.).
STAGING_SHARED_MEMORY enables memory sharing optimizations
does not appear to work with gamescope at present
also works under steam deck with same settings, runs 40-60 fps depending on area, i usually soft-cap it to 30fps for battery life, noise reduction, and stable framerate.
gamemoderun env MANGOHUD=1 STAGING_SHARED_MEMORY=1 RADV_PERFTEST=gpl,sam,dccmsaa,bolist,localbos,cswave32,gewave32,pswave32 %command% -ignore-windows-system-certs
game will install and load just fine, but will not get past login to steam unless you add -ignore-windows-system-certs after the %command% section of the launch options.
Game would not launch. Also tried Proton Experimental and GE-Proton7-37
borked.
