Compatibility Report

You can try to switch to proton 8 and it should running then

You can try to switch to proton 8 and it should running then

Yes!

Graphics default to 1080p Low and cannot be changed, no DLSS, but everything is running, and I am on the mountains now, too.

Thank you!

Thank you for the reports. Could you check if this works fine on Bleeding Edge or if it still has the issue?

I'm getting the game to start, but it uses up all available system memory on the "Death Stranding 2 - On The Beach" splash screen after the launcher but before the logos, and crashes with the PlayStation reporter. This happens on any Proton version (including Experimental Bleeding Edge) on Mesa 26.0.2, even after deleting shadercache and the prefixes between runs.

EDIT: Here's the steam-3280350.log file, and after running it on my Steam Deck, that splash screen only took a second or two before proceeding to the intro videos, so something is definitely wrong. In the game's crash log, it ends with:

16:13:52:829 (00000328) > [NxApp] Swapchain initialized
16:13:52:829 (00000328) > [NxApp] Initializing renderer...
16:13:52:829 (00000328) > [NxApp] Renderer initialized
16:13:52:829 (00000328) > [Render] UMA = False, CacheCoherentUMA = False
16:13:52:829 (00000328) > [Render] Tight alignment support: yes
16:13:52:873 (00000328) > [PSO] Loaded 25277 shader hashes, 40837 descriptors from appdir:HashDB.bin
16:13:52:969 (00000328) > [PSN Account Linking] [PSN] PSPC initialization failed: 8a800111
16:13:52:970 (00000328) > [PSN Account Linking] [PSN] Setting device data collection setting failed 8a80010d
16:13:52:970 (00000328) > [PSN Account Linking] Failed to update data collection policy to PSPC, error=0
16:14:10:579 (00000480) > [D3D] m_pDevice->CreateHeap(&heapDesc, IID_PPV_ARGS(&pHeap->m_pHeap)) failed with HRESULT 2147942487 (0x80070057)
16:14:10:587 (00000480) > [Crash] Memory statistics:
16:14:10:587 (00000480) > [Crash]   Total RAM = 61.9 GB (63395 MB)
16:14:10:587 (00000480) > [Crash]   Avail RAM = 0.2 GB (187 MB)
16:14:10:587 (00000480) > [Crash]   Total virtual memory = 131072.0 GB (134217727 MB)
16:14:10:587 (00000480) > [Crash]   Avail virtual memory = 131071.9 GB (134217603 MB)
16:14:10:587 (00000480) > [Crash]   Total page file = 85.9 GB (87971 MB)
16:14:10:587 (00000480) > [Crash]   Avail page file = 1.6 GB (1616 MB)
16:14:10:587 (00000480) > [Crash] 
16:14:10:587 (00000480) > [Crash] RAM info:
16:14:10:587 (00000480) > [Crash] Unhandled exception at address 0x00000000f28ca876 (code: 0xc0000005): "Access violation"
16:14:13:307 (00000480) > [Crash] Created minidump at "C:\users\steamuser\Documents\DEATH STRANDING 2 - ON THE BEACH\DEATH STRANDING 2 - ON THE BEACH-v1.0.48.0 2026-03-19-16-14-11.mdmp".

I have the same issue as peter. Proton log mentions this warn as the reason: vkd3d-proton:vkd3d_try_allocate_device_memory: Allocation size 4294967296 exceeds maxMemoryAllocationSize of 4294967292.

edit: Bleeding Edge doesn't fix it.

some odd behavior for sure. it crashed the first couple times, then played through the intro section on a 3060 ti and current stable proton. had to add dxvk_hdr=0 %command% to launch options to get the colors right.
after about 60 minutes of gameplay, some but not all of the audio cuts off. i can hear rain and sam’s gadgets but dialogue and bt sounds are gone.
now it’s crashing on launch again.

@Blisto91 Bleeding Edge seems to have fixed this issue for me, I have gotten into the game with that

Seems like it launching the game without problem but I have problem with my dualshock 4 when launching it with bleeding edge. the joysticks are going up while on proton 8 i dont have such problem

Thank you for the reports. Could you check if this works fine on Bleeding Edge or if it still has the issue?

Bleeding Edge is working well so far. I've got DLSS back, I can modify graphics settings, will come back and edit this comment if I find any problems.

Edit: If I push the graphics too far, game freezes and I can't tab out. I ran DS1 at 4k@High, now I run 1080p@High and it plays very solid.

Extremely impressed with the ability to run with Proton 8 at launch, and that the Bleeding Edge Experimental came up same day as launch. Kudos!

OS: NixOS 26.05 (Yarara) x86_64
Host: B550M AORUS ELITE AX (Default string-CF)
Kernel: Linux 6.18.18
DE: KDE Plasma 6.6.3
WM: KWin (Wayland)
CPU: AMD Ryzen 7 5700X3D (16) @ 4.15 GHz
GPU: AMD Radeon RX 9070 XT [Discrete]
Memory: 31.27 GiB 

Game works, but performance is pretty bad. It uses ~80% of my CPU even in main menu and I can't even hold 60 fps no matter the settings. I was thinking it's shader cache compilation, but even after playing for about 2 hours and enabling shader cache in Steam it didn't change. Audio glitch is also present.

OS: Arch Linux x86_64
Host: MS-7E56 (1.0)
Kernel: Linux 6.19.8-zen1-1-zen
DE: KDE Plasma 6.6.3
WM: KWin (Wayland)
CPU: AMD Ryzen 7 9800X3D (8) @ 5.27 Ghz
GPU: AMD Radeon RX 9070 XT [Discrete]
Memory: 60.38 GiB

CPU usage constantly maxed out at 100%, GPU usage hanging around 70-85%.
Similar performance issues. Opening scene constantly bounces between 40-60fps with plenty of stuttering at 4K using FSR4 with dynamic framerate target set to 60fps. Cutscenes break down with audio not playing for a while until the video eventually kills its framerate to let the audio catch up again. Skipping through one of the early cutscenes resulted in further instability, with dialogue options not rendering.

OS: Omarchy 3.4.2
Motherboard: X870 AORUS ELITE WIFI7 (Default string-CF-WCP-ADO)
CPU: AMD Ryzen 7 9700X (16) @ 5.79 GHz
GPU: NVIDIA GeForce RTX 4070 Ti SUPER [Discrete]
Monitor: 2560x1440 in 32", 165 Hz [External]
Memory: 12.30 GiB / 30.95 GiB (40%)

Switching to bleeding edge solved the issue for me as well and I can use all features of DLSS and Ray Tracing. I am encountering the audio bug as well. Restarting the game resolves.

Performance is great, running DLSS at Native with all settings at max.

Only other issue I have noticed is that exiting to desktop doesn't close the game and I need to force kill the process.

EDIT: Crashes ever hour or so.

OS: Fedora Linux 43
Kernel: Linux 6.19.8-200
DE: KDE Plasma 6.6.2
WM: KWin (Wayland)
CPU: AMD Ryzen 7 7800X3D 
GPU: NVIDIA GeForce RTX 4090 - 580.126.18
Memory: 30.00 GiB

Something change since the launch day on Proton Experimental Bleeding Edge. I was getting 40-50 fps with high cpu usage and stutters. Right now game still doesn't run as good as on Windows but it's somewhat playable. It runs at 70-80 FPS but the frame times are still bad especially while panning the camera around etc.

EDIT: Wanted to post logs but they are 1.2GB after few minutes of gameplay. It's getting spammed with 1385.839:0128:01c0:fixme:netprofm:list_manager_GetConnectivity 000000002EDF7020, 0000000008FFFE60

The performance through Proton is absolutely hideous compared to (the same setup) on Windows. The CPU usage stays maxed (for as long as i've managed to play) and the GPU is under utilized, which is not the case on Windows. Something must be very wrong.

Audio is also constantly crackling.

Crashes during first hideout cutscenes, after losing audio.

Something is pretty wrong with audio, not sure why

I can confirm the high cpu usage.
My 5700X3D on Linux is sitting at around 80%.
On Windows is less than 40%.
Using Proton Bleeding Edge.

Can confirm the excessive CPU usage.
Also a note to proton-ge users: game is broken with ntsync for me (crashes upon loading into world). no issues otherwise.

90% CPU usage on main menu. I though shaders were compiling, but not sure. I just let it run for ~20 min and the issue persists. Maybe more time for shaders compitaion? Or just wait for game or proton patch?

Bleeding edge fixed my problems with poor performance (about 30 fps) on 4080, Arch, latest main branch drivers.

bleeding-edge version of Proton Experimental fixed my performance issues as well. I was previously using Proton-CachyOS (10.0.20260312-slr).

I'm also using the following launch options, though I don't think they're contributing any:

PROTON_DLSS_UPGRADE=1 PROTON_NVIDIA_LIBS_NO_32BIT=1 VKD3D_CONFIG=nodxr gamemoderun %command%

I'll give it another shot and report back.

EDIT:
Performance is definitely better with the new bleeding edge build, but the log spam remains. CPU utilization is still maxed on every thread (16T) and frametimes are still less consistent than default proton or GE-Proton-33 with logging enabled. Getting <30FPS with no logging enabled on regular proton, ~60FPS with bleeding edge and no logging, and ~100FPS with regular proton and logging enabled.

I can confirm the high cpu usage. My 5700X3D on Linux is sitting at around 80%. On Windows is less than 40%. Using Proton Bleeding Edge.

Similar experience. On a 7800X3D the game is using roughly 90-95% of my CPU time on PikaOS, around 50-60% on Windows 11. Using Proton Bleeding Edge too. Similarly, it feels like there's some kind of frame pacing issue on Proton, because running on Windows was noticeably smoother, even though the framerates were similar.

Just popping in again to confirm what @alicium is saying; with Proton bleeding edge it is indeed much better than on release day but it's still far from close to the performance you get with the same hardware in Windows.
Something is still wrong.

just envs, DS2, looking at sky, ingame:

Proton Experimental, no flags: 101fps / 85 % CPU
Proton Experimental + flags: 120fps, 60% CPU

WINE_FSYNC_SIMULATE_SCHED_QUANTUM=1 WINE_FSYNC_YIELD_TO_WAITERS=1 %command%

Proton Experimental (bleeding-edge -> proton experimental in library, right click, properties, set to bleeding-edge)

can you guys reproduce?

Replying to https://github.com/ValveSoftware/Proton/issues/9593#issuecomment-4103379074

w/ bleeding edge

No flags:	Flags:

Definitely helps, you can tell a huge improvement just from the frametime graph.

@uxandai a lot better, but still high compared to Windows and GPU not being fully utilized.

I'm seeing no improvements on the splash screen crash issue with updates to Bleeding Edge, though it seems Windows users may be experiencing the same issue from what I've read online. I'll report back after the first game patch

@peterdwall long shot: did you enable dlss? try deleting your death stranding 2 config folder under steam/steamapps/compatdata/3280350/drive_c/users/username/My Documents/Death Stranding 2 and start with defaults.

the game also writes its own log to that folder. i found that my crash was related to dlss (yes even on bleeding edge) so just sticking with the default upscale method fixed it. check the log, maybe it’ll help.

still struggling with performance and audio dropping out during cutscenes or when the game loads new areas.

WINE_FSYNC_SIMULATE_SCHED_QUANTUM=1 WINE_FSYNC_YIELD_TO_WAITERS=1 %command%

I had some improvement (10-15 fps to 20-24 fps), but still very high CPU (>90%). (see EDIT below)

Command line:

ulimit -n  1048576; WINE_FSYNC_SIMULATE_SCHED_QUANTUM=1 WINE_FSYNC_YIELD_TO_WAITERS=1 PROTON_USE_XALIA=0 PULSE_LATENCY_MSEC=60 gamemoderun %command%

Game settings and other details:

• quality: high @ 1920x1080
• upscaling FSR3 with dynamic scaling @ 30 FPS
• VSync ON at half refresh rate (60/2=30) - disabling it doesn't change much anyway
• streaming over Sunshine/Moonlight @ 60 FPS

@uxandai you seem to be pretty sure of the root cause, do you mind sharing more? E.g. other bug reports, documentation, etc. maybe other people can help too. Thanks!

EDIT: turned out I had Sunshine using a SW encoder, so the CPU was way over :-) after making it work with a HW encoder, CPU dropped at about 80%. I can now get at least a more-or-less stable 30 FPS with high quality settings (just beginning the game). Thanks!

