I cannot get the game to run at all using my 2060m and the Nvidia 510 drivers. Tried Proton 7.1 GE and Proton 6.3 and Experimental. All result in a black bar for a splash screen, the game comes up in windowed mode (completely black) then it crashes. According to the logs it's a PageFault but the reason why is lost on me.

Using the intel igpu in this laptop will get me past the intro cutscene however.

Arch Linux Kernel 5.16.5

Works well with Proton-7.1-GE-2, was able to play Co-Op with two friend for three hours without any problems yesterday.

Works well with Proton-7.1-GE-2, was able to play Co-Op with two friend for three hours without any problems yesterday.

Yes, I want to confirm this. Switching to 7.1-GE-2 fixed Co-Op. We played for hours afterwards without any issues.

@Meulengracht @l0wl3vel Just wondering, were your co-op partners running on Windows?

@Meulengracht @l0wl3vel Just wondering, were you co-op partners running on Windows?

Nope, we were both running experimental, and both switched to GE

@Meulengracht @l0wl3vel Just wondering, were you co-op partners running on Windows?

My co-op partners were both running Windows 10. I was hosting the session.

i experience that same issues with the game crashing almost every 15-30 min, No other proton games does that. i I have tried both Steam Beta, Proton Experimental and the stable version with no luck. both on dx11 and dx12

I have read on forums and on proton DB to find similar users with similar problems and it looks like something that happens more often for Ryzen users not distro specific. Not sure if it is a fact but i looks like it from the amount of comments.

i will be happy to provide any details, it is on Ubuntu 20.04 with nvidia 510 drivers. bios on the motherboard have been updated to the newest and have tried many of the proposed steam launch options with no luck

Seems Proton 7 is much worse. After 20 minutes it gave stuttering to a crawl, then a hard lock up. Proton experimental is still fine.

It'd be helpful if you could gather a Proton log showing the issue. It's working well on my AMD desktop machine so far.

I've run into this issue on my Intel Xeon desktop with an AMD Radeon RX 5600 XT, on Kubuntu 20.04 with Hardware Enablement Stack active.

I continued my Dying Light 2 world, had a friend join, and after roughly 15 minutes, the game hung - sounds played, but the video output froze, and I had to forcibly terminate it to exit.

Computer Information:
    Manufacturer:  Gigabyte Technology Co., Ltd.
    Model:  Z97X-SLI-CF
    Form Factor: Desktop
    No Touch Input Detected

Processor Information:
    CPU Vendor:  GenuineIntel
    CPU Brand:  Intel(R) Xeon(R) CPU E3-1241 v3 @ 3.50GHz
    CPU Family:  0x6
    CPU Model:  0x3c
    CPU Stepping:  0x3
    CPU Type:  0x0
    Speed:  3900 Mhz
    8 logical processors
    4 physical processors
    HyperThreading:  Supported
    FCMOV:  Supported
    SSE2:  Supported
    SSE3:  Supported
    SSSE3:  Supported
    SSE4a:  Unsupported
    SSE41:  Supported
    SSE42:  Supported
    AES:  Supported
    AVX:  Supported
    AVX2:  Supported
    AVX512F:  Unsupported
    AVX512PF:  Unsupported
    AVX512ER:  Unsupported
    AVX512CD:  Unsupported
    AVX512VNNI:  Unsupported
    SHA:  Unsupported
    CMPXCHG16B:  Supported
    LAHF/SAHF:  Supported
    PrefetchW:  Unsupported

Operating System Version:
    Ubuntu 20.04.4 LTS (64 bit)
    Kernel Name:  Linux
    Kernel Version:  5.13.0-30-generic
    X Server Vendor:  The X.Org Foundation
    X Server Release:  12013000
    X Window Manager:  KWin
    Steam Runtime Version:  steam-runtime_0.20211207.0

