Andi
Published
Apart from the video files and the requirement to launch the game with "-dx11" command line switch, it's working as well as on Windows.
Artifacts on character skins if using Direct3D12. Artifacts disappear if passing "-dx11" command line switch.
Except for the cutscenes and tutorial videos, the game is working like a charm.
Videos are not playing. This means that cutscenes will render as "black screen".
One needs to hold the "f" key to skip the cutscenes.
While Steam's default proton version is unable to play the videos, Proton-5.9-GE-8-ST works perfect.
Once the game is installed, along with the media-foundation workaround ( https://github.com/z0z0z/mf-install ), it's running fine.
Needs teh media foundation workaround to get past the tutorial
While it took me a while to get the game to run in a stable manner, it does run pretty well now. I haven't played too much yet though.
RADV_DEBUG=llvm %command%
Without any tinkering, the game would crash for me every time I tried to click on a building in the building menu.
In order to get the game to run, I had to do three things:
- Force Proton version 9 or Experimental
- Update my graphics drivers to Mesa 24.1.1
- Change launch options to "RADV_DEBUG=llvm %command%"
Forcing a newer Proton version was needed, because of the error "DirectX 12 Agility SDK could not be loaded. Please update your Poerating System to Windows 10 Version 1909 or newer.". I have no idea which Proton version Steam tried to use without forcing Proton 9, but it obviously was too old.
The graphics driver update was initially a shot in the dark. However, I tried downgrading to 24.0.9 after I found the RADV_DEBUG=llvm workaround, and with that older mesa version, the game wouldn't launch if this environment variable is set.
Last, but not least, I got the idea to try "RADV_DEBUG=llvm %command%" because of this post: https://github.com/HansKristian-Work/vkd3d-proton/issues/1725#issuecomment-2058452620 I thought, that if the bug is caused by a shader, maybe using another shader compiler (llvm instead of aco) might work around the bug (and it seems it does). However, this has the drawback that llvm has longer compile times than aco, so shader compilation stutter is more noticeable with this compiler.
Right after installing this game, I had the problem that the image didn't update unless I tabbed out and back into the game. Sooo, I had "still image" -> Alt+Tab -> "another still image" -> Alt+Tab -> "yet another still image". Took me a while to figure that I had (by accident) forced Proton 6.4 for all titles... After changing that to Proton 7.0, this game now works perfectly fine for me.
That's why I guess that people who just install it without having a globally forced proton version, will have a good experience also without tinkering.