CPU: Intel Core i3-10105
GPU: AMD Radeon RX 6800 (16 GB)
RAM: 32 GB
OS: Debian testing (updated today)
Proton: bleeding-edge (updated today)
Kernel: 6.19.8
Mesa: 26.0.3
Window system: X11 (with XFCE)

@daniele-athome not so sure anymore, too early (problem with connections spamming and wwise audio in this game/engine when comes to wine/linux)

WINE_FSYNC_SIMULATE_SCHED_QUANTUM=1 WINE_FSYNC_YIELD_TO_WAITERS=1 %command%

On proton-cachyos 10.0-20260319 CPU usage dropped from 80% to around 50% and GPU is getting utilized fully, seems to be on par with windows now.

WINE_FSYNC_SIMULATE_SCHED_QUANTUM=1 WINE_FSYNC_YIELD_TO_WAITERS=1 %command%

On proton-cachyos 10.0-20260319 CPU usage dropped from 80% to around 50% and GPU is getting utilized fully, seems to be on par with windows now.

I just tested with those launch args and that proton version and i disagree, it is still not nearly as smooth as on Windows, FPS is not reaching the same levels (about 10fps less in my case) and the frame pacing is still all over the place compared to windows where its rock steady. The GPU is also not as utilized as it is on Windows.

Unfortunately.

@Zonrotan what GPU/other specs?

I agree: the situation has certainly improved but it's far from being on par with Windows. With bleeding-edge, the flags by @uxandai and dynamic scaling I can get stable 30 FPS now (high settings; even with the portable preset I can't get more than 40-45 FPS).

@Zonrotan what GPU/other specs?

It would help also to compare their specs with @TERMSTRAANGE's.

Here are my specs:

CPU: Ryzen 5 7640HS
GPU: RTX 4060 8GB
RAM: 16GB
OS: CachyOS
Proton: proton-cachyos 10.0-20260319(latest)
Kernel: 6.19.9-1-cachyos
GPU Drivers: 595.45.04
DE: KDE on Wayland

@Zonrotan what GPU/other specs?

Distro: Fedora Linux 43 (KDE Plasma Desktop Edition)
Kernel: 6.19.8-200.fc43.x86_64
RAM: 32 GB
GPU Driver: 4.6 Mesa 25.3.6
GPU: AMD Radeon RX 7800 XT (radeonsi, navi32, LLVM 21.1.8, DRM 3.64, 6.19.8-200.fc43.x86_64)
CPU: AMD Ryzen 7 7800X3D 8-Core

@TERMSTRAANGE without fully implemented heaps probably it will be few % less on Nvidia comparing to Windows.

For CPU tho, theres some things that should be targeted in game code directly, but keep expectations low. Probably someone (or me) will come with some game specific quirks.

Using game-performance?

@uxandai not using game-performance, but I do use sxc_lavd.

Booted up the game again and it seems that the CPU usage is back up again and performance is dropped. Not sure what's up with that.

@TERMSTRAANGE what about without scx, BORE?

Been digging into the CPU usage issues on this game for a while and wanted to share what I found since it might help someone.
First thing worth knowing is that WINE_FSYNC_SIMULATE_SCHED_QUANTUM=1 WINE_FSYNC_YIELD_TO_WAITERS=1 does actually help across all proton versions (GE, Bleeding Edge, Cachy, EM, stable, all of them) but it only works if you have FSync on, so make sure NTSync is disabled or you won't see any difference.
To give you an idea of the impact, here's what I measured on Proton Experimental Bleeding Edge with FSync on:

• Stock game, no env vars: ~90% CPU during gameplay and pause menu
• Env vars only, no patch: ~60% CPU consistently, gameplay and pause menu both sit there
• Binary patch only (see below), no env vars: 30-50% CPU during gameplay but 60%+ CPU the moment you open the pause menu and it doesn't come back down
• Both combined (env vars + binary patch): 30-40% CPU during gameplay, but opening the pause menu still jumps to 60%+ and stays there

So the env vars alone are a solid improvement and the most accessible fix since they don't require touching the binary. Patching the binary DS2.exe [credit to https://github.com/jas0n098 for detecting this] (file offset 0x23D69CE, changing 0F 8E to 48 E9) [PLEASE DON'T THIS WITHOUT BACKUP] does help during gameplay but doesn't address what happens in the pause menu at all.

The reason for all of this, from what perf showed on the unmodified binary, is that __x64_sys_futex alone was eating 13.27% of all CPU time. What's happening is Background threads 1, 2, 3, 8 and 10 are all just hammering NtWaitForMultipleObjects with basically a zero timeout nonstop, and the main thread keeps responding with futex_wake -> try_to_wake_up over and over. When you open the pause menu it just piles a whole second loop of the same thing on top, which is why it spikes separately. When I profiled specifically with the pause menu open the hot JIT addresses were all around 0x1400CE022, 0x1400CF242 and 0x1400FCEF1, all going into fsync_wait_objects -> NtWaitForMultipleObjects.

