Just Plain Garak
Published
VKD3D_SHADER_CACHE_PATH=0 %command%
Like most others with an AMD card, combinations of Strand Hair and/or Ray Tracing would produce driver timeouts (logs show an eventual device disconnected error). After lots of troubleshooting, it seems to me that DATV doesn't like vkd3d's external cache. Disabling vkd3d's cache and letting the game handle its own shaders with the environment variable VKD3D_SHADER_CACHE_PATH=0 appears to have cured those crashes.
Either disable Strand Hair and Ray Tracing or disable vkd3d's cache and you'll have a great time. Machine in the report is out of date, I'm on F41 on latest Mesa and CachyOS LTO kernel 6.11.9.
The tweaks I've done have made the experience enjoyable and stable and Linux gamers tend to be technical enough to tinker out issues.
PROTON_NO_FSYNC=1 DXVK_ASYNC=1 VKD3D_CONFIG=no_upload_hvv mangohud gamemoderun %command%
I'm using a DualSense controller, and right now EasyAntiCheat breaks the Steam Overlay, so that mapping was not working. I have had success with xboxdrv and am currently using a build of the dualsense branch of SC Controller that supports DualSense to work around this issue.
Initially, I had some stuttering at random intervals. With the options I have set, however, the stuttering has entirely disappeared.
Have been invaded a few times and it worked as I would have expected.
This is a fantastic game, and the experience playing in Linux, once I ironed out the controller and performance issues, has been fantastic.
The tweaks I've done have made the experience enjoyable and stable and Linux gamers tend to be technical enough to tinker out issues.
PROTON_NO_FSYNC=1 mangohud gamemoderun strangle 59.94 %command%
I'm using a DualSense controller, and right now EasyAntiCheat breaks the Steam Overlay, so that mapping was not working. I have had success with xboxdrv and am currently using a build of the dualsense branch of SC Controller that supports DualSense to work around this issue.
Initially, I had some stuttering at random intervals. With the options I have set, however, the stuttering has entirely disappeared (updated further from my initial report - added strangle and set an appropriate FPS limit for my refresh rate).
Have been invaded a few times and it worked as I would have expected.
This is a fantastic game, and the experience playing in Linux, once I ironed out the controller and performance issues, has been fantastic.
mangohud %command%
Using a DualSense, I just had to set the Desktop Configuration to a normal controller layout and that tricks the game into working with Steam Input.
Honestly, the multiplayer experience worked great out of the box. Goes to show if the devs put in the time to allow EAC to work on Linux, the experience can be the same as native Windows.
This is my 3rd report after a few weeks of tinkering. I think feral gamemode conflicts with the built-in frame limiter and that causes all of the stuttering I couldn't track down. Without gamemode flagged, the game runs essentially perfectly on Linux with the latest GE-Proton (or Experimental) and no other tweaks aside from Mangohud, but that's a me thing and its not required in any fashion.
Game Launches, but locks up entire computer when trying to load into game.
gamemoderun mangohud %command%
I've tried mesa-git, standard mesa drivers, many versions of GE-proton, Proton Experimental, Proton Hotfix, and the behavior is always the same (pre and post Winter Update). I get into the main menu, music and all, but when I try to load into the campaign I sit on the loading screen for a while and then my entire PC locks up and I have to do a hard reset.
Since Steam updated to their new interface with the new overlay, Hunt: Showdown crashes with a Wine C++ error when activating the overlay. I have to disable the overlay entirely and can only accept team invites (since sending them requires the overlay) from chat windows. SOMETIMES the overlay works, but it seems like it keeps breaking intermittently so I just had to turn it off. Have tried several versions of Proton but they all have the same effect.
Other than the overlay issues, if you are okay only being able to accept team invites from chat for the time being, its a fantastic experience. For me on an AMD GPU, the game runs better than Native Windows on Linux.
I've tuned the settings for the game in a config file in the Proton prefix. I've got the game running at a stable 30 FPS with occasional dips that I believe I can attribute to the UE4 engine itself. I've published my config file and instructions for changing yours on Github.
At first launch, the game asks to install a pre-requisite. Simply run through the installer like you would on any other computer.
With an AMD CPU, the game runs exactly as I would expect after setting the listed WINEDLLOVERRIDE.
WINEDLLOVERRIDES="amd_ags_x64.dll=b" gamemoderun mangohud %command%
Running on an AMD CPU, I was unable to start the game without the listed WINEDLLOVERRIDE that I found from soey in the Steam forums. Their post can be found here! https://steamcommunity.com/app/1659420/discussions/0/3494256256404009471/
Not sure if its a game or a Proton issue, but I had to scour forums for a solution that another user found to specify a DLL override to launch on AMD processors. The game had no issue running on my Steam Deck, which runs an AMD SoC, so theoretically there should be some way to get this game to simply launch without manually selecting the AMD DLL listed in my report.
