Square789
Published
Slightly choppy voicechat. Likely was network-related/Not Proton's fault
Compatability/Switching to Proton Experimental worked flawlessly. On the native version, the audio input device dropdown would only contain "{option}{option}{option}{option}" and no mic input was recorded.
Multiplayer broken by latest "Epic" Games patch
I was unable to play with friends; accepting invites on either end was met with a silent rejection by the game. The Linux native version of Payday has just been killed, it seems. The other menus and singleplayer probably still somewhat work; I did not bother to test the latter though cause multiplayer is the only way Payday was enjoyable to me.
The game's FPS are quite low, probably due to my insufficient GPU. nvidia-settings reports 100% usage while the game is running.
Setting the lowest ingame graphics doesn't help, but this steam guide identifies some values that made performance bearable again!
Modified compatdata/1361210/pfx/drive_c/users/steamuser/AppData/Roaming/Fatshark/Darktide/user_settings.config as follows:
rough_transparency_enabled = true (from default false)
rt_checkerboard_reflections = false (from default true)
rt_light_quality = "off" (from default "high")
sharpen_enabled = true (from default false)
screen_resolution = [
1152
648
] (from default [1600 900], which was the lowest the settings menu would allow)
Fullscreening behaves strangely. Can't make out a difference between "Fullscreen" and "Borderless Window", although it's not like i understand the exact details of them on X11.
The game seems to run best when it is in fullscreen just as it starts.
Tabbing out has a risk of freezing the game for good.
Tabbing out will cause the game to grow window decorations again, sometimes resizing down to its true resolution and suffering from lower FPS. Navigating back to graphics and re-selecting "Fullscreen" carries another risk of crashing, but if that is survived, FPS rise again.
Launcher: After hitting Play, there is a ~50% chance the launcher will simply hang on the "Building Shader Cache" progress popup. Only way out is killing the process and trying again until the game starts properly.
Thanks, and have fun
