No Rest for the Wicked (1371980)

[kahnakha]

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:

• 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.

[kahnakha]

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.

[tgurr]

While the latest co-op beta worked fine with Proton Experimental with the official game patch from January 22nd the game fails to start. It doesn't even create a log file with PROTON_LOG=1 %command% for me. Switching to Proton 10.0-3 allows the game to work so this probably could count as a Proton Experimental regression. Hope you'll have time to look into it.

[kisak-valve]

Hello @tgurr, if there's no Proton log generated, that hints towards an issue with the Proton install instead of running the game itself. I'd completely close Steam, then run steam from a terminal and check the terminal spew when telling Steam to start the game. Alternatively, you can keep an eye on ~/.local/share/Steam/logs/console_log.txt (and/or console-linux.txt).

[tgurr]

Other games still work fine and I can reproduce this on another machine running another distro, but thanks for the hint and, here's the actual error:

chdir "/mnt/games/Steam/steamapps/common/NoRestForTheWicked"
ERROR: ld.so: object '/home/tgurr/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/tgurr/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/tgurr/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/tgurr/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/tgurr/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Game Recording - would start recording game 1371980, but recording for this game is disabled
Adding process 836288 for gameID 1371980
Adding process 836289 for gameID 1371980
Adding process 836290 for gameID 1371980
pid 836379 != 836375, skipping destruction (fork without exec?)
pid 836384 != 836375, skipping destruction (fork without exec?)
/mnt/games/Steam/steamapps/common/NoRestForTheWicked/NoRestForTheWicked.exe: 8: /mnt/games/Steam/steamapps/common/NoRestForTheWicked/NoRestForTheWicked.exe: Syntax error: ")" unexpected
Adding process 836375 for gameID 1371980
Game Recording - game stopped [gameid=1371980]
Removing process 836375 for gameID 1371980
Removing process 836290 for gameID 1371980
Removing process 836289 for gameID 1371980
Removing process 836288 for gameID 1371980

$ file /mnt/games/Steam/steamapps/common/NoRestForTheWicked/NoRestForTheWicked.exe
/mnt/games/Steam/steamapps/common/NoRestForTheWicked/NoRestForTheWicked.exe: PE32+ executable for MS Windows 6.00 (GUI), x86-64, 7 sections

I've set Proton Experimental globally as compat tool so sorry for jumping on conclusions in regards to a possible Proton Experimental regression, when manually setting the compat tools for the specific game to Proton Experimental as well it also works. Looking at https://steamdb.info/sub/481243/history/?changeid=33235578 there's been a Linux depot added with

Added depot 1371986

so maybe that makes steam not try to use Proton at all and fails now which would also explain why PROTON_LOG=1 %command% does nothing. Also when ticking the compat tool to a Proton version and ticking it off nothing is actually downloaded. Looks like the Linux depot may be incomplete and/or broken(?)

[kahnakha]

Something else I noticed recently is the overwhelming amount of system memory(RAM) that is been utilized by the game, in comparison to the same running on WIndows where it only takes about 6 or 7gb of system memory.
On SteamOS with any proton version it's easily filling up the 16GB of RAM on both SteamDeck and ROG Ally.
I tested it on another system with 32gb and it still takes about 16-17gb which is quite high, especially when most handhelds are only having 16gb thus throttling severely the rest of the resources.
CPU utilization about 40%, GPU about 50-60%, and the game runs with 20-30fps on the lowest possible preset.