fixme:vulkan:NtGdiDdDDIDestroyAllocation params 0x... stub!
Not relevant, and this spam is resolved on master anyway.
fixme:vulkan:NtGdiDdDDIDestroyAllocation params 0x... stub!
Not relevant, and this spam is resolved on master anyway.
I don't quite understand how exactly?
That spam doesn't mean anything is wrong. That spam is removed on master.
That spam doesn't mean anything is wrong. That spam is removed on master.
The hard-freeze (game process hangs, system is fine) is still 100% reproducible for me on Manjaro/NVIDIA, but it happens only when joining a multiplayer match (which seems to be triggered by EAC).
Since the log is 'clean' of real errors, do you have any other ideas what could be causing this specific EAC/NVIDIA hang? Is there a debug build I could run?
(Just to confirm, I have already tried a clean NVIDIA driver reinstall (580.82.09), switched kernels (6.12 and 6.6-LTS), and cleared all caches, with no success).
which seems to be triggered by EAC
Not sure what we can do in D3D12 when it's likely anti-cheat related?
ge-proton10-25x1 2025-11proton 9.0-4x1 2025-11proton experimentalx1 2025-11DXVK_CONFIGx1 2025-11PROTON_LOG=1`.x1 2025-11
System Information
Symptoms
The game runs perfectly fine in menus or any single-player mode.
The moment I try to join a multiplayer match, the game freezes completely (image is static, audio hangs or loops). The rest of the system (Manjaro desktop) remains perfectly responsive.
This freeze is 100% reproducible and seems to be triggered by EasyAntiCheat (EAC) activating for the multiplayer session.
Steps to Reproduce
Log File
I have attached the Proton log generated with
PROTON_LOG=1.The log is spammed (thousands of times per second) with the following two lines, which appear to be the cause of the hang:
fixme:vulkan:NtGdiDdDDIDestroyAllocation params 0x... stub!trace:seh:__processing_throw ()This confirms
vkd3d-protonis hitting an unimplemented function ("stub") when EAC is active, causing the game process to hang.steam-2138720.zip
Troubleshooting Performed
To confirm this is not a local setup issue, I have already tried:
linux66).mhwd -randmhwd -a).DXVK_CONFIGand__GL_launch options.None of these steps solved the problem. This appears to be a hard bug in
vkd3d-proton's handling of this specific EAC-triggered function call.