Mair
Published
PROTON_USE_WINED3D=1 %command%
I couldn't get the game to run without the launch command "PROTON_USE_WINED3D=1 %command%"
other than that it's completely fine
In menus in fullscreen, sometimes the mouse cursor on screen does not reflect where it is actually positioned. Normally this isn't a huge issue.
Often once per match you experience 5 seconds or so of sub 10 fps, but it passes and returns to a high, stable framerate. Others have reported this also
Works great aside from the previously mentioned issues. Frame rates are high and stable.
good ootb
its fine of the standard proton version that steam provides. Some people report issues and these are generally solved by switching to proton experimental.
DXVK_ASYNC=1 PROTON_USE_WINED3D=1 PROTON_NO_ESYNC=1 PROTON_LOG=1 %command%
Without the supplied launch options, the game would freeze often
Download and launch this as a non-steam game: https://github.com/AgentRev/CoD-FoV-Changers/releases
it will let you alter the FOV in game
PROTON_USE_WINED3D=1 %command%
works online with friends well
use PROTON_USE_WINED3D=1 %command% to get the game working
just works on anything but arch. see previous report if arch user
eval $(echo "%command%" | sed 's/Chivalry2Launcher.exe/TBL\/Binaries\/Win64\/Chivalry2-Win64-Shipping.exe/') --gamemoderun %command% -dx11
use the launch options above with the steam default proton option (in my case, 8-0-3)
just works natively on Arch
performance is lackluster compared to windows: I reccomend running on all low
who up rockin they stone
I crash once every 5 games or so, I haven't been able to find a fix for this.
gamescope -W 2560 -H 1440 -r 60 -- %command%
use gamescope to launch this game and it works fine. I think it's a DRM problem
if you aren't familair with gamescope, use this guide here: https://wiki.archlinux.org/title/Gamescope
Only works in borderless windowed with a white border around the screen
Needs no additional launch options other than using 8-32 GE
Works with either proton experimental or proton 9.0 beta for me with no other options. 8.0-5 also works, though will result in crashes.
gamemoderun mangohud %command%
The game will slow to sub-30fps if you change any settings. This is only fixed by closing the game and launching it again
Has got better over time, but you might crash every now and again. Seems to be a problem on Windows too.
I'd avoid using Proton GE for now, as it's currently less up-to-date than proton experimental for this game.
works now with proton experimental or the latest GE-Proton without any special launch options.
gamemoderun mangohud %command%
either select proton experimental or download Proton GE and do the same. no need for the --use-d3d11 flag anymore, at least for me
needs specific launch options and BIOS settings alterations to work on 14th gen intel CPUs
MESA_SHADER_CACHE_DISABLE=true mangohud gamemoderun %command% --use-d3d11
the game stutters slightly with an uncapped framerate in d3d11 mode
without BIOS changes on 14th gen intel and the launch options listed; my entire system would hard crash
if you have an intel 13th or 14th gen CPU, follow this: https://www.reddit.com/r/Helldivers/comments/1aqvokt/comment/kqsnurf/. If it crashes occascionally and freezes your computer or forces a restart. Change your CPU Vcore Loadline calibration in BIOS. It hates automatic settings and needs to be set as 'normal' or 'medium' depending on what BIOS you're using. My BIOS is an MSI one that runs from 1-8 instead of having named levels: I just set it to 8 and it seems to work fine.
I had pretty constant hardcrashes for my whole system without the -- use-d3d11 flag, but I had significant performance problems without the MESA_SHADER_CACHE_DISABLE=true flag in addition.
on an RX 7000 system Plasma 6 wayland, you must use D3D11 with gamescope for good performance
gamescope -h 1080 -H 1440 -F fsr -f --force-grab-cursor --mouse-sensitivity 1 -- mangohud %command% --use-d3d11
wouldn't accept mouse input without specific gamescope flags
if you change any settings the game will go to sub-10 fps and peg the GPU at 100% utilisation
this game has some massive problems on KDE wayland and RX 7000
you must use the --use-d3d11 flag in conjection with gamescope or you'll experience either full GPU driver crash, requiring a system reload, or terrible performance.
even with all this, if you change a setting the game will run unplayably slow and you'll need to restart the game
this SHOULD be the last of the many reports I've left for this game. I've absolutely went through the wringer over weeks trying to find these solutions.
Has weird issues on RX 7000 series RDNA 3 cards. I recently swapped to RDNA2 and have been having no issues
white border around the window, not intrusive.
proton experimental allows your mic to work, other than that it should just function for everyone but RDNA 3 users
all versions of proton other than proton GE 8-6 would result in frequent crashes
you must use proton 8-6 to avoid constant crashes in this game. you'll still see the occasional crash regardless, but I think thats mostly the game's fault and would happen on windows as well
PROTON_USE_WINED3D=1 %command%
missing textures and cutscenes not loading (a white or black screen in cutscenes)
use these launch options if you are having missing textures and cutscenes like me:
PROTON_USE_WINED3D=1 %command%
Use proton, the native version of the game does not run.
Use proton, as the native version of this game does not run. Otherwise, perfect experience.
run with the latest version of Proton GE in DX11 mode and it should run flawlessly
mangohud gamemoderun PROTON_LOG=1 RADV_PERFTEST=gpl %command%
works well on arch with Proton GE and the listed launch options
gamemoderun %command% -nojoy -nosteamcontroller -nohltv -particles 1 -precachefontchars
without launch options it runs badly in larger fights, even on modern hardware
you must enter these launch options or you'll had significant performance dips in large fights
now that the 64bit version of the game has been released; it just runs perfectly with no tweaks.
you can use some launch options for the sake of convenience, but they're really not necessary
NixOS requires dotnet-sdk package to run:
Exiting from the game whilst fullscreened would sometimes cause a full system crash. I just use windowed mode now. This might be a NixOs or PaperWM issue.
NixOS requires dotnet-sdk package to run:
--launcher-skip
opened launcher-configuration.json and changed fallback to DX11 from DX12
you must do three things to avoid frequent crashes:
first: go into launcher-configuration.json in the game directory and edit the line marked "fallback" to "dx11". DX12 is not stable.
second: search your steam library for and download "Proton Hotfix". then in the compaitibility dropdown in properties you select it instead of whatever version of proton you currently have selected.
third: go into the launch options and paste: "--launcher-skip". CDPR's launcher stopped working on linux recently and it simply wont boot if you dont do this.
additionally I found that my steam controller wouldnt work, but a standard xbox 360 controller would.
occasional crashes, but you can load back in
the game plays and performs equivilently to windows. slightly more crashes, but it also crashes on windows
textures sometimes load as their low LOD versions. annoying but does not impact gameplay
occasionally at the end of missions or in the character menu
gamescope --expose-wayland -f gamescope -W 2560 -H 1440 -r 165 -- %command%
on wayland you will have frequent crashes without gamescope
textures will often not load correctly
you need to use gamescope to play this on wayland without frequent hard crashes. see this arch wiki guide https://wiki.archlinux.org/title/Gamescope to configure it. gamescope is also availible through flatpak. I'd also reccomend setting it to fullscreen and lowering many of the settings.
I found that only proton 8-20 worked for me. other versions required shenanigains (see previous reports on this game) to work well
use proton 8.05 and make the config edit in this post to solve crashes and the model loading issues
gamemoderun %command%
https://github.com/ValveSoftware/Proton/issues/6573 Modify steamapps\common\Warhammer 40,000 DARKTIDE\bundle\application_settings\settings_common.ini change mesh settings on line 57 to disable true disable = true
without using the version of proton listed, I had frequent hard crashes with any other version. I think this is an RX 7000 series issue.
edit config file and include launch options for a good experience with RX7000 series GPUs
gamemoderun VKD3D_SHADER_CACHE_PATH=0 %command% PROTON_LOG=1 VKD3D_SHADER_CACHE_PATH=0
https://github.com/ValveSoftware/Proton/issues/6573 Modify steamapps\common\Warhammer 40,000 DARKTIDE\bundle\application_settings\settings_common.ini change mesh settings on line 57 to disable true disable = true
set textures to low and turn off screen space reflections
without disabling the vkd3d shader cache, the game will crash frequently on RX 7000 series GPUs
I think the game is having conflicts between it's internal shader cache and the VKd3d shader cache, so just disable it using the launch options.
make sure to edit the config file as described or you'll have texture loading issues
Either use the most recent GE proton or proton experimental: I think GE stutters slightly less.
also screen space reflections destroys performance so turn that off
has issues on RX 7000 RDNA 3 cards as per my previous reports. Works great on my current RDNA 2 card now though.
https://github.com/ValveSoftware/Proton/issues/6573 Modify steamapps\common\Warhammer 40,000 DARKTIDE\bundle\application_settings\settings_common.ini change mesh settings on line 57 to disable true disable = true
works perfectly
just run it with and recent version of proton
PROTON_USE_WINED3D=1 PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command% -nomovies
go and follow this guide to get steamtinkerlaunch on soulstorm: https://www.reddit.com/r/SteamDeck/comments/18hyp5g/how_to_run_dawn_of_war_mod_manager_and_other_mod/
If you are having issues getting steamtinkerlaunch to show up on flatpak, follow this guide: https://www.reddit.com/r/linux_gaming/comments/14kegjz/steamtinkerlaunch_doesnt_show_up_in_steams/
I found GE-Proton8-25 to work best out of all the versions of proton I tried
gamemoderun %command% -allowconsole
use this alternative launcher to manage and enable your steam workshop mods: https://github.com/X2CommunityCore/xcom2-launcher
works fine, though it runs like ass (this is not exclusive to linux, this game is just poorly optimised)
