Lordi
Published
Works just fine
Do not enable FSR 3 Frame Generation right now, it will crash the game. If you enabled it and disabled the launcher, you can use the launch option "-launcher" at the end to start it.
gamemoderun RADV_PERFTEST=gpl %command%
Game runs very well, I just added RADV_PERFTEST=gpl to get rid of some very minor stuttering, but with lower-end hardware, it might help a bit more. If you are using a newer PlayStation Controller, remember to disable Steam Input for better controller rumble
RADV_PERFTEST=rt,gpl gamemoderun %command%
The game is poorly optimized as of right now but this is in no way the fault of wine/proton
Proton 8.0-1 as well as GE-55 had the EA Launcher crashing non-stop but are probably able to run the game just as well. AMDVLK gave me horrible performance as well as longer shader compile times.
Using Mesa as well as my launch options I was able to get a stable 50-70 fps in the first level. Raytracing did not work, at least performance did not decrease at all and visuals were exactly the same. For anyone experiencing low performance as well as low hardware utilization, take a look at https://github.com/doitsujin/dxvk/issues/2938. TL;DR: add split_lock_detect=off to your /etc/default/grub/ in the line with GRUB_CMDLINE_LINUX_DEFAULT
AMD_VULKAN_ICD=RADV RADV_DEBUG=nodcc %command%
I had to disable SteamVR home in order to get the game to launch, because otherwise I would just get stuck in the loading area without being able to play. It can be disabled by clicking on the top of the SteamVR popup -> Settings -> General -> SteamVR Home and then set it to "off".
I recommend trying to run this on Xorg first because for me, using sway, it did not start in the VR headset but rather just as a window on the desktop.
PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command% -nomovies
The game usually runs fine, as long as you get it to actually start. I just swap through the newest stable Proton, Proton Experimental, and GE and one usually makes it work.
I enabled esync in /etc/security/limits.conf and that fixed the multiplayer for me (unmodded), I will try with the unification mod.
If you want to use the unification mod, just move the four parts into ~/.local/share/Steam/steamapps/common/Dawn\ of\ War\ Soulstorm/, then copy and paste the following commands
cd ~/.local/share/Steam/steamapps/common/Dawn\ of\ War\ Soulstorm/
mv Soulstorm.exe Soulstorm.exe.bac
mv Unification-v6.9.0-Full.exe Soulstorm.exe # or whatever version you use
Now run the game once, and install the mod. Then run:
cd ~/.local/share/Steam/steamapps/common/Dawn\ of\ War\ Soulstorm/
mv DoW_Mod_Manager_v2.3.1.0.exe Soulstorm.exe # Version may change, so look what is there
start the game again The mod manager should start right up, then
cd ~/.local/share/Steam/steamapps/common/Dawn\ of\ War\ Soulstorm/
mv Soulstorm.exe DowModManager.exe
mv Soulstorm.exe.bac Soulstorm.exe
and now you can enable laa and play with the unification mod on Linux! To start the mod manager again, simply do
cd ~/.local/share/Steam/steamapps/common/Dawn\ of\ War\ Soulstorm/
mv Soulstorm.exe Soulstorm.exe.bac
mv DowModManager.exe Soulstorm.exe
and once you started it, repeat the 3rd code block There is probably a better way to do this, but you can just put these comnmand into a script and just run that.
