I actually have this same issue. I've worked around it by enabling DXVK_LOG_LEVEL=info or disabling fsync and using esync (server sync doesn't work either)
Caused by the vulkan luid commit for xwayland. Seems like there's some race going on.
Scratch this, my issue is unrelated to this, I did not read the issue in it's entirety.
UPDATE: It appears that something might've broke vkd3d for specific games, because I was able to launch gears 5 and get to the usual xbox game studio and mangohud confirmed I'm using vkd3d 2.3.1
Interesting find by user ZereoX while trying F1 2020, he states that the game shows that the windows version doesn't support D3D12 and linked me to this specific change: https://github.com/ValveSoftware/wine/commit/a2adb204b2c2e8a2a54ed7c8cd20075c6822f722
Ghostrunner is broken too when starting in DirectX 12 mode.
@kodatarule It looks like this was a wine regression: https://bugs.winehq.org/show_bug.cgi?id=51080
Fix commit will be in the next Proton release :)
This should be resolved in today's Proton Experimental release. We'll move the fix over to 6.3 soon.
This issue is hopefully fixed in the Proton 6.3-4 RC candidate, see #4821.
Yep seems resolved with Proton 6.3-4 RC!
Thanks everyone for reporting and testing. 6.3-4 is released now, so I'll close this issue.
proton 6.3-4x2 2021-05proton experimentalx2 2021-05proton 6.3-3x1 2021-05DXVK_LOG_LEVEL=infox1 2021-05
Compatibility Report
System Information
I confirm:
Symptoms
It says that there is no d3d12 device and even if a game is able to launch it launches it with d3d11.
Reproduction
Try to run any d3d12 application.
steam-564310.log
steam-673130.log