Wrong repo, dxvk only goes up to DirectX 11
This is a dx12 game
Edit:
Link to proton issue report
https://github.com/ValveSoftware/Proton/issues/9595#issuecomment-5219829166
The logs do mention DxvkMemoryAllocator so it's probably trying to do some resource sharing across D3D12 and D3D11.
Tested on two different Proton builds: GE-Proton11-3 and proton-cachyos-11.0-20260703-slr — same result on both.
I don't think that's the issue here but for the record: Please at least try official Proton releases...
I mean Pascal is on life support when it comes to modern D3D12 games, not sure if this is unexpected. But yeah, this is primarily a D3D12 game and we don't do D3D12 here.
so it's probably trying to do some resource sharing across D3D12 and D3D11.
Yes, for video stuff only.
ge-proton11-3x2 2026-08PROTON_LOG=1x1 2026-08PROTON_VKD3D_HEAP=1x1 2026-08VKD3D_CONFIG=descriptor_heap,enable_experimental_featuresx1 2026-08VKD3D_CONFIG=descriptor_heap,enable_experimental_features PROTON_VKD3D_HEAP=1 PROTON_LOG=1 %command%x1 2026-08
Summary
The game environment (world geometry, terrain, skybox) renders correctly, but character and object models fail to load/render entirely. The game itself starts and runs (no crash), but is unplayable with models missing.
Log Evidence
The following warning repeats continuously in the Proton log during gameplay:
warn: DxvkMemoryAllocator::createImageResource: Failed to open shared NT handle
This appears at high frequency (tens of repeats per second) for the duration of the session.
Steps Taken to Rule Out Local Causes
Cleared all shader caches (Steam shadercache, Mesa shader cache, NVIDIA GLCache) — issue persisted.
Fully deleted and regenerated the Proton compatdata prefix from scratch — issue persisted.
Tested on two different Proton builds: GE-Proton11-3 and proton-cachyos-11.0-20260703-slr — same result on both.
Tried VKD3D_CONFIG=descriptor_heap,enable_experimental_features PROTON_VKD3D_HEAP=1 launch options (relevant to a separate, unrelated D3D12/vkd3d-proton crash issue on RTX 50-series cards) — no effect, as expected, since this warning originates in DXVK (D3D11 path), not vkd3d-proton (D3D12 path).
Confirmed NVIDIA driver (580.173.02) is well below the 595.x branch associated with other unrelated Crimson Desert issues on newer NVIDIA architectures.
Software information
Crimson Desert,
run as non-steam game,
launch options:VKD3D_CONFIG=descriptor_heap,enable_experimental_features PROTON_VKD3D_HEAP=1 PROTON_LOG=1 %command%.
System information
Log files
crimson-desert-trimmed.log