The env vars help because instead of all those threads just spinning and burning CPU, Wine actually yields and doesn't go crazy when the main thread tries to wake them all at once. It's not a real fix since the game itself is just polling way too hard, but it takes the edge off. If someone wants to actually fix this properly the pause menu polling loop needs to be addressed separately, the current binary patch doesn't do anything about that.
EDIT: This is before the last update from Nixxes (https://steamdb.info/patchnotes/22438405/).

Well, the actual issue here is not a fsync or other Proton bug...

A better working workaround (than adding delays to all the sync primitives) is in the just updated Proton Experimental bleeding-edge branch (https://github.com/ValveSoftware/Proton/wiki/Proton-Versions#proton-bleeding-edge)

UPDATE. That workaround is supposed to remove the great excessive CPU usage from the background threads. Depending on setup, settings and other things it may or may not affect the actual FPS.

I can verify the gains described by eXxe-elcior, but after playing the first part of the game and arriving to the river, the game will run at 5-6fps no matter what, while utilizing less than 50% of both CPU and GPU

This fixed the CPU usage for me:
https://github.com/jas0n098/DS2NetFix

Copy both files into your game folder and set the launch arguments:
WINEDLLOVERRIDES="xinput1_4=n,b" %command%

FWIW that is hopefully fixed in Experimental bleeding-edge already (https://github.com/ValveSoftware/Proton/issues/9593#issuecomment-4103934483).

FWIW that is hopefully fixed in Experimental bleeding-edge already ([#9593 (comment)](https://github.com/ValveSoftware/Proton/issues/9593#issuecomment-4103934483)).

Does not work for me, CPU usage is still at 80-85% for me and performance drop to 40 from 60 ...

This fixed the CPU usage for me:
https://github.com/jas0n098/DS2NetFix

I'm curious, what does it do? What was the actual issue?

I'm going to try it later tonight.

@daniele-athome

Experimental ASI plugin for Death Stranding 2 that tries to fix very high CPU usage caused by very aggressive connectivity checks.

Yes, I mean what's the fix, technically? I'm asking as a fellow developer and I was curious about it :-) it is not clear from the source code.

Latest Proton bleeding edge did not seem to give me significant perf gains over just having WINE_FSYNC_SIMULATE_SCHED_QUANTUM=1 WINE_FSYNC_YIELD_TO_WAITERS=1, but doing @eXxe-elcior 's binary patch as well took me from low 40s FPS to solid 60, tyvm!

be advised: @eXxe-elcior 's patch might break online functionality (manual or auto-login gives me an endless Connecting... spinner, i think it also disables manual saving), probably a failed file integrity check.

@jazzsnobeatcake I deleted the prefix and shaders after each try with an updated Bleeding Edge branch. I've also tried all three upscalers, as well as setting graphics to Portable. I've also completely redownloaded the game twice, once from a transfer from a Steam Deck that was able ot play the game. No matter what combo of Proton and env vars I try, the Death Stranding 2 splash screen opens, uses up all available memory, and crashes without generating a frame (checked via mangohud).

I think my issue is an engine issue, as other people on Windows as well have had this issue. No issues with any other Decima engine games (Horizon, DS1). This is my system's hardware, for what it's worth:

CPU: AMD Ryzen 7 7800X3D
GPU: AMD Radeon RX 7900 XT
RAM: 64GB
OS: bazzite-dx:latest
Proton: Bleeding Edge
Kernel: 6.17.7-ba28.fc43.x86_64
GPU Drivers: Mesa 26.0.2
DE: KDE on Wayland

EDIT:

PC Hotfix 1 has an identical startup issue, no differences. I'll continue testing, and try a different kernel + mesa combo

EDIT2:
Updating to the newest unstable image with:

Kernel: 6.19.8-200.ogc.fc43.x86_64
GPU Drivers: 26.0.3

results in no change.

My understanding is that the change mentioned in [#9593 (comment)](https://github.com/ValveSoftware/Proton/issues/9593#issuecomment-4103934483) should be for the out of the box experience, performance should be measured with no other workarounds as the baseline, including removing WINE_FSYNC_SIMULATE_SCHED_QUANTUM=1 WINE_FSYNC_YIELD_TO_WAITERS=1 from the launch options if you have that.

Without others workaround, the issue is not fixed for me.

This fixed the CPU usage for me: https://github.com/jas0n098/DS2NetFix

Copy both files into your game folder and set the launch arguments: WINEDLLOVERRIDES="xinput1_4=n,b" %command%

The game crash at startup before the initial launcher with your patch

Today's game patch + Proton Bleeding Edge (updated) was fixed excessive CPU usage for me, 18% when capped to 60fps (was 40-60%), 38% when uncapped (~130fps, was 80-90% and 70-80fps).

Without any envs.

Unfortunately I still have the problem with ds4 where the joystick don't want to go up in y axis no idea why. I dont have such issue on proton 8.

Game version 1.0.49 here. CPU usage is still >90%.

Today's game patch + Proton Bleeding Edge (updated) was fixed excessive CPU usage for me, 18% when capped to 60fps (was 40-60%), 38% when uncapped (~130fps, was 80-90% and 70-80fps). Without any envs.

I can confirm pretty much the same: I removed the FSYNC-related variables and latest Proton bleeding edge greatly reduced CPU usage. GPU usage is now roughly 90% at ~50 FPS (high settings, probably too much for my GPU eheh).

Switching to bleeding-edge has resolved the high cpu usage for me as well, but not the crashes. I determined initially that the crashes were occuring due to VRAM spikes that pushed it over 16GB. Lowering settings (and disabling Ray Tracing) provided enough head room that the VRAM spikes didn't consume all of the available VRAM, however the random crashes are still occuring. Aproximately every hour or so.

Launch variables are only: PROTON_ENABLE_WAYLAND=1 mangohud %command%

Specs:

OS: Omarchy 3.4.2
Motherboard: X870 AORUS ELITE WIFI7 (Default string-CF-WCP-ADO)
CPU: AMD Ryzen 7 9700X (16) @ 5.79 GHz
GPU: NVIDIA GeForce RTX 4070 Ti SUPER [Discrete]
Monitor: 2560x1440 in 32", 165 Hz [External]
Memory: 12.30 GiB / 30.95 GiB (40%)

Anybody else getting a high crash rate?

somewhat fixed it on my build too.
before on any proton build: 100% cpu usage on the main menu, 60% gpu usage ingame, 40 to 55 fps tops
.
with the bleeding edge patch now i reach 70 to 80 fps on very high and fsr3 with native AA at 1440p with some drops here and there, especially when moving the camera. cpu usage between 40/60% and gpu on the 90% mark. sadly the bleeding edge proton does not support FSR4 yet.
far from perfect but it works fine

OS: Arch Linux x86_64
Host: B850M Riptide WiFi
Kernel: Linux 6.19.9-zen1-1-zen
CPU: AMD Ryzen 7 9700X (8) @ 5.58 GHz
GPU 1: AMD Radeon RX 9070 XT [Discrete]
Memory: 32GB

Anybody else getting a high crash rate?

Yes, frequently when entering, exiting, or moving about the DHV Magellan (the game's mobile base of operations).

Running Bleeding Edge, no environment variables.

Not fixed for me unfortunately.

the fps are really low even on bleeding edge with flags. It's also on low settings

OS: CachyOS x86_64
HOST: X570 AORUS ELITE (-CF)
Kernel: Linux 6.19.7-1-cachyos
CPU: AMD Ryzen 7 5800X (16) @ 4.85 GHz
GPU 1: NVIDIA GeForce RTX 2080 Rev. A [Discrete]
Memory: 48 GB

No change after the latest patch and Proton bleeding edge, CPU still stays at 90+% and the issue is maybe the same, constant bombarding of the sync objects?

Extremely high CPU usage fixed for me. Funnily enough that had almost no impact on GPU utilization, so my GPU is still pulling 100W under the power limit with that bottleneck removed and CPU usage in the 35-45% range.

Replying to https://github.com/ValveSoftware/Proton/issues/9593#issuecomment-4105818164

Zero crashes in 25h, both before and after the CPU fix. Decently similar setups, maybe it's the 590 driver?

OS: CachyOS
KERNEL: 6.19.9-1-cachyos
CPU: AMD Ryzen 7 5800X3D 8-Core
GPU: NVIDIA GeForce RTX 4070 Ti
GPU DRIVER: NVIDIA 595.45.04
RAM: 32 GB

FYI patch in bleeding edge works if game is run from steam guys... (to stop spreading misinformation here about CPU usage only).

Not utilizing all GPU is not normal btw. Mine is 90% (4070, 595)

There is also bug graphical bug when you take wild animal at the back

Latest proton-cachyos(includes the newest cpu fix from bleeding edge) helps with cpu usage but framerate is still quite low compared to windows.

Hello @theLastOfCats, does that happen with mesa 26.0.3?

I'm on bazzite, didn't try unstable. But with mesa-git game not starting.

Hello @theLastOfCats, does that happen with mesa 26.0.3?

I'm on bazzite, didn't try unstable. But with mesa-git game not starting.

When I've used the mesa-git tool, I've always had to pass my full path into the Steam launch options, even though it's available in the PATH. So "/home/USER/mesa-git/mesa-git" VKD3D_CONFIG=nodxr %command%

EDIT: Today's unstable mesa from that tool, while I thought of trying it, did not work at all (no launcher like you said), so you may want to try one from a few days ago. Just delete and unzip an older release in the folder.

@kisak-valve @peterdwall

same result on mesa-git https://github.com/xXJSONDeruloXx/mesa-maker/releases/tag/mesa-20260317-063824

I've tried different methods to try and resolve the high CPU usage but nothing has worked except the logging trick. Despite trying latest CachyOS Proton or latest DW-Proton as that also added the bleeding edge functionally, none of those have worked out for me. Though enabling logging has made the game be a bit more playable.

I also tried that DS2NetFix method someone posted a bit back but running that through steam was making the game crash and a crash report prompt pop up.

Is the high CPU usage issue fixed? High end cpu's users, please, share your experience with the fix.

Is the high CPU usage issue fixed? High end cpu's users, please, share your experience with the fix.

I'm not sure if I fall in the 'High End' CPU bracket, but I went from 60-80% usage to 20-30% using bleeding-edge proton. AMD Ryzen 7 9700X overclocked.

Is anyone dealing with VRAM limits causing consistent crashes?

System:
OS: Pop!_OS 24.04 LTS
Kernel: 6.17.9-76061709-generic
CPU: Intel Core i7-9700K @ 3.60GHz
GPU: NVIDIA GeForce RTX 2070 SUPER (8GB VRAM)
GPU Driver: NVIDIA 580.119.02
RAM: 32GB
Proton: Bleeding Edge (latest)

The issue:
Game runs well with the latest game patch + Proton Bleeding Edge, solid FPS, no launch issues. But it crashes consistently after roughly an hour of gameplay regardless of graphics settings. Dropping from Medium all the way down to Portable shows little to no FPS or VRAM improvement, and VRAM stays maxed either way.

Crash logs confirm the cause. From the Decima crash log:

Video Usage: 5998MB  Tex Budget: 1847MB

The engine appears to not be scaling its VRAM budget correctly based on quality settings (to be honest I have no f-ing clue), the card is saturated at 8GB no matter what preset is active.

I understand 8GB is on the lower end, but this is the first time I've had a situation where a game runs fine performance-wise (90 FPS+) but crashes purely due to VRAM ceiling with no apparent way to reduce usage through settings.

Is this a known issue with how Decima manages VRAM budgets on sub-10GB cards? Any workarounds short of hardware upgrades?

The engine appears to not be scaling its VRAM budget correctly based on quality settings (to be honest I have no f-ing clue), the card is saturated at 8GB no matter what preset is active.

I have 16GB and I haven't seen the VRAM be below 9GB once. I was having VRAM spikes that exceeded 16GB so I disabled Ray Tracing and that resolved it for me. I am still getting frequent crashes at least every hour. Decima log varies but usually some version of [FatalError] Timed out waiting for GPU or [Crash] Unhandled exception at address 0x00000000420e1afc (code: 0xc0000005): "Access violation".

I understand 8GB is on the lower end, but this is the first time I've had a situation where a game runs fine performance-wise (90 FPS+) but crashes purely due to VRAM ceiling with no apparent way to reduce usage through settings.

A user above is using a 2080 and showing 5.6GB VRAM usage, what resolution are you playing at?

what resolution are you playing at?

Swapped between 2K and 1080p with no observable difference in VRAM usage or crash behaviour.

Worth noting I'm using the PICO upscaler + FSR frame gen, which isn't helping the VRAM budget, but my main concern is that usage doesn't seem to change regardless of what settings I apply. Getting similar crashes when the upscaler and FSR are off as well.

Decima log varies but usually some version of [FatalError] Timed out waiting for GPU or [Crash] Unhandled exception at address 0x00000000420e1afc (code: 0xc0000005): "Access violation".

This matches what I'm seeing consistently. Maybe it's not purely a VRAM ceiling then, could be related.

A user above is using a 2080 and showing 5.6GB VRAM usage

Similar numbers here. The issue seems to be that VRAM usage creeps upward and doesn't release anything from cache. Starts around 5.5GB, climbs to ~5.9GB after 20 minutes, then hard crashes around 6.3GB. That's what led me to assume it was a ceiling issue rather than a spike.

One thing I haven't tried yet: wiping the shader cache. I've swapped Proton versions several times throughout troubleshooting and suspect I may have accumulated stale shader compilations across versions. Will test and report back.

One thing I haven't tried yet: wiping the shader cache. I've swapped Proton versions several times throughout troubleshooting and suspect I may have accumulated stale shader compilations across versions. Will test and report back.

Let us know!

Worth noting I'm using the PICO upscaler + FSR frame gen, which isn't helping the VRAM budget, but my main concern is that usage doesn't seem to change regardless of what settings I apply. Getting similar crashes when the upscaler and FSR are off as well.

That is definitely not behavior I have observed on my end. Changing settings as an effect on VRAM and I can see the VRAM changing allocation in real time both up and down, although I do see a trend in the upward direction like you, but I don't think it is high enough to say it ran out of VRAM (since disabling Ray Tracing, I think the highest I have seen is 12.5GB)

Just in case it matters, my driver version is - 590.48.01

According to ProtonDB, some people are also having trouble with this weird drifting with the DualShock. It only doesn't appear on Steam Input, but then it feels slow. When playing on bleeding edge.

@Atmudia the controller issues seem (to me) to be the same as the first game. I've heard that it's an issue with the steam input translation layer, but I have the same experience with any controller regardless of the translation layer being used on both games.

If you are somehow able to find a fix, you'd be doing many of us a favor.

@DealingLace that's odd I dont have such problem in the Death Stranding 1 but yeah... unfortunately I have no idea how does wine look. I can look into that tho

@Ripped-Kanga cleared the shader cache and verified integrity, allowed the "new" vulkan shaders to compile, and unfortunately naught. Still getting those errors. Seems to actually run worse, somehow, even with the exact same settings. Very strange.

Updated my graphics drivers to 590 as well. Not sure how badly that would have affected it.

Just FYI.

In my case I get ring0 crashes on my PC during gameplay, only happens with this game.

amdgpu, everything updated, GE, Catchy and Experimental Bleeding Edge tested with same result.

@Ripped-Kanga cleared the shader cache and verified integrity, allowed the "new" vulkan shaders to compile, and unfortunately naught. Still getting those errors. Seems to actually run worse, somehow, even with the exact same settings. Very strange.

Updated my graphics drivers to 590 as well. Not sure how badly that would have affected it.

Thanks, I just tried tonight with the latest Cachy Proton and got around an hour of playtime before the same crash event occured.

I have alot of vram issues with this game where what kinds of settings does not matter for vram consumption, I have 3070 8gib and it always consumes 7.6 gib. I can run the game with smooth 60 fps but when interacting with menues or walking into certain areas the performace goes down to 20 fps and stay there. Logs from the Nvidia driver suggest that all vram is used up.

I'm getting these after some play time with Proton Experimental Edge:

[20175.768448] amdgpu 0000:03:00.0: amdgpu: Dumping IP State
[20175.769768] amdgpu 0000:03:00.0: amdgpu: Dumping IP State Completed
[20175.769803] amdgpu 0000:03:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
[20175.769804] amdgpu 0000:03:00.0: amdgpu: [drm] Check your /sys/class/drm/card0/device/devcoredump/data
[20175.769805] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 timeout, signaled seq=2490103, emitted seq=2490105
[20175.769806] amdgpu 0000:03:00.0: amdgpu:  Process DS2.exe pid 54488 thread vkd3d_queue pid 54561
[20175.769807] amdgpu 0000:03:00.0: amdgpu: Starting comp_1.1.1 ring reset
[20175.769812] amdgpu 0000:03:00.0: amdgpu: reset compute queue (1:1:1)
[20175.962834] amdgpu 0000:03:00.0: amdgpu: failed to wait on hqd deactivate
[20175.962838] amdgpu 0000:03:00.0: amdgpu: failed to reset legacy queue
[20175.962838] amdgpu 0000:03:00.0: amdgpu: fail(-110) to reset kcq and try pipe reset
[20175.962839] amdgpu 0000:03:00.0: amdgpu: The CPFW hasn't support pipe reset yet.
[20175.962840] amdgpu 0000:03:00.0: amdgpu: Ring comp_1.1.1 reset failed
[20175.962842] amdgpu 0000:03:00.0: amdgpu: GPU reset begin!. Source:  1
[20178.128949] amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE
[20178.128954] amdgpu 0000:03:00.0: amdgpu: failed to unmap legacy queue
[20180.128871] amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE
[20180.128874] amdgpu 0000:03:00.0: amdgpu: failed to unmap legacy queue
[20182.128789] amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE
[20182.128791] amdgpu 0000:03:00.0: amdgpu: failed to unmap legacy queue
[20184.128747] amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE
[20184.128750] amdgpu 0000:03:00.0: amdgpu: failed to unmap legacy queue
[20186.128667] amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE
[20186.128669] amdgpu 0000:03:00.0: amdgpu: failed to unmap legacy queue
[20188.128573] amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE
[20188.128576] amdgpu 0000:03:00.0: amdgpu: failed to unmap legacy queue
[20188.176679] amdgpu 0000:03:00.0: amdgpu: MODE1 reset
[20188.176682] amdgpu 0000:03:00.0: amdgpu: GPU mode1 reset
[20188.176737] amdgpu 0000:03:00.0: amdgpu: GPU smu mode1 reset
[20188.679435] amdgpu 0000:03:00.0: amdgpu: GPU reset succeeded, trying to resume
[20188.679544] [drm] PCIE GART of 512M enabled (table at 0x0000008000300000).
[20188.679580] amdgpu 0000:03:00.0: amdgpu: VRAM is lost due to GPU reset!
[20188.679581] amdgpu 0000:03:00.0: amdgpu: PSP is resuming...
[20188.749559] amdgpu 0000:03:00.0: amdgpu: reserve 0x1300000 from 0x85fc000000 for PSP TMR
[20188.897324] amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available
[20188.897327] amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: optional securedisplay ta ucode is not available
[20188.897329] amdgpu 0000:03:00.0: amdgpu: SMU is resuming...
[20188.897332] amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x0000003d, smu fw if version = 0x00000040, smu fw program = 0, smu fw version = 0x004e8300 (78.131.0)
[20188.897333] amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched
[20189.056173] amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully!
[20189.066513] amdgpu 0000:03:00.0: amdgpu: [drm] DMUB hardware initialized: version=0x07002F00
[20189.147848] amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[20189.147851] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[20189.147852] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[20189.147853] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
[20189.147853] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
[20189.147854] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
[20189.147855] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
[20189.147855] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
[20189.147856] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
[20189.147856] amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
[20189.147857] amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
[20189.147858] amdgpu 0000:03:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
[20189.147859] amdgpu 0000:03:00.0: amdgpu: ring vcn_unified_1 uses VM inv eng 1 on hub 8
[20189.147859] amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 4 on hub 8
[20189.147860] amdgpu 0000:03:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 14 on hub 0
[20189.152052] amdgpu 0000:03:00.0: amdgpu: GPU reset(1) succeeded!
[20189.152065] amdgpu 0000:03:00.0: amdgpu: [drm] *ERROR* Failed to initialize parser -125!
[20189.165561] amdgpu 0000:03:00.0: [drm] device wedged, but recovered through reset

I'm running RX7900XTX which has 24gb vram, it's not about vram size, the crash would happen.

Currently I only see the crash on this game so that I'm not convinced that it's my heat management is the problem.

Still seeing the same crash issue from before with PC Patch 1.1. I'll try swapping in my old 2070 this weekend to see if that makes a difference with regards to the memory leak.

EDIT: It works fine with the 2070, so definitely some sort of driver/engine/AMD GPU issue. It seems like it's incorrectly allocating VRAM.

I have alot of vram issues with this game where what kinds of settings does not matter for vram consumption, I have 3070 8gib and it always consumes 7.6 gib. I can run the game with smooth 60 fps but when interacting with menues or walking into certain areas the performace goes down to 20 fps and stay there. Logs from the Nvidia driver suggest that all vram is used up.

Updating to the new Nvidia drivers 595 solved my issues. Now it crashes from time to time but it is manageable comparable to bad performance.

So I got done playing through the game (v1.0.49.0) and I wanted to share an update here as to what method worked the best for me.

One of the primary issues that i was facing was high CPU usage and low GPU usage, and I did also have some crashes here and there. The method that worked the best for me was using this mod, https://github.com/jas0n098/DS2NetFix, that others mentioned in this thread already and using the launch argument WINEDLLOVERRIDES="d3d12=n,b" %command% .

One thing to note is that the mod didn't work right away and required changing the name from xinput1_4.dll to d3d12.dll. The usage of this mod significantly reduced the CPU usage and let the GPU utilization max out without being bottlenecked.

The Proton version that I used throughout the game was GE-Proton 10-34 as other versions like Proton-CachyOS and Proton-Experimental still caused issues for me. And as the CPU usage issue was resolved, I just ended up using the latest GE-Proton version.

System Specs if anyone is curious:
Distro: Arch Linux
Kernel: 6.19.8-arch1-1
RAM: 16 GB
GPU Driver: 4.6 Mesa 26.0.2-arch1.1
GPU: AMD Radeon RX 9060 XT (radeonsi, gfx1200, ACO, DRM 3.64, 6.19.8-arch1-1)
CPU: AMD Ryzen 5 5600 6-Core

Still seeing the same crash issue from before with PC Patch 1.1. I'll try swapping in my old 2070 this weekend to see if that makes a difference with regards to the memory leak.

EDIT: It works fine with the 2070, so definitely some sort of driver/engine/AMD GPU issue. It seems like it's incorrectly allocating VRAM.

It is incorrectly allocating VRAM and it seems to be to system ram. VRAM seems to stay low but system memory is getting filled up in seconds until the kernel panics. Not sure if it's a proton issue or vkd3d or mesa or whatever. But there is no fix. I've tried every combination of everything and nothing changes. Might be a game issue. No clue.

By trying to fix the issue with dualshock 4. I found the cause its because ValveSoftware/wine of this commit

Replying to https://github.com/ValveSoftware/Proton/issues/9593#issuecomment-4150383380

Yeah, it's the only clear link. I'm thinking Nixxes just needs to put a little more work in with some patches and things will hopefully improve.

On the 2070, I'm running into another issue, which is being stuck at a constant ~15-30FPS while in the game world, and 30-60FPS in menus. CPU never gets above ~40%, and the GPU is also not being fully utilized, and performance doesn't really correlate with any in-game actions or settings. 4K, Native AA, and settings on High is the same result as 1080p, Native, Portable, so it's not a settings issue. While this is running in a VM, other similar games run much better (both Horizon games, DS1). Even running it at Steam Deck default settings (720p, Portable, PICO + 30FPS scaling) is the exact same.

I might try it on a W11 VM and seeing what any differences may be.

EDIT: I get 40-60FPS most of the time with 1440p, High settings, and DLSS Quality on a W11 VM, and the GPU + CPU is fully utilized.

Replying to https://github.com/ValveSoftware/Proton/issues/9593#issuecomment-4164640094

I switched from a 5600x (cachyos v3 repo) to a 9800x3d and cachyos v4 repo, and now it just works with proton hotfix and nothing in launch commands. :/

Technical Bug Report: Death Stranding 2 Crash at 87% (GPU Timeout)
System Information:

OS: CachyOS (Arch Linux based)

Kernel: 6.19.9-2-cachyos

GPU: NVIDIA GeForce RTX 5070 Laptop GPU (Mobile)

Driver Version: 595.58.03 (NVIDIA Open Kernel Modules)

Desktop Environment: KDE Plasma (Wayland)

Proton Version: Proton-CachyOS / Proton GE-10-34

Problem Description:
The game crashes consistently during the initial shader compilation/loading screen at approximately 75-87%. The crash occurs right after the launcher settings are confirmed and the main engine initializes.

Error Messages captured:

Game Log: [FatalError] Timed out waiting for GPU

Wine/Proton Trace: Assertion failed! File: ../src-wine/dlls/winevulkan/loader_thunks.c Line: 2775. Expression: "!status && "vkCreateComputePipelines""

System Crash Code: 0xc0000005 (Access violation)

Attempted Workarounds (Failed):

Disabled DirectStorage (-noDirectStorage, PROTON_DIRECTSTORAGE=0).

Disabled NVIDIA NGX/DLSS via DLL Overrides (nvngx=d).

Forced Wayland support (PROTON_ENABLE_WAYLAND=1).

Limited VRAM upload (VKD3D_CONFIG=no_upload_hvv).

Tried various Proton versions (CachyOS, GE, Experimental).

Observations:
The issue seems specifically related to how the 595.58.03 driver handles asynchronous compute pipelines on the new RTX 50-series architecture. Previous driver versions (590.48.x) on similar hardware did not exhibit this specific "GPU Timeout" during the 87% initialization phase.

23:19:17:921 (00000296) > [Startup] DEATH STRANDING 2: ON THE BEACH
23:19:17:921 (00000296) > [Startup] ==============
23:19:17:921 (00000296) > [Startup] 
23:19:17:921 (00000296) > [Startup] Build: v1.1.53.0
23:19:17:921 (00000296) > [Startup] Windows 10.0 (build 19045.5796)
23:19:17:921 (00000296) > [Startup] Distribution platform: Steam
23:19:17:921 (00000296) > [Startup] Game directory: C:\users\<username>\Documents\DEATH STRANDING 2 - ON THE BEACH\
23:19:17:921 (00000296) > [Startup] Working directory: Z:\home\valentinef\.local\share\Steam\steamapps\common\DEATH STRANDING 2 - ON THE BEACH
23:19:17:921 (00000296) > [Startup] Run ID: 3200-D133-0ACE-0193
23:19:17:921 (00000296) > [Startup] 
23:19:17:921 (00000296) > [Startup] Memory statistics:
23:19:17:921 (00000296) > [Startup]   Total RAM = 30.6 GB (31368 MB)
23:19:17:921 (00000296) > [Startup]   Avail RAM = 22.9 GB (23432 MB)
23:19:17:921 (00000296) > [Startup]   Total virtual memory = 131072.0 GB (134217727 MB)
23:19:17:921 (00000296) > [Startup]   Avail virtual memory = 131071.6 GB (134217281 MB)
23:19:17:921 (00000296) > [Startup]   Total page file = 61.3 GB (62736 MB)
23:19:17:921 (00000296) > [Startup]   Avail page file = 53.5 GB (54800 MB)
23:19:17:921 (00000296) > [Startup] 
23:19:17:921 (00000296) > [Startup] RAM info:
23:19:17:921 (00000296) > [Startup] 
23:19:17:921 (00000296) > [Steam] Wine version: "Proton10-34"
23:19:17:921 (00000296) > [Steam] Initializing.
23:19:17:954 (00000296) > [Steam] Successfully initialized.
23:19:17:954 (00000296) > [Steam] Currently connected to 0 remote sessions
23:19:17:955 (00000296) > [Steam] Steam beta branch: unknown
23:19:18:376 (00000296) > [NxApp] PreInit
23:19:18:376 (00000296) > [SwapChain] Initializing...
23:19:18:376 (00000296) > [DXGI] Initializing...
23:19:18:758 (00000296) > [NxApp] Streamline was successfully initialized.
23:19:18:758 (00000296) > [DXGI] Successfully initialized.
23:19:18:758 (00000296) > [Render] Enumerating adapters:
23:19:18:758 (00000296) > [Render]      Adapter 0:
23:19:18:758 (00000296) > [Monitor]             Description             : NVIDIA GeForce RTX 5070 Laptop GPU
23:19:18:758 (00000296) > [Monitor]             Vendor                  : nVidia (10de)
23:19:18:758 (00000296) > [Monitor]             Device                  : 2d58
23:19:18:758 (00000296) > [Monitor]             Sub system              : 0
23:19:18:758 (00000296) > [Monitor]             Revision                : 0
23:19:18:758 (00000296) > [Monitor]             Dedicated Video Memory  : 8151 MB
23:19:18:758 (00000296) > [Monitor]             Dedicated System Memory : 0000 MB
23:19:18:758 (00000296) > [Monitor]             Shared System Memory    : 23526 MB
23:19:18:758 (00000296) > [Monitor] 
23:19:18:758 (00000296) > [Render] Loading NVAPI...
23:19:18:759 (00000296) > [Render] Done loading NVAPI
23:19:18:759 (00000296) > [Render] Enumerating monitors:
23:19:18:759 (00000296) > [Render]      Monitor 0: handle = 0000000000000001, size aspect = 1.60, resolution aspect = 1.60, rounded aspect = 1.60
23:19:18:759 (00000296) > [Render]      Monitor 1: handle = 0000000000000002, size aspect = 1.60, resolution aspect = 1.60, rounded aspect = 1.60
23:19:18:759 (00000296) > [Render] 
23:19:18:760 (00000296) > [Render] Failed to get the nvidia display output ID
23:19:18:760 (00000296) > [Render]      Monitor handle = 0000000000000001, pixel aspect ratio = 1.00
23:19:18:762 (00000296) > [Render] Failed to get the nvidia display output ID
23:19:18:762 (00000296) > [Render]      Monitor handle = 0000000000000002, pixel aspect ratio = 1.00
23:19:18:762 (00000296) > [SwapChain] Successfully initialized.
23:19:18:762 (00000296) > [Render] Enumerating Display Modes:
23:19:18:762 (00000296) > [Render] Querying NVAPI for Surround modes
23:19:18:762 (00000296) > [Render] NvAPI_Mosaic_GetDisplayViewportsByResolution() - no surround modes detected
23:19:18:762 (00000296) > [Render] Querying NVAPI for Surround modes
23:19:18:762 (00000296) > [Render] NvAPI_Mosaic_GetDisplayViewportsByResolution() - no surround modes detected
23:19:18:762 (00000296) > [Render]      Monitor '1 (NVIDIA GeForce RTX 5070 Laptop GPU(1))' (0000000000000001): rect(0 2560 0 1600)
23:19:18:762 (00000296) > [Render]              - Mode  0 : 1920 x 1080 @  60 Hz, stereo = 0, hdr = 0 exclusive = 0
23:19:18:762 (00000296) > [Render]              - Mode  1 : 1920 x 1080 @ 240 Hz, stereo = 0, hdr = 0 exclusive = 0
23:19:18:762 (00000296) > [Render]              - Mode  2 : 1920 x 1200 @  60 Hz, stereo = 0, hdr = 0 exclusive = 0
23:19:18:762 (00000296) > [Render]              - Mode  3 : 1920 x 1200 @ 240 Hz, stereo = 0, hdr = 0 exclusive = 0
23:19:18:762 (00000296) > [Render]              - Mode  4 : 1920 x 1280 @  60 Hz, stereo = 0, hdr = 0 exclusive = 0
23:19:18:762 (00000296) > [Render]              - Mode  5 : 1920 x 1280 @ 240 Hz, stereo = 0, hdr = 0 exclusive = 0
23:19:18:762 (00000296) > [Render]              - Mode  6 : 1920 x 1440 @  60 Hz, stereo = 0, hdr = 0 exclusive = 0
23:19:18:762 (00000296) > [Render]              - Mode  7 : 1920 x 1440 @ 240 Hz, stereo = 0, hdr = 0 exclusive = 0
23:19:18:762 (00000296) > [Render]              - Mode  8 : 2048 x 1152 @  60 Hz, stereo = 0, hdr = 0 exclusive = 0
23:19:18:762 (00000296) > [Render]              - Mode  9 : 2048 x 1152 @ 240 Hz, stereo = 0, hdr = 0 exclusive = 0
23:19:18:762 (00000296) > [Render]              - Mode 10 : 2048 x 1536 @  60 Hz, stereo = 0, hdr = 0 exclusive = 0
23:19:18:762 (00000296) > [Render]              - Mode 11 : 2048 x 1536 @ 240 Hz, stereo = 0, hdr = 0 exclusive = 0
23:19:18:763 (00000296) > [Render]              - Mode 12 : 2560 x 1080 @  60 Hz, stereo = 0, hdr = 0 exclusive = 0
23:19:18:763 (00000296) > [Render]              - Mode 13 : 2560 x 1080 @ 240 Hz, stereo = 0, hdr = 0 exclusive = 0
23:19:18:763 (00000296) > [Render]              - Mode 14 : 2560 x 1440 @  60 Hz, stereo = 0, hdr = 0 exclusive = 0
23:19:18:763 (00000296) > [Render]              - Mode 15 : 2560 x 1440 @ 240 Hz, stereo = 0, hdr = 0 exclusive = 0
23:19:18:763 (00000296) > [Render]              - Mode 16 : 2560 x 1600 @  60 Hz, stereo = 0, hdr = 0 exclusive = 0
23:19:18:763 (00000296) > [Render]              - Mode 17 : 2560 x 1600 @ 240 Hz, stereo = 0, hdr = 0 exclusive = 0
23:19:18:763 (00000296) > [Render] ***** Additional Monitor Output Info *****
23:19:18:763 (00000296) > [Render]              BitsPerColor: 10
23:19:18:763 (00000296) > [Render]              Primaries: R=0.6400;0.3300  G=0.3000;0.6000  B=0.1500;0.0600  White-Point=0.3127;0.3290
23:19:18:763 (00000296) > [Render]              HDR: No (Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709)
23:19:18:763 (00000296) > [Render]              Luminance: Min=0.5000 Max=270.0000 MaxFullFrame=270.0000
23:19:18:763 (00000296) > [Render] ******************************************
23:19:18:763 (00000296) > [Render]      Monitor '2 (NVIDIA GeForce RTX 5070 Laptop GPU(1))' (0000000000000002): rect(2560 4960 0 1350)
23:19:18:763 (00000296) > [Render]              - Mode  0 : 1920 x 1080 @  60 Hz, stereo = 0, hdr = 0 exclusive = 0
23:19:18:763 (00000296) > [Render]              - Mode  1 : 1920 x 1080 @ 143 Hz, stereo = 0, hdr = 0 exclusive = 0
23:19:18:763 (00000296) > [Render]              - Mode  2 : 1920 x 1200 @  60 Hz, stereo = 0, hdr = 0 exclusive = 0
23:19:18:763 (00000296) > [Render]              - Mode  3 : 1920 x 1200 @ 143 Hz, stereo = 0, hdr = 0 exclusive = 0
23:19:18:763 (00000296) > [Render]              - Mode  4 : 1920 x 1280 @  60 Hz, stereo = 0, hdr = 0 exclusive = 0
23:19:18:763 (00000296) > [Render]              - Mode  5 : 1920 x 1280 @ 143 Hz, stereo = 0, hdr = 0 exclusive = 0
23:19:18:763 (00000296) > [Render]              - Mode  6 : 2048 x 1152 @  60 Hz, stereo = 0, hdr = 0 exclusive = 0
23:19:18:763 (00000296) > [Render]              - Mode  7 : 2048 x 1152 @ 143 Hz, stereo = 0, hdr = 0 exclusive = 0
23:19:18:763 (00000296) > [Render]              - Mode  8 : 2400 x 1350 @  60 Hz, stereo = 0, hdr = 0 exclusive = 0
23:19:18:763 (00000296) > [Render]              - Mode  9 : 2400 x 1350 @ 143 Hz, stereo = 0, hdr = 0 exclusive = 0
23:19:18:763 (00000296) > [Render] ***** Additional Monitor Output Info *****
23:19:18:763 (00000296) > [Render]              BitsPerColor: 10
23:19:18:763 (00000296) > [Render]              Primaries: R=0.6400;0.3300  G=0.3000;0.6000  B=0.1500;0.0600  White-Point=0.3127;0.3290
23:19:18:763 (00000296) > [Render]              HDR: No (Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709)
23:19:18:763 (00000296) > [Render]              Luminance: Min=0.5000 Max=270.0000 MaxFullFrame=270.0000
23:19:18:763 (00000296) > [Render] ******************************************
23:19:18:763 (00000296) > [Render] 
23:19:19:562 (00000296) > [NxApp] Querying GPU Driver Info...
23:19:19:562 (00000296) > [NxApp] Enumerating available display adapters:
23:19:19:563 (00000296) > [NxApp]               NVIDIA GeForce RTX 5070 Laptop GPU (active)
23:19:19:563 (00000296) > [NxApp] Successfully found GPU Driver Info
23:19:19:563 (00000296) > [D3D] Max supported feature level: 11.0
23:19:19:563 (00000296) > [Render] Disabled D3D12 experimentals
23:19:20:031 (00000296) > [Render] VMEM Budget: 7309 MB
23:19:20:031 (00000296) > [Render] VMEM Available: 7277 MB
23:19:20:260 (00000296) > [Render] GPU node count: 1
23:19:20:260 (00000296) > [NxD3D] RAY TRACING ENABLED: Ray Tracing Tier 1.1 support detected
23:19:20:260 (00000296) > [NxLowLatency] Reflex support result:Result::eOk
23:19:20:260 (00000296) > [NxFrameGen] DLSSG support result: Result::eOk
23:19:20:260 (00000296) > [NxFrameGen] Max generated DLSSG frames: 3
23:19:20:260 (00000296) > [NxFrameGen] DLSSG vsync supported: 0
23:19:20:260 (00000296) > [NxApp] PreInit successful.
23:19:20:264 (00000296) > [NxLowLatency] XeLL init, code = 0
23:19:20:264 (00000296) > [NxLowLatency] Anti-Lag2 not supported. Error code (-2147024890)
23:19:20:277 (00000296) > [NxUpscaler] SL DLSS support: Result::eOk
23:19:20:277 (00000296) > [NxUpscaler] XeSS init, code = 0
23:19:20:332 (00000296) > [Input] Keyboard language: "English (United States)" (id: 1033)
23:19:20:334 (00000296) > [Input] Mouse               "Wine HID device"   id 1 buttons 5 sampleRate 0 horizontalWheel no
23:19:20:334 (00000296) > [Input] Keyboard            "Wine HID device"   type 0 subType 0 mode 1 function 12 indicators 3 total 101
23:19:20:357 (00000296) > [Input] Trying to load libScePad from C:\ProgramData\Sony Interactive Entertainment Inc\PSPC_SDK\S22\5.50.00.11\libScePad.dll
23:19:20:364 (00000296) > [Input] Using LibScePad
23:19:20:372 (00000296) > [XInput] Enumerating available xusb hid devices:

23:19:23:955 (00000296) > [NxLowLatency] Reflex support result:Result::eOk
23:19:23:955 (00000296) > [NxFrameGen] DLSSG support result: Result::eOk
23:19:23:955 (00000296) > [NxFrameGen] Max generated DLSSG frames: 3
23:19:23:955 (00000296) > [NxFrameGen] DLSSG vsync supported: 0
23:19:23:955 (00000296) > [Settings] Applied settings to preset: H
23:19:23:956 (00000296) > [NxApp] Driver Desc: NVIDIA GeForce RTX 5070 Laptop GPU
23:19:23:956 (00000296) > [NxApp] Driver Version: 999.99
23:19:23:956 (00000296) > [**************************************************Display + Graphics Settings**************************************************] 
23:19:23:956 (00000296) > [Settings] DirectX Version: 12
23:19:23:956 (00000296) > [Settings] Window mode: Fullscreen
23:19:23:956 (00000296) > [Settings] Fullscreen display mode:
23:19:23:956 (00000296) > [Settings]    Displaying on monitor: 1
23:19:23:956 (00000296) > [Settings]    Resolution: 1920x1080
23:19:23:956 (00000296) > [Settings]    HDR: Off
23:19:23:956 (00000296) > [Settings]    OS reported Refresh rate: 143
23:19:23:956 (00000296) > [Settings]    VSync: Off
23:19:23:956 (00000296) > [Settings]    Low Latency: None
23:19:23:956 (00000296) > [Settings]    Frame generation: None
23:19:23:956 (00000296) > [Settings]    Max generated frames: 0
23:19:23:956 (00000296) > [Settings]    Dynamic resolution FPS target: 60
23:19:23:956 (00000296) > [Settings] Anti aliasing: PICO
23:19:23:956 (00000296) > [Settings] Upscale method: PICO
23:19:23:956 (00000296) > [Settings] Upscale quality: Dynamic
23:19:23:956 (00000296) > [Settings] Upscale sharpen value: 0.000000
23:19:23:956 (00000296) > [Settings] Graphics Options:
23:19:23:956 (00000296) > [Settings]    Texture Quality: High
23:19:23:956 (00000296) > [Settings]    Texture Filtering: Anisotropic8x
23:19:23:956 (00000296) > [Settings]    Shadow Quality: High
23:19:23:956 (00000296) > [Settings]    Shadow Res: High
23:19:23:956 (00000296) > [Settings]    Depth of Field: High
23:19:23:956 (00000296) > [Settings]    Level of Detail: High
23:19:23:956 (00000296) > [Settings]    Terrain Quality: High
23:19:23:956 (00000296) > [Settings]    Clouds Quality: High
23:19:23:956 (00000296) > [Settings]    Ambient Occlusion: SSAO_High
23:19:23:956 (00000296) > [Settings]    Reflections: High
23:19:23:956 (00000296) > [Settings]    Translucency Quality: Default

23:19:23:956 (00000296) > [Settings]    Bloom: On
23:19:23:956 (00000296) > [Settings]    Vignette: On
23:19:23:956 (00000296) > [Settings]    Motion Blur: 0.500000
23:19:23:956 (00000296) > [Settings]    FOV Correction: 1.000000
23:19:23:956 (00000296) > [Settings]    Sharpness: 0.500000
23:19:23:956 (00000296) > [Settings]    Lens Flares: On
23:19:23:956 (00000296) > [Settings]    Screen Space Shadows: On
23:19:23:956 (00000296) > [**************************************************Display + Graphics Settings**************************************************] 
23:19:23:956 (00000296) > [NxApp] Initializing module prefetch thread
23:19:23:956 (00000296) > [NxProcessorInfo] Processor info:
23:19:23:956 (00000296) > [NxProcessorInfo]     Description:                    AMD Ryzen 9 8945HX with Radeon Graphics
23:19:23:956 (00000296) > [NxProcessorInfo]     Group Count:            1
23:19:23:956 (00000296) > [NxProcessorInfo]     Physical Core:          16
23:19:23:956 (00000296) > [NxProcessorInfo]     Logical  Core:          32
23:19:23:956 (00000296) > [NxProcessorInfo]     Distinct L3 Cache:      2
23:19:23:956 (00000296) > [NxProcessorInfo]     Family:                 25
23:19:23:956 (00000296) > [NxProcessorInfo]     Model:                  97
23:19:23:956 (00000296) > [NxProcessorInfo]     Name:                   AMD Ryzen 9 8945HX with Radeon Graphics        
23:19:23:956 (00000296) > [NxProcessorInfo]     AVX:                    1
23:19:23:956 (00000296) > [NxProcessorInfo]     F16C:                   1
23:19:23:956 (00000296) > [NxProcessorInfo]     AVX2:                   1
23:19:23:956 (00000296) > [NxProcessorInfo]     NormalAffinity(auto)
23:19:24:103 (00000296) > [NxApp] Creating window...
23:19:24:160 (00000752) > [GameWindow] UpdateState bVisible true
23:19:24:166 (00000296) > [NxApp] Window created.
23:19:24:166 (00000296) > [NxApp] Initializing swapchain...
23:19:24:166 (00000648) > [SwapChain] Creating...
23:19:24:166 (00000648) > [NxSwapChainImpl] Swapchain native backbuffer (windows) resolution: 2400x1350
23:19:24:180 (00000648) > [DXGI] Created swapchain.
23:19:24:185 (00000648) > [SwapChain] Gamma correction is enabled.
23:19:24:185 (00000648) > [SwapChain] Successfully created.
23:19:24:185 (00000648) > [NxSwapChainImpl] Swapchain native backbuffer (windows) resolution: 2400x1350
23:19:24:185 (00000296) > [NxApp] Swapchain initialized
23:19:24:185 (00000296) > [NxApp] Initializing renderer...
23:19:24:186 (00000296) > [NxApp] Renderer initialized
23:19:24:186 (00000296) > [Render] UMA = False, CacheCoherentUMA = False
23:19:24:186 (00000296) > [Render] Tight alignment support: yes
23:19:24:299 (00000296) > [PSO] Loaded 25277 shader hashes, 40837 descriptors from appdir:HashDB.bin
23:19:24:299 (00000296) > [PSO] Loaded 14 shader hashes, 70 descriptors from appdata:UserHashDB.bin
23:19:24:392 (00000296) > [PSN Account Linking] [PSN] PSPC initialization failed: 8a800111
23:19:24:393 (00000296) > [PSN Account Linking] [PSN] Setting device data collection setting failed 8a80010d
23:19:24:393 (00000296) > [PSN Account Linking] Failed to update data collection policy to PSPC, error=0
23:19:24:393 (00000296) > [NxStorage] Storage Drive Type is HDD.
23:19:24:393 (00000296) > [NXStorage] Storage Drive (Z:) free disk space is 16444125184 (bytes).

23:19:24:393 (00000296) > [NXStorageReadDevice] Failed to initialize DirectStorage, using fallback.

23:19:24:767 (00000472) > [PSN Account Linking] [PSN] Setting device data collection setting failed 8a80010d
23:19:24:767 (00000472) > [PSN Account Linking] Failed to update data collection policy to PSPC, error=0
23:19:25:491 (00000484) > [PSN Account Linking] [PSN] Setting device data collection setting failed 8a80010d
23:19:25:491 (00000484) > [PSN Account Linking] Failed to update data collection policy to PSPC, error=0
23:19:25:493 (00000488) > [PSN Account Linking] [PSN] Setting device data collection setting failed 8a80010d
23:19:25:493 (00000492) > [PSN Account Linking] [PSN] Setting device data collection setting failed 8a80010d
23:19:25:493 (00000488) > [PSN Account Linking] Failed to update data collection policy to PSPC, error=0
23:19:25:493 (00000492) > [PSN Account Linking] Failed to update data collection policy to PSPC, error=0
23:19:25:493 (00000496) > [PSN Account Linking] [PSN] Setting device data collection setting failed 8a80010d
23:19:25:493 (00000496) > [PSN Account Linking] Failed to update data collection policy to PSPC, error=0
23:19:25:901 (00000296) > [Steam] Stats received: 1
23:19:25:901 (00000296) > [Settings] Applied settings to preset: H
23:19:25:901 (00000648) > [NxSwapChainImpl] Swapchain native backbuffer (windows) resolution: 2400x1350
23:19:25:901 (00000296) > [NxLowLatency] Reflex support result:Result::eOk
23:19:25:901 (00000296) > [NxFrameGen] DLSSG support result: Result::eOk
23:19:25:901 (00000296) > [NxFrameGen] Max generated DLSSG frames: 3
23:19:25:901 (00000296) > [NxFrameGen] DLSSG vsync supported: 0
23:19:25:901 (00000296) > [Settings] New display settings are:
23:19:25:901 (00000296) > [**************************************************Display + Graphics Settings**************************************************] 
23:19:25:901 (00000296) > [Settings] DirectX Version: 12
23:19:25:901 (00000296) > [Settings] Window mode: Fullscreen
23:19:25:901 (00000296) > [Settings] Fullscreen display mode:
23:19:25:901 (00000296) > [Settings]    Displaying on monitor: 1
23:19:25:901 (00000296) > [Settings]    Resolution: 1920x1080
23:19:25:901 (00000296) > [Settings]    HDR: Off
23:19:25:901 (00000296) > [Settings]    OS reported Refresh rate: 143
23:19:25:901 (00000296) > [Settings]    VSync: Off
23:19:25:901 (00000296) > [Settings]    Low Latency: None
23:19:25:901 (00000296) > [Settings]    Frame generation: None
23:19:25:901 (00000296) > [Settings]    Max generated frames: 0
23:19:25:901 (00000296) > [Settings]    Dynamic resolution FPS target: 60
23:19:25:901 (00000296) > [Settings] Anti aliasing: PICO
23:19:25:901 (00000296) > [Settings] Upscale method: PICO
23:19:25:901 (00000296) > [Settings] Upscale quality: Dynamic
23:19:25:901 (00000296) > [Settings] Upscale sharpen value: 0.000000
23:19:25:901 (00000296) > [Settings] Graphics Options:
23:19:25:901 (00000296) > [Settings]    Texture Quality: High
23:19:25:901 (00000296) > [Settings]    Texture Filtering: Anisotropic8x
23:19:25:901 (00000296) > [Settings]    Shadow Quality: High
23:19:25:901 (00000296) > [Settings]    Shadow Res: High
23:19:25:901 (00000296) > [Settings]    Depth of Field: High
23:19:25:901 (00000296) > [Settings]    Level of Detail: High
23:19:25:901 (00000296) > [Settings]    Terrain Quality: High
23:19:25:901 (00000296) > [Settings]    Clouds Quality: High
23:19:25:901 (00000296) > [Settings]    Ambient Occlusion: SSAO_High
23:19:25:901 (00000296) > [Settings]    Reflections: High
23:19:25:901 (00000296) > [Settings]    Translucency Quality: Default

23:19:25:901 (00000296) > [Settings]    Bloom: On
23:19:25:901 (00000296) > [Settings]    Vignette: On
23:19:25:901 (00000296) > [Settings]    Motion Blur: 0.500000
23:19:25:901 (00000296) > [Settings]    FOV Correction: 1.000000
23:19:25:901 (00000296) > [Settings]    Sharpness: 0.500000
23:19:25:901 (00000296) > [Settings]    Lens Flares: On
23:19:25:901 (00000296) > [Settings]    Screen Space Shadows: On
23:19:25:901 (00000296) > [**************************************************Display + Graphics Settings**************************************************] 
23:19:25:901 (00000296) > [Settings] End of settings.
23:19:25:904 (00000296) > [NxApp] Finished enforcing display settings
23:19:26:884 (00000904) > [PSN Account Linking] AuthenticationRequest: 200
23:19:26:887 (00000296) > [PSN Account Linking] Auth Complete
23:19:27:065 (00000920) > [PSN Account Linking] GetConfigData: 200
23:19:27:065 (00000780) > [PSN Account Linking]     registration: enabled
23:19:27:426 (00000920) > [PSN Account Linking] GetRegisteredAccount: 200
23:19:33:177 (00000424) > [FatalError] Fatal error occurred: 
23:19:33:177 (00000424) > [FatalError] Timed out waiting for GPU
23:19:33:177 (00000424) > [Crash] Memory statistics:
23:19:33:177 (00000424) > [Crash]   Total RAM = 30.6 GB (31368 MB)
23:19:33:177 (00000424) > [Crash]   Avail RAM = 17.3 GB (17670 MB)
23:19:33:177 (00000424) > [Crash]   Total virtual memory = 131072.0 GB (134217727 MB)
23:19:33:177 (00000424) > [Crash]   Avail virtual memory = 131066.3 GB (134211854 MB)
23:19:33:177 (00000424) > [Crash]   Total page file = 61.3 GB (62736 MB)
23:19:33:177 (00000424) > [Crash]   Avail page file = 47.9 GB (49038 MB)
23:19:33:177 (00000424) > [Crash] 
23:19:33:177 (00000424) > [Crash] RAM info:
23:19:33:177 (00000424) > [Crash] Unhandled exception at address 0x00000000f4af223c (code: 0xc0000005): "Access violation"
23:19:40:177 (00000424) > [Crash] Created minidump at "C:\users\<username>\Documents\DEATH STRANDING 2 - ON THE BEACH\DEATH STRANDING 2 - ON THE BEACH-v1.1.53.0 2026-04-01-23-19-38.mdmp".

It probably needs some more testing but the 1.2 Patch improved performance (at least for me)
Patch mentions "Steam Deck improvements"

While the 1.2 patch might have improved performance for some, it hasn't addressed the critical initialization crashes on newer hardware. I am still experiencing a consistent crash at 87% (GPU Timeout/Access Violation) on an RTX 5070 Laptop GPU with the latest 595.58.03 drivers.

It appears that the issue is not related to game optimization itself, but rather to how Proton (vkd3d) handles asynchronous compute pipelines or shader compilation on the Blackwell architecture.

For me on the RTX 5070, the game remains unplayable regardless of the 1.2 patch. Attached are my logs for further investigation. In logs there are few problems with hardware detection. For example it is not detect that I have SSD and thinks it is HDD but the main error is that it has a time out response form GPU, so it is looks like the compatibility issue, not game. But thank you for your response)

Update: After installing the 1.2 patch, the situation has worsened for the RTX 5070 Laptop GPU (Driver 595.58.03).

Previously, the game would reach 87% before crashing. Now, it crashes immediately after the 'Death Stranding 2: On the Beach' splash screen, right after the launcher. This confirms that the recent improvements likely introduced new conflicts with the vkd3d-proton shader compilation or asynchronous compute on NVIDIA's Blackwell architecture.

The game is now even further from being playable on this hardware. Attached is the latest log showing the immediate crash after the splash screen
Log:
20:13:11:795 (00000316) > [Startup] DEATH STRANDING 2: ON THE BEACH
20:13:11:795 (00000316) > [Startup] ==============
20:13:11:795 (00000316) > [Startup]
20:13:11:795 (00000316) > [Startup] Build: v1.2.57.0
20:13:11:795 (00000316) > [Startup] Windows 10.0 (build 19045.5796)
20:13:11:795 (00000316) > [Startup] Distribution platform: Steam
20:13:11:795 (00000316) > [Startup] Game directory: C:\users<username>\Documents\DEATH STRANDING 2 - ON THE BEACH
20:13:11:795 (00000316) > [Startup] Working directory: Z:\home\valentinef.local\share\Steam\steamapps\common\DEATH STRANDING 2 - ON THE BEACH
20:13:11:795 (00000316) > [Startup] Run ID: 5520-FC15-6090-01CC
20:13:11:795 (00000316) > [Startup]
20:13:11:795 (00000316) > [Startup] Memory statistics:
20:13:11:795 (00000316) > [Startup] Total RAM = 30.6 GB (31368 MB)
20:13:11:795 (00000316) > [Startup] Avail RAM = 23.5 GB (24050 MB)
20:13:11:795 (00000316) > [Startup] Total virtual memory = 131072.0 GB (134217727 MB)
20:13:11:795 (00000316) > [Startup] Avail virtual memory = 131071.6 GB (134217284 MB)
20:13:11:795 (00000316) > [Startup] Total page file = 61.3 GB (62736 MB)
20:13:11:795 (00000316) > [Startup] Avail page file = 54.1 GB (55418 MB)
20:13:11:795 (00000316) > [Startup]
20:13:11:796 (00000316) > [Startup] RAM info:
20:13:11:796 (00000316) > [Startup]
20:13:11:796 (00000316) > [Steam] Initializing.
20:13:11:839 (00000316) > [Steam] Successfully initialized.
20:13:11:839 (00000316) > [Steam] Currently connected to 0 remote sessions
20:13:11:840 (00000316) > [Steam] Steam beta branch: unknown
20:13:12:225 (00000316) > [CRS] Client ID: e1a6e478-bbbb-463a-a13a-de3000541eab
20:13:12:225 (00000316) > [CRS] Session ID: 795b9a46-00cb-422a-8612-e4edb92e0d6b
20:13:12:301 (00000316) > [NxApp] PreInit
20:13:12:301 (00000316) > [SwapChain] Initializing...
20:13:12:301 (00000316) > [DXGI] Initializing...
20:13:12:745 (00000316) > [NxApp] Streamline was successfully initialized.
20:13:12:745 (00000316) > [DXGI] Successfully initialized.
20:13:12:745 (00000316) > [Render] Enumerating adapters:
20:13:12:745 (00000316) > [Render] Adapter 0:
20:13:12:745 (00000316) > [Monitor] Description : NVIDIA GeForce RTX 5070 Laptop GPU
20:13:12:745 (00000316) > [Monitor] Vendor : nVidia (10de)
20:13:12:745 (00000316) > [Monitor] Device : 2d58
20:13:12:745 (00000316) > [Monitor] Sub system : 0
20:13:12:745 (00000316) > [Monitor] Revision : 0
20:13:12:745 (00000316) > [Monitor] Dedicated Video Memory : 8151 MB
20:13:12:745 (00000316) > [Monitor] Dedicated System Memory : 0000 MB
20:13:12:745 (00000316) > [Monitor] Shared System Memory : 23526 MB
20:13:12:745 (00000316) > [Monitor]
20:13:12:745 (00000316) > [Render] Loading NVAPI...
20:13:12:746 (00000316) > [Render] Done loading NVAPI
20:13:12:746 (00000316) > [Render] Enumerating monitors:
20:13:12:746 (00000316) > [Render] Monitor 0: handle = 0000000000000001, size aspect = 1.60, resolution aspect = 1.60, rounded aspect = 1.60
20:13:12:746 (00000316) > [Render] Monitor 1: handle = 0000000000000002, size aspect = 1.60, resolution aspect = 1.60, rounded aspect = 1.60
20:13:12:746 (00000316) > [Render]
20:13:12:747 (00000316) > [Render] Failed to get the nvidia display output ID
20:13:12:747 (00000316) > [Render] Monitor handle = 0000000000000001, pixel aspect ratio = 1.00
20:13:12:749 (00000316) > [Render] Failed to get the nvidia display output ID
20:13:12:749 (00000316) > [Render] Monitor handle = 0000000000000002, pixel aspect ratio = 1.00
20:13:12:749 (00000316) > [SwapChain] Successfully initialized.
20:13:12:749 (00000316) > [Render] Enumerating Display Modes:
20:13:12:749 (00000316) > [Render] Querying NVAPI for Surround modes
20:13:12:749 (00000316) > [Render] NvAPI_Mosaic_GetDisplayViewportsByResolution() - no surround modes detected
20:13:12:749 (00000316) > [Render] Querying NVAPI for Surround modes
20:13:12:749 (00000316) > [Render] NvAPI_Mosaic_GetDisplayViewportsByResolution() - no surround modes detected
20:13:12:749 (00000316) > [Render] Monitor '1 (NVIDIA GeForce RTX 5070 Laptop GPU(1))' (0000000000000001): rect(0 2560 0 1600)
20:13:12:750 (00000316) > [Render] - Mode 0 : 1920 x 1080 @ 60 Hz, stereo = 0, hdr = 0 exclusive = 0
20:13:12:750 (00000316) > [Render] - Mode 1 : 1920 x 1080 @ 240 Hz, stereo = 0, hdr = 0 exclusive = 0
20:13:12:750 (00000316) > [Render] - Mode 2 : 1920 x 1200 @ 60 Hz, stereo = 0, hdr = 0 exclusive = 0
20:13:12:750 (00000316) > [Render] - Mode 3 : 1920 x 1200 @ 240 Hz, stereo = 0, hdr = 0 exclusive = 0
20:13:12:750 (00000316) > [Render] - Mode 4 : 1920 x 1280 @ 60 Hz, stereo = 0, hdr = 0 exclusive = 0
20:13:12:750 (00000316) > [Render] - Mode 5 : 1920 x 1280 @ 240 Hz, stereo = 0, hdr = 0 exclusive = 0
20:13:12:750 (00000316) > [Render] - Mode 6 : 2560 x 1080 @ 60 Hz, stereo = 0, hdr = 0 exclusive = 0
20:13:12:750 (00000316) > [Render] - Mode 7 : 2560 x 1080 @ 240 Hz, stereo = 0, hdr = 0 exclusive = 0
20:13:12:750 (00000316) > [Render] - Mode 8 : 2560 x 1440 @ 60 Hz, stereo = 0, hdr = 0 exclusive = 0
20:13:12:750 (00000316) > [Render] - Mode 9 : 2560 x 1440 @ 240 Hz, stereo = 0, hdr = 0 exclusive = 0
20:13:12:750 (00000316) > [Render] - Mode 10 : 2560 x 1600 @ 60 Hz, stereo = 0, hdr = 0 exclusive = 0
20:13:12:750 (00000316) > [Render] - Mode 11 : 2560 x 1600 @ 240 Hz, stereo = 0, hdr = 0 exclusive = 0
20:13:12:750 (00000316) > [Render] ***** Additional Monitor Output Info *****
20:13:12:750 (00000316) > [Render] BitsPerColor: 10
20:13:12:750 (00000316) > [Render] Primaries: R=0.6797;0.3203 G=0.2646;0.6904 B=0.1504;0.0596 White-Point=0.3125;0.3291
20:13:12:750 (00000316) > [Render] HDR: No (Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709)
20:13:12:750 (00000316) > [Render] Luminance: Min=0.5000 Max=507.6204 MaxFullFrame=507.6204
20:13:12:750 (00000316) > [Render] ******************************************
20:13:12:750 (00000316) > [Render] Monitor '2 (NVIDIA GeForce RTX 5070 Laptop GPU(1))' (0000000000000002): rect(2560 4480 0 1080)
20:13:12:750 (00000316) > [Render] - Mode 0 : 1920 x 1080 @ 60 Hz, stereo = 0, hdr = 0 exclusive = 0
20:13:12:750 (00000316) > [Render] - Mode 1 : 1920 x 1080 @ 144 Hz, stereo = 0, hdr = 0 exclusive = 0
20:13:12:750 (00000316) > [Render] ***** Additional Monitor Output Info *****
20:13:12:750 (00000316) > [Render] BitsPerColor: 10
20:13:12:750 (00000316) > [Render] Primaries: R=0.6396;0.3301 G=0.2998;0.5996 B=0.1504;0.0596 White-Point=0.3125;0.3291
20:13:12:750 (00000316) > [Render] HDR: No (Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709)
20:13:12:750 (00000316) > [Render] Luminance: Min=0.5000 Max=270.0000 MaxFullFrame=270.0000
20:13:12:750 (00000316) > [Render] ******************************************
20:13:12:750 (00000316) > [Render]
20:13:13:734 (00000316) > [NxApp] Querying GPU Driver Info...
20:13:13:734 (00000316) > [NxApp] Enumerating available display adapters:
20:13:13:734 (00000316) > [NxApp] NVIDIA GeForce RTX 5070 Laptop GPU (active)
20:13:13:735 (00000316) > [NxApp] Successfully found GPU Driver Info
20:13:13:735 (00000316) > [D3D] Max supported feature level: 11.0
20:13:13:735 (00000316) > [Render] Disabled D3D12 experimentals
20:13:14:192 (00000316) > [Render] VMEM Budget: 7332 MB
20:13:14:192 (00000316) > [Render] VMEM Available: 7300 MB
20:13:14:482 (00000316) > [Render] GPU node count: 1
20:13:14:482 (00000316) > [NxD3D] RAY TRACING ENABLED: Ray Tracing Tier 1.1 support detected
20:13:14:482 (00000316) > [NxLowLatency] Reflex support result:Result::eOk
20:13:14:482 (00000316) > [NxFrameGen] DLSSG support result: Result::eOk
20:13:14:482 (00000316) > [NxFrameGen] Max generated DLSSG frames: 3
20:13:14:482 (00000316) > [NxFrameGen] DLSSG vsync supported: 0
20:13:14:483 (00000316) > [NxApp] PreInit successful.
20:13:14:486 (00000316) > [NxLowLatency] XeLL init, code = 0
20:13:14:486 (00000316) > [NxLowLatency] Anti-Lag2 not supported. Error code (-2147024890)
20:13:14:516 (00000316) > [NxUpscaler] SL DLSS support: Result::eOk
20:13:14:517 (00000316) > [NxUpscaler] XeSS init, code = 0
20:13:14:604 (00000316) > [Input] Keyboard language: "English (United States)" (id: 1033)
20:13:14:605 (00000316) > [Input] Mouse "Wine HID device" id 1 buttons 5 sampleRate 0 horizontalWheel no
20:13:14:605 (00000316) > [Input] Keyboard "Wine HID device" type 0 subType 0 mode 1 function 12 indicators 3 total 101
20:13:14:622 (00000316) > [Input] Trying to load libScePad from C:\ProgramData\Sony Interactive Entertainment Inc\PSPC_SDK\S22\5.50.00.11\libScePad.dll
20:13:14:651 (00000316) > [Input] Using LibScePad
20:13:14:652 (00000316) > [XInput] Enumerating available xusb hid devices:

20:13:22:856 (00000316) > [NxLowLatency] Reflex support result:Result::eOk
20:13:22:856 (00000316) > [NxFrameGen] DLSSG support result: Result::eOk
20:13:22:856 (00000316) > [NxFrameGen] Max generated DLSSG frames: 3
20:13:22:856 (00000316) > [NxFrameGen] DLSSG vsync supported: 0
20:13:22:856 (00000316) > [Settings] Applied settings to preset: H
20:13:22:857 (00000316) > [NxApp] Driver Desc: NVIDIA GeForce RTX 5070 Laptop GPU
20:13:22:857 (00000316) > [NxApp] Driver Version: 999.99
20:13:22:857 (00000316) > [Display + Graphics Settings]
20:13:22:857 (00000316) > [Settings] DirectX Version: 12
20:13:22:857 (00000316) > [Settings] Window mode: Fullscreen
20:13:22:857 (00000316) > [Settings] Fullscreen display mode:
20:13:22:857 (00000316) > [Settings] Displaying on monitor: 1
20:13:22:857 (00000316) > [Settings] Resolution: 1920x1080
20:13:22:857 (00000316) > [Settings] HDR: Off
20:13:22:857 (00000316) > [Settings] OS reported Refresh rate: 144
20:13:22:857 (00000316) > [Settings] VSync: Off
20:13:22:857 (00000316) > [Settings] Low Latency: None
20:13:22:857 (00000316) > [Settings] Frame generation: None
20:13:22:857 (00000316) > [Settings] Max generated frames: 0
20:13:22:857 (00000316) > [Settings] Dynamic resolution FPS target: 60
20:13:22:857 (00000316) > [Settings] Anti aliasing: PICO
20:13:22:857 (00000316) > [Settings] Upscale method: PICO
20:13:22:857 (00000316) > [Settings] Upscale quality: Dynamic
20:13:22:857 (00000316) > [Settings] Upscale sharpen value: 0.000000
20:13:22:857 (00000316) > [Settings] Graphics Options:
20:13:22:857 (00000316) > [Settings] Texture Quality: High
20:13:22:857 (00000316) > [Settings] Texture Filtering: Anisotropic8x
20:13:22:857 (00000316) > [Settings] Shadow Quality: High
20:13:22:857 (00000316) > [Settings] Shadow Res: High
20:13:22:857 (00000316) > [Settings] Depth of Field: High
20:13:22:857 (00000316) > [Settings] Level of Detail: High
20:13:22:857 (00000316) > [Settings] Terrain Quality: High
20:13:22:857 (00000316) > [Settings] Clouds Quality: High
20:13:22:857 (00000316) > [Settings] Ambient Occlusion: SSAO_High
20:13:22:857 (00000316) > [Settings] Reflections: High
20:13:22:857 (00000316) > [Settings] Translucency Quality: Default

20:13:22:857 (00000316) > [Settings] Bloom: On
20:13:22:857 (00000316) > [Settings] Vignette: On
20:13:22:857 (00000316) > [Settings] Motion Blur: 0.500000
20:13:22:857 (00000316) > [Settings] FOV Correction: 1.000000
20:13:22:857 (00000316) > [Settings] Sharpness: 0.500000
20:13:22:857 (00000316) > [Settings] Lens Flares: On
20:13:22:857 (00000316) > [Settings] Screen Space Shadows: On
20:13:22:857 (00000316) > [Display + Graphics Settings]
20:13:22:857 (00000316) > [NxApp] Initializing module prefetch thread
20:13:22:857 (00000316) > [NxProcessorInfo] Processor info:
20:13:22:857 (00000316) > [NxProcessorInfo] Description: AMD Ryzen 9 8945HX with Radeon Graphics
20:13:22:857 (00000316) > [NxProcessorInfo] Group Count: 1
20:13:22:857 (00000316) > [NxProcessorInfo] Physical Core: 16
20:13:22:857 (00000316) > [NxProcessorInfo] Logical Core: 32
20:13:22:857 (00000316) > [NxProcessorInfo] Distinct L3 Cache: 2
20:13:22:857 (00000316) > [NxProcessorInfo] Family: 25
20:13:22:857 (00000316) > [NxProcessorInfo] Model: 97
20:13:22:857 (00000316) > [NxProcessorInfo] Name: AMD Ryzen 9 8945HX with Radeon Graphics
20:13:22:857 (00000316) > [NxProcessorInfo] AVX: 1
20:13:22:857 (00000316) > [NxProcessorInfo] F16C: 1
20:13:22:857 (00000316) > [NxProcessorInfo] AVX2: 1
20:13:22:857 (00000316) > [NxProcessorInfo] NormalAffinity(auto)
20:13:23:025 (00000316) > [NxApp] Creating window...
20:13:23:074 (00000848) > [GameWindow] UpdateState bVisible true
20:13:23:085 (00000316) > [NxApp] Window created.
20:13:23:085 (00000316) > [NxApp] Initializing swapchain...
20:13:23:085 (00000744) > [SwapChain] Creating...
20:13:23:085 (00000744) > [NxSwapChainImpl] Swapchain native backbuffer (windows) resolution: 1920x1080
20:13:23:123 (00000744) > [DXGI] Created swapchain.
20:13:23:137 (00000744) > [SwapChain] Gamma correction is enabled.
20:13:23:137 (00000744) > [SwapChain] Successfully created.
20:13:23:137 (00000744) > [NxSwapChainImpl] Swapchain native backbuffer (windows) resolution: 1920x1080
20:13:23:137 (00000316) > [NxApp] Swapchain initialized
20:13:23:137 (00000316) > [NxApp] Initializing renderer...
20:13:23:137 (00000316) > [NxApp] Renderer initialized
20:13:23:137 (00000316) > [Render] UMA = False, CacheCoherentUMA = False
20:13:23:138 (00000316) > [Render] Tight alignment support: yes
20:13:23:284 (00000316) > [PSO] Loaded 25722 shader hashes, 42446 descriptors from appdir:HashDB.bin
20:13:23:284 (00000316) > [PSO] Loaded 14 shader hashes, 70 descriptors from appdata:UserHashDB.bin
20:13:23:412 (00000316) > [PSN Account Linking] [PSN] PSPC initialization failed: 8a800111
20:13:23:413 (00000316) > [PSN Account Linking] [PSN] Setting device data collection setting failed 8a80010d
20:13:23:413 (00000316) > [PSN Account Linking] Failed to update data collection policy to PSPC, error=0
20:13:23:413 (00000316) > [NxStorage] Storage Drive Type is HDD.
20:13:23:413 (00000316) > [NXStorage] Storage Drive (Z:) free disk space is 215821631488 (bytes).

20:13:23:446 (00000316) > [NXStorageReadDevice] Initialized DirectStorage.

20:13:24:159 (00000524) > [PSN Account Linking] [PSN] Setting device data collection setting failed 8a80010d
20:13:24:159 (00000524) > [PSN Account Linking] Failed to update data collection policy to PSPC, error=0
20:13:24:846 (00000528) > [PSN Account Linking] [PSN] Setting device data collection setting failed 8a80010d
20:13:24:846 (00000528) > [PSN Account Linking] Failed to update data collection policy to PSPC, error=0
20:13:24:849 (00000532) > [PSN Account Linking] [PSN] Setting device data collection setting failed 8a80010d
20:13:24:849 (00000564) > [PSN Account Linking] [PSN] Setting device data collection setting failed 8a80010d
20:13:24:849 (00000532) > [PSN Account Linking] Failed to update data collection policy to PSPC, error=0
20:13:24:849 (00000564) > [PSN Account Linking] Failed to update data collection policy to PSPC, error=0
20:13:24:849 (00000564) > [PSN Account Linking] [PSN] Setting device data collection setting failed 8a80010d
20:13:24:849 (00000564) > [PSN Account Linking] Failed to update data collection policy to PSPC, error=0
20:13:25:077 (00000316) > [FatalError] Fatal error occurred:
20:13:25:077 (00000316) > [FatalError] Timed out waiting for GPU
20:13:25:078 (00000316) > [Crash] Memory statistics:
20:13:25:078 (00000316) > [Crash] Total RAM = 30.6 GB (31368 MB)
20:13:25:078 (00000316) > [Crash] Avail RAM = 21.3 GB (21760 MB)
20:13:25:078 (00000316) > [Crash] Total virtual memory = 131072.0 GB (134217727 MB)
20:13:25:078 (00000316) > [Crash] Avail virtual memory = 131069.4 GB (134215071 MB)
20:13:25:078 (00000316) > [Crash] Total page file = 61.3 GB (62736 MB)
20:13:25:078 (00000316) > [Crash] Avail page file = 51.9 GB (53128 MB)
20:13:25:078 (00000316) > [Crash]
20:13:25:078 (00000316) > [Crash] RAM info:
20:13:25:078 (00000316) > [Crash] Unhandled exception at address 0x00000000420e3fac (code: 0xc0000005): "Access violation"
20:13:27:888 (00000316) > [Crash] Created minidump at "C:\users<username>\Documents\DEATH STRANDING 2 - ON THE BEACH\DEATH STRANDING 2 - ON THE BEACH-v1.2.57.0 2026-04-02-20-13-26.mdmp".

• Crash now occurs much earlier (immediately after splash screen/DirectStorage initialization).
• Address of the "Access Violation" has shifted to 0x00000000420e3fac.
• Workarounds like -noDirectStorage and nvngx=d no longer prevent the immediate "Timed out waiting for GPU" error.

It seems the Steam Deck-focused optimizations in 1.2 are causing immediate memory access conflicts on NVIDIA 50-series laptop GPUs under Proton.

System: CachyOS | Driver 595.58.03 | RTX 5070 Laptop | Ryzen 9 8945HX

@Ripped-Kanga cleared the shader cache and verified integrity, allowed the "new" vulkan shaders to compile, and unfortunately naught. Still getting those errors. Seems to actually run worse, somehow, even with the exact same settings. Very strange.
Updated my graphics drivers to 590 as well. Not sure how badly that would have affected it.

Thanks, I just tried tonight with the latest Cachy Proton and got around an hour of playtime before the same crash event occured.

Updating to the 595.58.03 drivers seems to have solved my crashing issues. Using proton experimental bleeding edge.

                                                              ┌──────────────────────Hardware──────────────────────┐
  ██████████████████████████████████████████████████████       PC: X870 AORUS ELITE WIFI7 (Default string-CF-WCP-ADO)
  ██████████████████████████████████████████████████████      │ ├: AMD Ryzen 7 9700X (16) @ 5.79 GHz
  ████                     ████                     ████      │ ├: NVIDIA GeForce RTX 4070 Ti SUPER [Discrete]
  ████                     ████                     ████      │ ├󱄄: 2560x1440 in 32", 165 Hz [External]
  ████    █████████████████████         ████████    ████      │ ├󰋊: 595.95 GiB / 929.50 GiB (64%) - btrfs
  ████    █████████████████████         ████████    ████      │ ├: 9.75 GiB / 30.95 GiB (32%)
  ████    ████                              ████    ████      └ └󰓡 : 459.41 MiB / 4.00 GiB (11%)
  ████    ████                              ████    ████      └────────────────────────────────────────────────────┘
  ████    ████                              ████    ████
  ████    ████                              ████    ████      ┌──────────────────────Software──────────────────────┐
  ████    ████                              ████    ████       OS: Omarchy 3.5.0
  ████    ████                              ████    ████      │ ├󰘬: master
  ████████████                              ████    ████      │ ├󰔫: stable
  ████████████                              ████    ████      │ ├: Linux 6.19.10-arch1-1
  ████    ████                              ████    ████      │ ├: Hyprland 0.54.3 (Wayland)
  ████    ████                              ████    ████      │ ├: kitty 0.46.2
  ████    ████                              ████    ████     
  ████    ████                              ████    ████      
  ████    ████                              ████    ████      
  ████    ████                              ████    ████      └────────────────────────────────────────────────────┘
  ████    ██████████████████████████████████████    ████
  ████    ██████████████████████████████████████    ████      ┌────────────────Age / Uptime / Update───────────────┐
  ████                     ████                     ████      󱦟 OS Age: 191 days
  ████                     ████                     ████      󱫐 Uptime: 3 hours, 15 mins
  █████████████████████████████     ████████████████████       Update: Saturday, April 04 2026 at 09:51
  █████████████████████████████     ████████████████████      └────────────────────────────────────────────────────┘

The game currently (version 1.3) still seems to suffer from lots of crashes. Especially during cutscenes.

While the gameplay runs fine as far as I tested (roughly 15 hours playtime), there is one cutscene in chapter 3 after delivering a package to the animal shelter where a crash during the following rather long cutscene seems to be guaranteed. I at least wasn't able to watch it fully after having tried it four times.

Using a RTX 2080 with nvidia-open 595.58.03-1 for the record. Tried with Proton-GE10-34 as well as bleeding edge Proton Experimental. Same problem with both.

I think it's possible to skip it by holding X, but skipping cutscenes in a Kojima game is kind of a no-go.

the game will reliably crash during the cutscene after the same mission (order 15) for me too, i can’t progress because of it. 3060 ti, nvidia-open 595.58.03.

Proton 11 (Beta) starts the game without issue on my hardware after clearing shadercache and compatdata folders. Haven't played more than a few minutes but loaded into various savegames without issue, most settings on High or Very High and native PICO AA @ 2560x1080

CPU: AMD Ryzen 7 7800X3D
GPU: AMD Radeon RX 7900 XT

After starting Order 5 and heading a short ways out from the C1 South Distribution Center I'm getting what looks like a series of vertex explosions in the sky. This was with DXVK_CONFIG='dxgi.hideAmdGpu = True;' so I could use this games ray tracing features with RADV. I also tried playing this section without that on Very High preset with the same result.

Proton Version: Proton Hotfix, default build from March 20th
Mesa: 26.0.5
Kernel: 6.19.13
GPU: RX 7900 XTX
CPU: Ryzen 7 5800X3D

I have texture misrendering issues similar to above in minimap and particularly around lucy's face:

         :++===++==================-       :++-           OS: CachyOS x86_64
        :*++====+++++=============-        .==:           Host: 83LU (Legion Pro 5 16IAX10H)
       -*+++=====+***++==========:                        Kernel: Linux 7.2.0-rc1-1-cachyos-rc
      =*++++========------------:                         Uptime: 12 hours, 46 mins
     =*+++++=====-                     ...                Packages: 38 (flatpak), 1700 (pacman)
   .+*+++++=-===:                    .=+++=:              Shell: fish 4.7.1
  :++++=====-==:                     -*****+              Display (XWU-CBA): 2560x1440 in 27", 165 Hz [External]
 :++========-=.                      .=+**+.              Display (SDC420A): 2560x1600 @ 1.49x in 16", 165 Hz [Built-in]
.+==========-.                          .                 WM: niri 26.04 (Wayland)
 :+++++++====-                                .--==-.     Theme: Breeze-Dark [GTK2], Breeze [GTK3]
  :++==========.                             :+++++++:    Icons: breeze [GTK2/3/4]
   .-===========.                            =*****+*+    Font: Arial (10pt) [GTK2/3/4]
    .-===========:                           .+*****+:    Cursor: breeze (24px)
      -=======++++:::::::::::::::::::::::::-:  .---:      Terminal: kitty 0.47.1
       :======++++====+++******************=.             Terminal Font: NotoSansMono-Regular (12pt)
        :=====+++==========++++++++++++++*-               CPU: Intel(R) Core(TM) Ultra 9 275HX (8+16) @ 5.50 GHz
         .====++==============++++++++++*-                GPU 1: NVIDIA GeForce RTX 5070 Ti Mobile [Discrete]
          .===+==================+++++++:                 GPU 2: Intel Graphics @ 1.90 GHz [Integrated]