Thanks for the report. I have captured the shader causing the crash with PT enabled and I think this could be a bug in dxil-spirv. When I run the spirv through spirv-val I get the following error:
error: line 21465: Block '20097[%20097]' appears in the binary before its dominator '19897[%19897]' %19897 = OpLabel
@HansKristian-Work could you take a look at this?
PROTON_LOG=1`x1 2026-04VKD3D_CONFIG=descriptor_heap,x1 2026-04VKD3D_CONFIG=vk_debug,breadcrumbs`x1 2026-04VKD3D_CONFIG=vk_debug,dxr12,breadcrumbs`x1 2026-04VKD3D_DEBUG=debug`x1 2026-040x80004005x1 2026-04
Software information
Running PRAGMATA (steam ID: 3357650) with proton-cachyos on Nvidia 595. Adding
/WineDetectionEnabled:Falseto game launch options to expose RT settings (without this, RT options don't appear at all ingame), and then enabling path tracing in settings crashes the game with errorFATAL D3D ERROR (1, E_FAIL, 0x80004005).Game doesn't crash if ray tracing alone is enabled, only if path tracing is also enabled.
System information
Log files
VKD3D logs (debug build, built from https://github.com/HansKristian-Work/vkd3d-proton/pull/2943):
VKD3D_CONFIG=vk_debug,breadcrumbsandVKD3D_DEBUG=debugvkd3d-log-pragmata-ptcrash.txt
VKD3D_CONFIG=vk_debug,dxr12,breadcrumbsandVKD3D_DEBUG=debug(dxr12 didn't help, I was just curious)vkd3d-log-pragmata-ptcrash-dxr12.txt
Suspicious bits, but not sure if these happen before the crash or as a result of the crash:
Unfortunately I can't collect usable proton logs, because even a 10 second session to repro the crash from the main menu settings is like 3 GB in size. Also adding
PROTON_LOG=1somehow gets rid of the error message dialog box (but the game still does crash). I attached a 1k line tail of that log here, but let me know if I can help find something specific in there.steam-3357650-tail.log