ValveSoftware
No Rest for the Wicked (1371980)
Compatibility Report
- Name of the game with compatibility issues: No Rest for The Wicked
- Steam AppID of the game: 1371980
System Information
- GPU: AMD Z1E (ROG Ally)
- Video driver version: 24.2.99
- Kernel version: 6.11.11
- Link to full system information report as Gist:
- Proton version: Latest Hotfix in SteamOS
I confirm:
- [x] that I haven't found an existing compatibility report for this game.
- [ x] that I have checked whether there are updates for my system available.
Symptoms
I found quite a big memory leak in this game regardless of Proton version, or Linux distro, so it’s not the SteamOS per say, as I have also tested on other distros too, and the issue still persists. It takes anywhere from 1 to 2h ingame before the memory leak starts happening, and as a result the performance starts hammering down.
This only happens with Linux running Proton, and it does not happen with Windows on the same system.
Reproduction
-Start the game, and note the MEM, and VRAM usage.
-Stay on one spot, not doing anything, return to the game after that, and note the system resource usage again. (spot the huge difference)
One easy way to trigger it without having to wait this long:
-Go to town -Go to the area called “The Black Trench”(town sewers area) -Return back to town
It takes exactly 1min to do these steps, and for the performance to be hammered heavily.
Update: There seems to be an issue with the focus of the game visuals as well, something that is not happening on Windows native, but only seems to affect Linux distros using Proton.
When FSR is enabled from the ingame settings, and when there is movement(main character moving) the entire image starts pulsating in and out of focus every 2-3 seconds or so. For a split second the entire image becomes super sharp(like if the sharpness is set to max) then back to normal and so on.
The issue with the support memory leak is also still active, as it is also very easy to reproduce, as it only requires the main character to enter, and exit an area. This is also tested on native Windows, and it’s also not happening there.