protonscr

Failed to create Vulkan device, vr -7 on RTX 4080 with driver 610.57.04 (Hunt: Showdown 1896)

vkd3dopen
HansKristian-Work/vkd3d-proton#3205 · opened 2026-08-07 by Ecczo612 · updated 2026-08-21 · 4 comments · github
EEcczo612 2026-08-07 github

Game launches, EAC briefly appears then closes, and the game shows a false "Unsupported Graphics Card / D3D FeatureLevel 11.0 required" dialog on a card that clearly supports it (confirmed via vulkaninfo). Log shows vkd3d_create_vk_device failing with vr -7 (VK_ERROR_EXTENSION_NOT_PRESENT), preceded by warnings about disabling shader_float_controls2 and missing coopmat/WMMA support. Reproduces identically across 3 different Proton builds and 2 kernels (bore, LTS), with prefix/shadercache wiped. Tried disabling VK_NV_cooperative_matrix2 and VK_KHR_shader_float_controls2 via VKD3D_DISABLE_EXTENSIONS — no change. Tried WINEDLLOVERRIDES="d3d12=" — no change.
PS: I'm a total beginner. AI generated contrent.

Software information

Hunt: Showdown 1896 (Steam AppID 594650), DX11 title. Steam Overlay disabled for testing, no launch options at time of log.

System information

  • GPU: NVIDIA GeForce RTX 4080
  • Driver: 610.57.04 (nvidia-open)
  • Wine version: Proton Experimental (also reproduced on Proton 9.0-4 and proton-cachyos-11.0-20260703)
  • VKD3D-Proton version: 3.1.0 (build 3dfc6f07d0953b1)

Log files

hunt-vkd3d-crash.txt

EEcczo612 2026-08-09 github

Additional data point:

I have a second machine also running driver 610.57.04 (same CachyOS setup), but with an RTX 5090 instead — Hunt: Showdown runs perfectly on it, no vkd3d-proton errors at all. Same driver version, different GPU architecture (Ada Lovelace 4080 vs Blackwell 5090). This suggests the vr -7 failure may be specific to how vkd3d-proton negotiates the shader_float_controls2 workaround / coopmat-WMMA feature detection on Ada-class cards rather than a general driver regression.

EEcczo612 2026-08-09 github

Update:

Found a related report on NVIDIA's own Developer Forums that points at the driver rather than vkd3d-proton:

https://forums.developer.nvidia.com/t/610-43-02-rtx-5080-vkcreatedevice-returns-vk-error-initialization-failed-when-cooperativematrix-feature-is-enabled-vkcreatedevice/371808

On driver 610.43.02, vkCreateDevice returns VK_ERROR_INITIALIZATION_FAILED when cooperativeMatrix is enabled, despite vkGetPhysicalDeviceFeatures2 reporting cooperativeMatrix = true for the device — a Vulkan spec violation (vkCreateDevice must not fail if the feature was reported as supported). That report was against an RTX 5080 (Blackwell).

I also tested on a second machine — same 610.57.04 driver, but an RTX 5090 (Blackwell) — and Hunt: Showdown launches with no issues there. Only the RTX 4080 (Ada Lovelace) machine fails. So this may be an Ada-specific instance of the same underlying driver capability-reporting bug that's already been reported against Blackwell, possibly not yet fully fixed across both architectures in 610.57.04.

Given this looks driver-side rather than vkd3d-proton-side, I'll also file directly with NVIDIA — linking back here for cross-reference.

EEcczo612 2026-08-20 github

Anyone?

BBlisto91 2026-08-21 github

Did you file the Nvidia issue?

Proton versions

Launch options