S.T.A.L.K.E.R. 2: Heart of Chornobyl (1643320)

[jarrard]

Compatibility Report

• Name of the game with compatibility issues: S.T.A.L.K.E.R. 2: Heart of Chornobyl
• Steam AppID of the game: 1643320

System Information

• GPU: RTX 4090
• Video driver version: nvidia 565.57.01 -->
• Kernel version: 6.12
• Link to full system information report as [Gist]: https://gist.github.com/jarrard/86b70884b754e302802571f3934237ee
• Proton version: Proton Experimental

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

LOG

Symptoms

Silent CTD after approximately 20mins

Reproduction

100%

[jarrard]

Proton Log was having issues attaching.
This one is where it silent CTD which happens all the time. Other then that the game runs fine.

protonlog.zip

ALMOST forgot to mention. Game CTD but steam shows it still running, however I can't find the process.

I have been using GAMESCOPE and HDR. Going to Test without. Perhaps this is GS issue.

[jarrard]

Tested without gamescope, and it appears to not crash.

So I will need to investigate about gamescope, as atm its only way HDR works under Plasma.

[jarrard]

I've tried a few things now and without much luck. The CTD is a bit random, normally it happens after 20mins but sometimes it will happen within 30s of play.

UPDATE: Looks like this is 100% a gamescope issue. It seems other people are using gamescope pretty well with HDR but for me, random ctd.

[Postnozet]

It seems the game doesn't save shaders cache and every launch it takes ~30mins (on Windows it takes 20 mins the first time and 5 mins afterwards). Could this be an issue in Mesa?

Operating System: Arch Linux
Kernel Version: 6.11.7-lqx1-2-lqx (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700X3D 8-Core Processor
Memory: 31.3 ГіБ of RAM
Graphics Processor: AMD Radeon RX 6800 XT

[jarrard]

This is not a issue for NVIDIA owners. First time is like maybe 5mins, after that is around 15-20seconds.

UPDATE: Actually Steam does take 20mins almost for the first vulkan shader compile time.

[Postnozet]

It seems the game doesn't save shaders cache and every launch it takes ~30mins (on Windows it takes 20 mins the first time and 5 mins afterwards). Could this be an issue in Mesa?

Operating System: Arch Linux Kernel Version: 6.11.7-lqx1-2-lqx (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700X3D 8-Core Processor Memory: 31.3 ГіБ of RAM Graphics Processor: AMD Radeon RX 6800 XT

Fixed by setting MESA_SHADER_CACHE_MAX_SIZE=10G env parameter

[simifor]

@jarrard what gamescope version are you using, and have you tried to use gamescope without HDR to see if it also crashes?

[jarrard]

@jarrard what gamescope version are you using, and have you tried to use gamescope without HDR to see if it also crashes?

I posted over in the gamescope issue tracker here (with versions) ValveSoftware/gamescope#1633

I do believe it still crashes without HDR enabled, however I should test it again just to be sure which I'll do now.

UPDATE: Decided to reinstall with CachyOS since its been a while and my system was setup for a virtual machine originally which I no longer use atm. Anyway solved a couple minor issues such as kwin crashing and also a keybind bug related with wayland windows (likely related to kwin_wayland crashes).

HOWEVER the underlining crash to desktop with WSI and HDR enabled via gamescope still occurs sadly. Took around 30mins or so to happen this time around thought. I'll test without HDR now and see how long it lasts for.

[jarrard]

Just confirmed, Crashes still with HDR disabled (--hdr-enable not used) and HDR turned off in game.

So this seems to be a issue with Gamescope, shame that tool has so many issues.

[JCDentonCore]

On my system game works but on log i have same warnings!

Proton log:
steam-1643320.zip

System: Arch Linux kernel 6.12, KDE plasma 6.2.3, 1440p resolution at 165 Hz, Ryzen 7800x3D, 32 GB ram DDR5 6000 Mhz dual channel, RX 7900 XT 20 GB, playing on maximum settings epic at 1440p.

https://youtu.be/gcoUmZYCsZE

[jarrard]

Yes I have seen that people reporting no issues on protondb and using gamescope.

I suspect this is a specific problem linked with Plasma6.2 or some other latest core software version.

It's still most likely a NVIDIA related issue!

Issue is resolved by this patch that is in master. ValveSoftware/gamescope#1630

I don't use a controller atm so can't test.

[gallexme]

anyone got any kind of controller working?