Video Card:
    Driver:  AMD AMD Radeon RX 5600 XT (NAVI10, DRM 3.41.0, 5.13.0-30-generic, LLVM 12.0.0)
    Driver Version:  4.6 (Compatibility Profile) Mesa 21.2.6
    OpenGL Version: 4.6
    Desktop Color Depth: 24 bits per pixel
    Monitor Refresh Rate: 60 Hz
    VendorID:  0x1002
    DeviceID:  0x731f
    Revision Not Detected
    Number of Monitors:  1
    Number of Logical Video Cards:  1
    Primary Display Resolution:  1920 x 1080
    Desktop Resolution: 1920 x 1080
    Primary Display Size: 20.04" x 11.26" (22.95" diag)
                                            50.9cm x 28.6cm (58.3cm diag)
    Primary VRAM: 6144 MB

Sound card:
    Audio device: Realtek ALC1150

Memory:
    RAM:  15881 MB

VR Hardware:
    VR Headset: None detected

Miscellaneous:
    UI Language:  English
    LANG:  en_US.UTF-8
    Total Hard Disk Space Available:  1804284 MB
    Largest Free Hard Disk Block:  1271475 MB

Storage:
    Number of SSDs: 0
    Number of HDDs: 0

And here's my full Proton log with PROTON_LOG=1 %command% as launch options - 7.6 MiB.

Let me know if there's any other information I can provide or things to test!

Also, GloriousEggroll's 7.2-GE-3-test-2 has been working without crashing for an entire hour! Co-op multiplayer disconnects after about half an hour, but the game itself doesn't crash and I can quit to menu, then continue to reconnect multiplayer. (My internet itself seemed stable, Mumble voice chat remained connected, but I'm not 100% certain of that.)

The game randomly hangs with latest Proton Experimental.
steam-534380.log
steam-534380.log
steam-534380.log

With Proton GE 7.2 the game randomly crashed.
steam-534380-GE-crash.log

Hardware:
CPU: AMD Ryzen 3950X
GPU: AMD Radeon 6900XT
Mesa: Builded from git commit 53ca85a

As of update 1.3.0 that was released today, the game now crashes for me before displaying anything other than a black window. I've attached the output of PROTON_LOG=1.
steam-534380.log

Same issue as tizzir. Also attached log
steam-534380.log
.

Same as above. Have never seen DL2 working via proton (6, 7, exp). Usually i get a black screen and a crash. I checked d3d11 log inside app folder and saw an attempt to use CPU integrated graphics (that brought to an error). Hope this will help somehow.

steam-534380.log
DyingLightGame_x64_rwdi_d3d11.log
DyingLightGame_x64_rwdi_dxgi.log

I still get crashes with the current Proton version, but after my earlier comment, even with the 1.3.0 update, GloriousEggroll's 7.3-GE-1 somehow continues to work - not the newer versions of GE, etc. 1.3.0 appeared to fix the disconnect issue and I've played as host with a Windows user joining for a few hours.

I don't advise settling for this as Proton itself should be fixed, but if you're looking to just play the game after submitting your logs here, this might work for you. Speaking of, if there's any testing I could do to help diagnose this, let me know!

Rather embarrassingly, I have discovered that the 1.3.0 update was not to blame for the game not starting for me. At least, not in its entirety. It turns out that I had some mods installed that had not been updated, which caused the game to crash on startup. After removing the mod files, the game starts just fine with the latest proton experimental (and likely other proton variants as well.)

For some reasons I can't play it. Even in menu my FPS is around 2. Tried different proton versions, but nothing helps.

It might be not for everyone, but I fixed my issues with launch option:
DXVK_FILTER_DEVICE_NAME="GeForce RTX 2070" PROTON_ENABLE_NVAPI=1 PROTON_HIDE_NVIDIA_GPU=0 VKD3D_CONFIG=dxr %command% -nologos
Now everything works just fine. "DXVK_FILTER_DEVICE_NAME" is most important, because I tried without and it wasn't working. And yes "GeForce RTX 2070" is my video card, so for everyone it will be different name.

It might be not for everyone, but I fixed my issues with launch option: DXVK_FILTER_DEVICE_NAME="GeForce RTX 2070" PROTON_ENABLE_NVAPI=1 PROTON_HIDE_NVIDIA_GPU=0 VKD3D_CONFIG=dxr %command% -nologos Now everything works just fine. "DXVK_FILTER_DEVICE_NAME" is most important, because I tried without and it wasn't working. And yes "GeForce RTX 2070" is my video card, so for everyone it will be different name.

Mr. @DMGPage advice helped me, but if this does not help you, then you can also go along the path: ~/.steam/steam/steamapps/compatdata/534380/pfx/drive_c/users/steamuser/Documents/dying light 2/out/settings .

534380 - game App ID.
In your case, everything will look about the same.

There is a file: video.scr.
And it needs to be:
RendererMode("d3d11")
AsyncCompute(0)
Not d3d12, despite the fact that during the game you can change everything as you wish (this does not negate the fact that everything can break again after graphics changes).
In addition, most likely you will also need to lower the graphics using this file by changing other settings.

I also set compatibility with Proton 7.0-4.

When using the Intel Arc A770, it only runs with the d3d11 renderer, but produces hangups and some transparency issues (a lot of black squares around things that should be transparent).
With d3d12 on the A770 I get the following on stderr:

wine: Unhandled exception 0xc0000417 in thread 12c at address 000000007B01253E (thread 012c), starting debugger...
Unhandled exception: 0xc0000417 in 64-bit code (0x000000007b01253e).
Register dump:
 rip:000000007b01253e rsp:000000000011b120 rbp:0000000000000000 eflags:00000202 (   - --  I   - - - )
 rax:000000007b0124f0 rbx:00000003af6fa146 rcx:000000000011b140 rdx:0000000000000001
 rsi:00000003af6fa146 rdi:0000000004d2d570  r8:0000000000000000  r9:0000000000000000 r10:0000000067fe3284
 r11:000000000000f010 r12:0000000000000000 r13:0000000000000000 r14:00000000241d0150 r15:000000000011b400
Stack dump:
0x000000000011b120:  000000000011b140 0000000000000000
0x000000000011b130:  0000000000000001 00000003af6daec9
0x000000000011b140:  00000001c0000417 0000000000000000
0x000000000011b150:  000000007b01253e ffffffff00000000
0x000000000011b160:  0000000000000000 00000003af6e44c2
0x000000000011b170:  45363344347b224c 353233452d383639
0x000000000011b180:  46422d454331312d 32303038302d3143
0x000000000011b190:  7d38313330314542 0000000000000022
0x000000000011b1a0:  0000000000000027 000000000011b340
0x000000000011b1b0:  0000000000000026 00000003af6eade8
0x000000000011b1c0:  0000000000000000 0000000000000000
0x000000000011b1d0:  0000000000000000 0000000000000000
Backtrace:
=>0 0x000000007b01253e AccessCheckByTypeAndAuditAlarmW+0x1153e() in kernelbase (0x0000000000000000)
  1 0x00000003af690b8f _Cmulcc+0x1fb8f() in ucrtbase (0x0000000000000000)
  2 0x00000003af69154e _Cmulcc+0x2054e() in ucrtbase (0x0000000000000000)
  3 0x00000003af6f1113 _Cbuild+0x363a3() in ucrtbase (0x0000000000000000)
  4 0x0000000037c424cc in xefx_loader (+0x24cc) (0x0000000000000000)
  5 0x0000000037c41e56 in xefx_loader (+0x1e56) (0x000000000011b4d0)
  6 0x0000000037c43846 in xefx_loader (+0x3846) (0x000000000011de80)
  7 0x0000000037c438f4 xefxLoadLibrary+0x54() in xefx_loader (0x000000000011de80)
  8 0x00000000379740fc xessD3D12BuildPipelines+0x2bafc() in libxess (0x000000000011de80)
  9 0x000000003794888c xessD3D12BuildPipelines+0x28c() in libxess (0x000000000011de80)
  10 0x0000000036fcb498 ffxGetCommandListDX12+0xbac8() in rd3d12_x64_rwdi (0x000000000011de80)
  11 0x0000000036fc232a ffxGetCommandListDX12+0x295a() in rd3d12_x64_rwdi (0x000000000011df09)
  12 0x00000000017f27ad ??0?$CAbstractSystem@VCoAudioPropagation@@@cbs@@QEAA@XZ+0xc621dd() in engine_x64_rwdi (0x000000000011dfe0)
  13 0x0000000000f282c0 ??0?$CAbstractSystem@VCoAudioPropagation@@@cbs@@QEAA@XZ+0x397cf0() in engine_x64_rwdi (0x000000000011e110)
  14 0x0000000000f1830a ??0?$CAbstractSystem@VCoAudioPropagation@@@cbs@@QEAA@XZ+0x387d3a() in engine_x64_rwdi (0x000000000011ee70)
  15 0x000000014000738b in dyinglightgame_x64_rwdi (+0x738b) (0x000000000011ee70)
  16 0x0000000140001df3 in dyinglightgame_x64_rwdi (+0x1df3) (0x0000000000000000)
  17 0x000000014007ec2a in dyinglightgame_x64_rwdi (+0x7ec2a) (0x0000000000000000)
  18 0x000000007b62c9e9 ActivateActCtx+0x20da5() in kernel32 (0x0000000000000000)
  19 0x000000017005f627 A_SHAFinal+0x3caa7() in ntdll (0x0000000000000000)

With an nvidia 1060 it runs fine either way.
So I guess the blackness-instead-of-transparency part is on the intel mesa side? Not sure.
But would definitely be nicer to run in d3d12 mode, the trace there is weird though.

UPDATE:
Tested mesa-git and the black squares seem to be gonethere (previously was on 22.2.3-1 on Arch)
Still some pretty hard short stalls but no complete hangup yet.
(Another update: another git update a day later and the glitches are back and worse lol)

I seem to be having a somewhat similar issue, at least judging by the appearance of that ??0?$CAbstractSystem@VCoAudioPropagation key in my logs. The symptom for me however is the game completely crashing after clearing the "Press any key to continue" splash just after launch. Pretty sure this has something to do with audio, as I'm not getting any on the splash screen or after I press the key to continue. I use pulseaudio and alsa if that helps.

CLI Args: PROTON_LOG=1 VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr11 VKD3D_FEATURE_LEVEL=12_1 %command% -nologos

Proton Log

Hope this issue is solved soon! I'm happy to provide more information, but I'm at a dead end here.

Just tried running this and the game fails to launch with both Proton 8, and Proton Experimental due to an Access Violation in dsound.dll (logs attached).

Forcing compatibility to Proton 7.0-6 and the game launches correctly.

Not sure how Proton works when it comes to system dll versioning, but since Proton 7 works and Proton 8+ doesn't, I assume this is a regression in Proton? Not sure if it should be flagged up somewhere else, since this game hasn't had any activity in a few months and is an older title.

steam-534380.log

As a secondary issue, the game fails to launch into the game from the menu if any DXR graphics options are enabled using Proton 7.0-6. After selecting continue or play campaign, the screen goes back and freezes with the music still playing. After 30s or so the force quit system message is shown. Non-RT launches into the game just fine.

Manually copying dsound.dll from steamapps/common/Proton 7.0/dist/lib64/wine/x86_64-windows/ to steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-windows allows the game to launch when running under Proton Experimental, fixes DLSS not being available, and fixes the game hanging when trying to load from the menu when RT is enabled as is the case running under Proton 7.0-6.

I'm having the same issue with DLSS not being available as @rcbevans. RTX 3090, 530.43.01 drivers. DLSS works fine in Lutris, but it's not available in the Dead Space Remake or Dying Light 2 no matter what I do. The fix rbcevans suggested doesn't work.

Just to add to that, it's NOT a VKD3D or Proton issue, as Deathloop allows DLSS (and RayTracing) with no issues.

So @kisak-valve is right, it is in fact a regression in Proton and it affects all games that use VKD3D (at least).

Deathloop running using GE-Proton7-53 works perfectly. Moving it to Proton Experimental or anything from the past few weeks (including GE-Proton7-55) kills DLSS capability. Seems like Dead Space and Dying Light 2 have the same issue. I'm going to test out DL2 with GE-Proton7-53 and see if DLSS comes back, that would at least narrow the breaking change to at least the last month or so, hopefully.

@rcbevans The dsound issue you were running into on 8.0 is quite odd from looking at the log. In order to try to figure out what is going on, could you:

1. Switch to the Steam Beta client
2. Run "Verify the integrity of files" on Proton Experimental to get the original dsound.dll back
3. Assuming you are still hitting the problem, try deleting the prefix just in case.
4. Assuming that didn't fix things, get a log of the crash with PROTON_LOG=+dsound,+sync,+mmdevapi,+pulse %command%
5. Get the output of pactl info, pactl list sources and pactl list-source-outputs and upload in addition to the log.

And a few more context questions --

1. On 7.0, did you do anything wrt voice chat in the game / playing online?
2. Where exactly is the game crashing? Before a window shows up?

I know you have a working game now, so I get if you don't want to go through this hassle. This is really a mystery right now. I believe that if the game is still broken after "verify integrity of files" you could just copy the 7.0 dsound.dll again and fix things while we see if anything can be gleaned from the results of these tests :)

@alasky17 Greetings. I was having this same issue and fortunately found this post to fix it. Since you are asking for some data and the op didn't get back to you, hopefully I can assist you.

After switching to Steam beta and verifying integrity of both Dying Light 2 and Proton Experimental the problem returned, here are the logs you asked for:

Proton Log: https://drive.google.com/file/d/10ft-5WH4z8iYLpNRxRN-sYDeIuSaGZ5p/view?usp=sharing
pactl sources: https://drive.google.com/file/d/1vFxDpvBjRY2e0SqieP9Fu3Sq4Cmh2Lls/view?usp=sharing
pactl source-outputs: NOTHING. The output of the command is empty.

The most interesting parts of the proton log to me are:

Line 666106: Unhandled exception: page fault on read access to 0xffffffffffffffff in 64-bit code (0x000003435318ad).
Line 666126: Stack trace starts with references to dsound.

Questions:
1.- On 7.0, did you do anything wrt voice chat in the game / playing online?
- I never use the in game voice chat. I use Discord.

2.- Where exactly is the game crashing? Before a window shows up?
- When I click play, the Splash appears, then an instant of black screen, then immediately back to desktop.

@Corbent Thank you so much!! I am hoping there will be some clue in there :) I also don't think I have any system info from anyone who has run into this bug yet. Could you also please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report. If you're using the Steam client beta, then please also include the output from Steam Runtime Diagnostics.

@alasky17

Steam system information: https://gist.github.com/Corbent/f5585e68b0eec81a86c1764af4d011e4
Steam Runtime Diagnostics: https://gist.github.com/Corbent/2fbd6b69c4db5a1e22045db31ce7e03b

I'm not used to contributing to issues on github so I'm unsure if "then include a link to the gist in this issue report" means something other than this comment.

Swapped from NVIDIA to AMD 6800xt and now Dying Light 2 won't launch.

Log file:
steam-534380.log

@LiamDawe If your problem is DSOUND.dll related try the method in the post by rcbevans. It helped me.
https://github.com/ValveSoftware/Proton/issues/5542#issuecomment-1525075438

Okay firstly here's a log with "PROTON_LOG=+dsound,+sync,+mmdevapi,+pulse %command%" using Proton Experimental:

steam-534380.tar.gz

Some other logs that @alasky17 asked for above:

liam@liam-kub:~$ pactl info
Server String: /run/user/1000/pulse/native
Library Protocol Version: 35
Server Protocol Version: 35
Is Local: yes
Client Index: 466
Tile Size: 65472
User Name: liam
Host Name: liam-kub
Server Name: PulseAudio (on PipeWire 0.3.65)
Server Version: 15.0.0
Default Sample Specification: float32le 2ch 48000Hz
Default Channel Map: front-left,front-right
Default Sink: alsa_output.pci-0000_0b_00.4.analog-stereo
Default Source: alsa_input.usb-046d_HD_Pro_Webcam_C920_B33EF4BF-02.analog-stereo
Cookie: ea1f:ad4f

pactl list sources:
https://gist.github.com/LiamDawe/6c0d9c63b1f3e4bfd9039ff4a6cbed1b

And also:

liam@liam-kub:~$ pactl list-source-outputs
No valid command specified.

I don't even seem to have dsound.dll in Proton 7, I tried verifying files and completely uninstalled and reinstalled Proton 7 and still don't have it. Weird?

Edit: okay removing Proton 7 folder entirely, re-installing and then running a game unpacked it properly. Weird how verifying didn't pick up the missing file though. Anyway, did the copying from 7 to Experimental and yup it now launches. So a regression from 7 to Experimental? Log file of it now working:

steam-534380.log

Coming back to add that I am seeing (what appears to be) the same DSOUND.dll crash in Remnant: From the Ashes

@alasky17
Beta Steam client log with PROTON_LOG=+dsound,+sync,+mmdevapi,+pulse

steam-534380.log

pactl-info.txt
pactl-list-sources.txt
pactl-source-outputs.txt

It's something to do with my connected SteelSeries Arctis Pro Wireless headset.

If I disconnect the headset GameDAC, the game launches fine.

Here's updated pactl logs without the SteelSeries connected.

pactl-info.txt
pactl-list-sources.txt
pactl-source-outputs.txt

It appears the issue is having two active audio input devices, as reported https://github.com/ValveSoftware/Proton/issues/6964.

Using pavucontrol to disable the additional multiple inputs (leaving only the one I want with an active configuration) the game launches.

Replying to https://github.com/ValveSoftware/Proton/issues/5542#issuecomment-1867872319

I've now also tried changing the renderer between dx11 and dx12 in the settings file, changing between Windowed and Fullscreen, and a few other proton versions. So far hasn't fixed it.

@something12356

Dying Light 2 is working perfectly fine for me. I Have been playing for the past few days and I tested right now to see if an update could have caused issues.

• GPU: RX 7900 XT

• Video driver version: Mesa 1:23.3.4-2

• Kernel version: 6.7.2.zen1-2

• Proton version: GE-Proton8-25

@Corbent
Thanks for the response. I just tried again and the game still crashes before getting to the main menu. Recently wine has started saying mono is not installed when I launch steam, even though I have the most up to date version, so maybe it's due to that? But I don't have an issues with other games.

• GPU: RX 6600 XT
• Video driver: Mesa 1:23.3.5-1
• Kernel: 6.74-zen1-1
• Proton version: GE-Proton8-32 and also Proton Experimental.

@something12356 I can launch the game just fine with a RX 6600 and the same mesa drivers, tested proton 8 stable and proton experimental. From your message it sounds like you're using the windows version of steam, any reason why?

@simifor I'm just using the version of steam in the Arch repo, it's not the Windows version. Here's the output from pacman -Qs steam:

local/python-steamgriddb 1.0.5-2
    Python API wrapper for SteamGridDB.com
local/samrewritten-git r258.39d524a-1
    A Steam Achievement Manager For Linux.
local/steam 1.0.0.78-2
    Valve's digital software delivery system

@simifor I'm just using the version of steam in the Arch repo, it's not the Windows version.
Well, you said the following: " Recently wine has started saying mono is not installed when I launch steam" which doesn't make sense unless you're launching the windows version of steam, though I had missed your logs ina previous message.

Anyway, your crash log from the game says that your data is corrupted. Have you tried to verify the gae files to see if they haev an effect?

I have, nothing is caught. I've also re-installed the game and that hasn't fixed anything.

@something12356 I'm comparing against my crash log, and I see that data4 and data7 aren't loaded in my case, do you have DLC installed?

No, I don't own any DLC for the game. I could try deleting data4 and data7 and seeing if that works. I'll get back to you after I've tried that.

@simifor That fixed it, thank you! I'm not sure why those files were there but deleting them makes the game work.

I'm glad that it was solved

If I enable d3d12 raytracing the game crashes on launch :/

steam-534380.log
crash_20240901_024455290.log
steam-hwinfo.txt

Runs fine without it though, not sure if it's a vkd3d issue or something else. I've tried a lot of different launch options (PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 DXVK_ASYNC=1 VKD3D_FEATURE_LEVEL=12_1 VKD3D_CONFIG=dxr,dxr11 PROTON_ENABLE_NGX_UPDATER=1) and 3 different proton versions (GE, Experimental and 9.0-2) but nothing seems to have an effect, it surprises me a little because other people have confirmed they got raytracing working.

I was also interestingly not able to run the game (with default settings, e.g. no raytracing) on wayland either, neither with my amd igpu or with my nvidia dgpu, i was on hyprland specifically, the game launched, it didn't crash, but it didn't render it just displayed my desktop wallpaper for some reason (not a snapshot of my desktop as is often the case with issues like this, no it specifically showed the desktop wallpaper only). But it ran fine on X11.

@Rabcor I reproduced the same crash with Wayland, 560.35.03 and RTX 3070 when I enabled ray tracing. When I switched to 550.40.71 (the latest beta driver) the game launched and I could get in-game just fine with the same settings. Maybe you'll have more luck with that version?

@Rabcor I reproduced the same crash with Wayland, 560.35.03

Hmm I can at least confirm I'm on 560.35.03 as well, installing the beta is a bit much of a hassle for me currently though, I'm on arch btut the 560.40 beta doesn't seem to be available in AUR yet, i'll let you know when I figure something out.

OS: Arch Linux
NVIDIA driver version: 560.35.03
GPU: RTX 3060 12GB
The game crash after enabling Ray Tracing features.

For me the Nvidia 560 driver doesn't work with dx12 and ray tracing (game only starts in dx11 mode), while reverting back to 550 works good.

The game with the most recent Proton Experimental version stuck randomly frequently.

steam-534380-5.zip
steam-534380-4.zip
steam-534380-3.zip
steam-534380-2.zip
steam-534380-1.zip

@Rabcor

game launched, it didn't crash, but it didn't render it just displayed my desktop wallpaper for some reason

Not sure if you already solved this, but I was getting the same problem, for me changing WindowMode attr in ~/.local/share/Steam/steamapps/compatdata/534380/pfx/drive_c/users/steamuser/Documents/dying light 2/out/settings/video.scr (your steam location could be different, so not sure) from WindowMode(1) → WindowMode(0)

After doing this, I was able to make the game render and not only show me my wallpaper when trying to full-screen it.

Not sure if anything else renders the game unable to load, but I tried changing from low to high graphics and nothing weird happened (did not test ray tracing)

OS: Arch 6.12.4
NVidia: 565.77

OS: Arch Linux NVIDIA driver version: 560.35.03 GPU: RTX 3060 12GB The game crash after enabling Ray Tracing features.

This is still happening as of latest updates.

System Information

• GPU: RTX 4070 Ti
• Video driver version: 570.86.16
• Kernel version: 6.13.0-3-cachyos
• Link to full system information report as Gist: https://gist.github.com/frozen-sea/96016d62a33e1e24187439688062bbef
• Proton version: experimental-bleeding-edge-9.0

Symptoms

Game starts and runs fine on first start, but enabling ray tracing in options causes it to crash and fail to start. Need to set VKD3D_CONFIG=nodxr in order for the game to start again.

Reproduction

• Start game
• Open options, change to ray tracing preset
• Game will prompt to restart, accept

steam-534380.log

This seems to be relevant part:

18360.112:012c:0130:warn:seh:dispatch_exception backtrace: --- Exception 0xc0000094.
18360.112:012c:0130:trace:seh:dispatch_exception code=c0000094 flags=0 addr=000073331F26F8BC ip=73331f26f8bc
18360.112:012c:0130:warn:seh:dispatch_exception EXCEPTION_INT_DIVIDE_BY_ZERO exception (code=c0000094) raised
18360.112:012c:0130:trace:seh:dispatch_exception  rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000000
18360.112:012c:0130:trace:seh:dispatch_exception  rsi=0000000000000000 rdi=00000001000fb98c rbp=0000000000000000 rsp=00000001000fb978
18360.112:012c:0130:trace:seh:dispatch_exception   r8=0000000000000000  r9=0000555577f57f38 r10=ffffffffffffffff r11=3f10119bbde353ef
18360.112:012c:0130:trace:seh:dispatch_exception  r12=00000001000fbe88 r13=00000001000fbe80 r14=0000555577edccd8 r15=0000555577d14010
18360.112:012c:0130:trace:seh:call_vectored_handlers calling handler at 00006FFFF15C0680 code=c0000094 flags=0
18360.112:012c:0130:trace:seh:call_vectored_handlers handler at 00006FFFF15C0680 returned 0
18360.112:012c:0130:trace:seh:call_vectored_handlers calling handler at 00006FFFF1EAB1D0 code=c0000094 flags=0
18360.112:012c:0130:trace:seh:call_vectored_handlers handler at 00006FFFF1EAB1D0 returned 0
18360.112:012c:0130:trace:seh:call_vectored_handlers calling handler at 00006FFFF1ABB190 code=c0000094 flags=0
18360.112:012c:0130:trace:seh:call_vectored_handlers handler at 00006FFFF1ABB190 returned 0
18360.112:012c:0130:trace:seh:call_vectored_handlers calling handler at 00006FFFF22FC060 code=c0000094 flags=0
18360.112:012c:0130:trace:seh:call_vectored_handlers handler at 00006FFFF22FC060 returned 0
18360.112:012c:0130:trace:unwind:dwarf_virtual_unwind function 73331f26f8bc base 0x73331f26f8a0 cie 0x73332449b600 len 14 id 0 version 1 aug 'zR' code_align 1 data_align -8 retaddr %rip
18360.112:012c:0130:warn:seh:dwarf_virtual_unwind backtrace: 0x73331f26f8bc: /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libnvidia-rtcore.so.570.86.16 + 0x86f8bc.
18360.112:012c:0130:trace:unwind:execute_cfa_instructions 73331f26f8a0: DW_CFA_def_cfa %rsp, 8
18360.112:012c:0130:trace:unwind:execute_cfa_instructions 73331f26f8a0: DW_CFA_offset %rip, -8
18360.112:012c:0130:trace:unwind:dwarf_virtual_unwind fde 0x733324553550 len 10 personality (nil) lsda (nil) code 73331f26f8a0-73331f26f8cb
18360.112:012c:0130:trace:unwind:dwarf_virtual_unwind next function rip=000073331f26f905
18360.112:012c:0130:trace:unwind:dwarf_virtual_unwind   rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000000
18360.112:012c:0130:trace:unwind:dwarf_virtual_unwind   rsi=0000000000000000 rdi=00000001000fb98c rbp=0000000000000000 rsp=00000001000fb980
18360.112:012c:0130:trace:unwind:dwarf_virtual_unwind    r8=0000000000000000  r9=0000555577f57f38 r10=ffffffffffffffff r11=3f10119bbde353ef
18360.112:012c:0130:trace:unwind:dwarf_virtual_unwind   r12=00000001000fbe88 r13=00000001000fbe80 r14=0000555577edccd8 r15=0000555577d14010
18360.112:012c:0130:err:seh:call_stack_handlers invalid frame 00000001000FB978 (0000000000022000-0000000000120000)
18360.112:012c:0130:err:seh:NtRaiseException Exception frame is not in stack limits => unable to dispatch exception.
18360.238:0030:0218:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
18360.239:0030:021c:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
18360.239:0030:0220:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
pid 85518 != 85517, skipping destruction (fork without exec?)

Edit: Did more testing on other systems.

Points of comparison:

• Arc A580 (Mesa 24.3.4) can launch in DX12 mode, but doesn't have any RT options available, even with VKD3D_CONFIG=dxr
• Steam Deck has the RT options, they can be enabled, and they work correctly (albeit with SD RT performance :))

For reference, the problem with the crash on startup when RT is enabled was reported to Nvidia here.

@Freegnu-fr it's working fine on my end with proton experimental and hotfix*. I have a 9070 but my driver and kernel versions are more recent than yours, mesa git 26.1 (6ebb502ab9e) and mesa 25.3.5 both, with linux 6.18.9, so there's a good chance the game will work if you update either your kernel or mesa drivers.

*In general, it's not a good ideal to manually use proton hotfix. That gets updates when specific games need an update to work, and when that's the case, said games are pinned to use it by default. Though it's not the issue here given that it works for me, it's worth keeping that in mind.

Okay, I'll see if it's possible to switch to a more recent kernel, and the same goes for Mesa, but not on my current distribution. I'll do a separate installation