no_enhanced_barriers is not a valid VKD3D_CONFIG value. I would expect as much considering the AI generated emdash in that bullet point.
@dillonchoi1992 why didn't you include the very clearly required proton log (steam-3321460.log) the bug template tells you to attach? Gee.
So as to add this here, this is the proton log (Proton 10.0-4) in my machine
My data:
CPU : AMD 7800X3D
GPU: AMD Radeon RX 7900 XTX
RAM: 64 GB DDR5
Driver: Mesa 26.0.5
Other data: https://gist.github.com/Patola/d976c74e535de3a8e14041f3985552ae
Note that one user in the steam forums says the issue is that function: "vkd3d-proton: d3d12_device_QueryInterface: {3febd6dd-4973-4787-8194-e45f9e28923e} not implemented", this error also appears in my log:
[10:28] [10025] [patola@risadinha patola]% grep d3d12_device_QueryInterface steam-3321460.log
271974.972:015c:0160:warn:vkd3d-proton:d3d12_device_QueryInterface: {3febd6dd-4973-4787-8194-e45f9e28923e} not implemented, returning E_NOINTERFACE.
271975.216:015c:0160:warn:vkd3d-proton:d3d12_device_QueryInterface: {0742a90b-c387-483f-b946-30a7e4e61458} not implemented, returning E_NOINTERFACE.
same issue on my system
System:
Note that one user in the steam forums says the issue is that function: "vkd3d-proton: d3d12_device_QueryInterface: {3febd6dd-4973-4787-8194-e45f9e28923e} not implemented"
I think people are quick to assume they found the root cause when they see a warning in a log. To my knowledge that should not cause a crash. Looking at other issue reports with the same assumption, the vkd3d-proton maintainer also thinks so.
Same here.
Worked fine before 1.04 patch.
System:
Perhaps a maintainer/janitor should close this issue and refer to the existing #9595 issue... @kisak-valve potentially sorry for tag
Yes, please use #9595 for feedback related to running Crimson Desert with Proton.
Ya sorry this is AI-generated. After the update I could not figure out why its crashing and just had AI draft because it was late but sorry if it caused a hick up
proton 10.0-4x1 2026-04ge-proton10-34x1 2026-04proton experimentalx1 2026-04proton hotfixx1 2026-04VKD3D_CONFIGx1 2026-04PROTON_VKD3D_HEAP=1x1 2026-04VKD3D_CONFIG=no_enhanced_barriersx1 2026-04
Game: Crimson Desert (AppID 3321460)
Patch that broke it: 1.04.00 (released 2026-04-22)
Previously working: 1.03.x played fine for 100+ hours on same system
System:
Crash: STATUS_ACCESS_VIOLATION (c0000005) at CrimsonDesert.exe + 0x031EE054, every
launch, consistently.
Proton log shows this immediately before crash:
warn:vkd3d-proton:d3d12_command_list_process_enhanced_barrier_texture: NumPlanes ==
0 promotes to 1 plane.
[×175]
fixme:vkd3d-proton:d3d12_command_list_process_enhanced_barrier_texture:
Transitioning away from UNDEFINED, but there is no DISCARD flag. Uncertain what is
expected here. vkd3d-proton will force a discard.
→ crash
What I tried:
crashes
Root cause: 1.04 introduced new D3D12 enhanced barrier calls that trigger an
unhandled code path in d3d12_command_list_process_enhanced_barrier_texture.
vkd3d-proton forces a discard on a texture transitioning away from UNDEFINED
without a DISCARD flag — game then dereferences null and crashes.