hero
Published
--skip-launcher
Deleted/Renamed "Data/PsoCache.pak" to get past the "!status && vkCreateComputePipelines" assert
For me, tinkering is required to play the game in its current state. The workaround is easy, so I suspect a fix on the dev's end would also be pretty easy.
Any one of these issues would be a minor inconvenience. But combined, it means I can usually only play the game for about 30-45m at a time.
DXVK_ASYNC=1 VKD3D_CONFIG=dxr PULSE_LATENCY_MSEC=50 gamescope -h 1440 -r 144 -f -- %command%
After some time of playing, the voice audio will randomly be muted. Restarting is the only way I know to fix it.
After some time of playing, the map will randomly render black and be unusable. I just restart the game.
Occasionally the framerate will get into a bad state where every few frames are long (visible via mango) and flickery. I've tried messing with the fullscreen and vsync settings, but have not been able to resolve this without restarting the game. This effect is hard to look at, but technically the game is still just playable enough to go save the game before restarting.
After experiencing the issue where the map goes black, if I go to a fire and try to manually save, the game will freeze and I have to force kill it.
gamescope -W 2560 -H 1440 -r 144 -- %command%
I had an issue with the inventory system where, after opening a container, I could move the selection box from the left inventory to the right inventory, but not the other way. In order to get the selection box back to the left, I had to go all the way to the right so that it would wrap back around. I was able to work around this by using gamescope. Not sure why this makes a difference.
Searching the forums, the game seems to have several quirks and bugs even when running on windows. So it's not surprising that a few of them also show up when running through proton.
The foliage on the walls and ground have very noticable z-fighting. I'm running on a 3080, not sure if that's related.
The game launches, the screen goes black, then the game crashes and the UE crash reporter launches.
The game is unplayable for at least the first 5 minutes. Must be shader cache related, because after a while the framerate smooths out.
Very inconsistent framerate, lots of hitching.
I was able to stream in discord, but after tabbing over to stop streaming, the game crashed.
Aside from the very inconsistent frame rate, the game runs pretty well.
Alt+Tab would occasionally cause the game to render black. Sometimes alt tabbing again fixed it, other times you need to force quit.
The game doesn't recognize the XB Elite Series 2 controller mapping correctly, but using Steam's Controller mapping layer fixes this.
The xone package for using a wireless dongle with an xb1 controller has an intermittent issue that causes significant performance degredation. I tried root causing it, but could not. My solution was to play wired or using BT using xpad instead.
The game seems to sync to 60fps regardless of your monitor's refresh rate.
vblank_mode=3 %command%
The game runs great, but you may notice that it pegs your GPU, potentially rendering at over 1000 FPS and if you're on a laptop/steamdeck it'll suck your battery dry in no time. This is because they don't vsync and don't offer it in the settings. Searching the forums, it looks like this is an issue on windows too that people typically use vendor-specific control panels to force. On linux you can set the launch options listed above to force vsync, save your battery, and keep your device cool.
When the game loses focus it switches the resolution to the lowest (600x480 or something silly). I worked around this by switching out of fullscreen in the settings.
When the game loses focus it changes its resolution to the lowest possible.
The game crashes on shutdown with the error "GetThreadContext failed", then I have to kill the process.
