-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cyberpunk 2077 (GOG) randomly crashes #2259
Comments
Can you check RAM usage with |
Back when I've reported this issue I also did test if it could be a memory leak but didn't encountered any issues regarding this. I've used mangohud and have checked the task manager of KDE while playing the game and the memory stayed the same. After your comment I've checked again but didn't encounter any increasing memory while playing. From my 32GB RAM the whole usage didn't go above 10GB (around ~6GB is used by the game). The game crashed about 30 mins. |
Try launching with |
Didn't helped. Game crashed after about 20 minutes. |
Playing the GOG version of Cyberpunk 2077 crashes randomly about 5 - 30 minutes in game. Screen freezes for a few seconds, than goes black for a few seconds, than it reappears for a few seconds and the game crashes to the desktop, which resets itself.
I've already tried following workarounds: disable GOG-overlay (rename GameServicesGOG.dll) even though I don't use the Galaxy Launcher, update vkd3d-proton, turn on V-Sync in game, using different Proton/Wine versions, using different launchers (Steam, Heroic & Bottles), run with VKD3D_DEBUG=none, switching between Wayland & X11.
Software information
Cyberpunk 2077 2.2 (GOG) - all settings maxed, AMD FSR 3, no Ray- /Pathtracing, FPS-Limiter set to 60 fps
System information
OS: Solus 4.6 KDE (Wayland)
Kernel 6.12.5-312.current (64-bit)
GPU: AMD Ryzen 9 7900 12-Core Processor
Driver: amdgpu, Vulkan: 1.3.290, Mesa 24.3.3
Wine version: Proton 9.0-4 / Proton 8 (also Wine-GE / Proton-GE / Wine 10.0rc2)
VKD3D-Proton version: 2.13 & 2.14 & git version shortly before 2.14.1 release
Log files
Proton logfile with multiple vkd3d-proton errors:
steam-0.log
I've attach the VKD3D.log (using VKD3D_DEBUG = err) with Version VKD3D-Proton 2.14, it keeps spamming multiple errors:
vk3d.log
After the crash, the terminal show these lines:
after crash.txt
Maybe a pure coincidence but a few months ago I've also tried to play Robocop: Rogue City (GOG) on Linux (tested with Fedora & Solus) which does have the same problem. In contrary to Saints Row (2022) via Epic Games Store (Heroic Launcher on Solus), which I've played a few weeks ago using DX12 (vkd3d-proton) and worked flawlessly on Linux.
The text was updated successfully, but these errors were encountered: