UnsupportedShow Details
Unknown
fixed with PULSE_LATENCY_MSEC=60
Switch to Vulkan in-game because the DX11 renderer blows
Works well with Proton Experimental. With Proton GE even the video playbacks work
Works out of the box
No issue
Runs perfecly out of the box now.
Works perfect out of the box with a recent update thanks to active developer support
The game may not "officially" support Linux, but the developers are aware of Proton and Linux and took steps to get it working properly! However it appears you'll need to be on a more recent Linux version if you're on an Ubuntu based distro (Ubuntu 22+ should do it).
As of the latest update (Fleet update at the time of writing) the CTD issues appear to have been fixed, and the game works perfectly with proton experimental selected
While the game runs now under Linux it is still is very unstable in general.
CTDs, but probably unrelated to Proton and just "the usual" for this game considering similar forum posts from other players who use Windows instead of Linux.
Sucessfully ran under Proton with:
Proton 8.0.4 (default Steam)
Game Version 1.1.7.4 Beta
(If you tried to get this game running before in one of the previous broken versions make sure to delete all old configuration files)
Played with new 1.1.7.3 beta with forced Proton experimental. Worked perfectly fine, just same as windows install.
%command%
minor pixel errors (2 times 5x3 Pixels on fixed location), constant unmoved
The developers degraded the linux/proton experience in between, now its great again.
With the recent beta build of 1.1.7.1 the game goes from completely unlaunchable to running out of the box. Tried on Experimental and GE but I suspect even regular proton will work now. Just be sure to select the 1.1.7.1 beta option in the beta selection menu of preferences until that build goes live.
Totally Borked
Though it was working in the past, seems to be in a borked state currently. Refuses to launch.
prior fixes/work-around no longer seem to work
protontricks 1531540 d3dcompiler_47
Attempted most ot the old fixes metioned hear but with no luck gettting past the launcher
If you find that you cannot go beyond 60FPS, go to the data folder, open GameSettingsOverrides.txt and change DisableFixedTimeStep to true
protontricks 1531540 d3dcompiler_47
Worked few years ago, I can not able to run anymore
protontricks --no-background-wineserver 1531540 dotnet472
Broken
protontricks 1531540 d3dcompiler_47
The game only works with Glorious Eggroll version 7-41 specifically, and after having run the specified protontricks command. Higher versions of Glorious Eggroll lead to the game not running (I haven't tried lower versions)
'protontricks --no-background-wineserver 1531540 d3dcompiler_47' needs to be run in the terminal for the installation to be complete. Game will not run past the launcher otherwise.
When changing the ingame graphic driver from directX 11 to Vulkan 2.0.0 through the settings the fullscreen broke, but the issue was solved with a game restart and has not repeated itself since.
If the d3dcompiler method doesn't work you might want to try using dotnet472 instead (it didn't work for me though). This might require you to temporarily use proton 5.0 to get around certain warnings but you can upgrade proton version back to higher versions after installation.
Game works mostly out of the box with a few minor tweaks on latest Aurora update (which borked previous workarounds)
gamemoderun mangohud %command%
protontricks --no-background-wineserver 1531540 d3dcompiler_47
The Aurora update borked previous work-arounds. After a full reinstall (uninstalled game via steam and blew away the prefix), and installing d3dcompiler_47 via protontricks, the game now launches and plays out of the box without any launch params.
Props to marty651 (https://steamcommunity.com/app/1531540/discussions/3/5561388294332782864/?ctp=6) for testing to find the latest working version of Proton-GE.
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 DXVK_ASYNC=1 %command%
protontricks 1531540 d3dcompiler_47
After running 'protontricks 1531540 d3dcompiler_47' and choosing GE-Proton7-17, the Aurora update works again
Aurora patch (Version 1.1.0.9) breaks the previous workarounds
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 DXVK_ASYNC=1 %command%
Looks like the new Aurora patch (Version 1.1.0.9) breaks the previous workarounds. The devs integrated .NET 7 in the exe. I tried installing the .NET 7 runtime with protontricks like it worked for .NET6 previously, but the game does not start past the initial launch window.
Game works perfect out of the box!!
Game works perfect w/o any tinkering!!. Just make sure to change to vulkan within the game settings and you will get 60FPS at all times!! A+++
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 DXVK_ASYNC=1 %command%
d3dcompiler_47
I've played up to 30min and haven't saw a problem for the moment.
Doesn't go past launcher
Tried Proton Experimental, Proton GE, Latest Stable Proton, tried with and without launch options suggested by others, nothing helps
d3dcompiler_47
Given how crashtastic the game is overall, this is probably not proton related
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 DXVK_ASYNC=1 eval $(echo "%command%" | sed 's|/Launcher.exe|/DW2Net6Win.exe|')
Switch to beta channel
I didn't play too long, but was able to start a game and experienced zero issues in the ~30 minutes I had to play after getting it working.
Currently not playable
Crashes on start up with defult config
Atemped to play with a few versions of proton, with no succses yet.
