protonscr

World of Warcraft on Intel Arc A770 / Linux: D3D12 works, VKD3D reports SM 6.8 + DXR 1.1, but WoW still detects sm:dx_5_0 and rt:None

vkd3dopen
HansKristian-Work/vkd3d-proton#2875 · opened 2026-03-13 by Olifnoctebrise · updated 2026-03-13 · 2 comments · github
OOlifnoctebrise 2026-03-13 github

Hello,

I am reporting a reproducible issue with World of Warcraft Retail on Linux.

System:

  • GPU: Intel Arc A770 16 GB
  • OS: Bazzite KDE
  • Launcher: Lutris
  • Runner: latest GE-Proton
  • API forced in WoW: D3D12

Problem:
World of Warcraft launches successfully in D3D12, but ray tracing remains unavailable in-game (checkbox greyed out).

Important detail:
On the same machine, under Windows, ray tracing works correctly in WoW.
So the GPU and the game do support RT in general on this hardware.

What I observed on Linux:

  • WoW successfully creates a D3D12 device
  • VKD3D log reports Shader Model 6.6/6.7/6.8 and DXR 1.1 enabled
  • but WoW still detects:
    • sm:dx_5_0
    • rt:None

This suggests that D3D12 is working, and VKD3D reports DXR capabilities, but WoW itself still falls back to a lower feature/shader model for capability detection.

Relevant WoW gx.log excerpts:
Force API D3D12
Adapter 0: "Intel(R) Arc(tm) A770 Graphics (DG2)" 16GB ... dx11:false dx12:true
GpuInfo: sm:dx_5_0, rt:None, vrs:2, bary:0, mesh:1 pull:1
D3d12 Device Create Successful
Using shader family dx_5_0

Relevant VKD3D log excerpts:
VKD3D_CONFIG='dxr'
d3d12_device_caps_init_shader_model: Enabling support for SM 6.6.
d3d12_device_caps_init_shader_model: Enabling support for SM 6.7.
d3d12_device_caps_init_shader_model: Enabling support for SM 6.8.
d3d12_device_determine_ray_tracing_tier: DXR support enabled.
d3d12_device_determine_ray_tracing_tier: DXR 1.1 support enabled.

Things already tested:

  • WoW forced to D3D12
  • latest GE-Proton in Lutris
  • no DLL overrides
  • no PROTON_USE_WINED3D
  • no WINEDLLOVERRIDES
  • tested with and without VKD3D_CONFIG=dxr
  • reset WoW config/cache (WTF and Cache renamed)
  • D3D12 path works consistently
  • issue persists

Expected behavior:
If VKD3D exposes SM 6.x and DXR 1.1 correctly, WoW should detect ray tracing support and enable the RT option.

Actual behavior:
WoW launches in D3D12, but still reports sm:dx_5_0 and rt:None, and ray tracing stays disabled.

[gx.log]
Force API D3D12
Adapter 0: "Intel(R) Arc(tm) A770 Graphics (DG2)" 16GB family:DG2 type:Discrete location:0 driver_date:13-Mar-2026 driver_ver:32.0.65535.65535 vendor:0x8086 device:0x56a0 dx11:false dx12:true
GpuInfo: sm:dx_5_0, rt:None, vrs:2, bary:0, mesh:1 pull:1
D3d12 Device Create Successful
Using shader family dx_5_0

[vkd3d-wow.log]
VKD3D_CONFIG='dxr'
d3d12_device_caps_init_shader_model: Enabling support for SM 6.6.
d3d12_device_caps_init_shader_model: Enabling support for SM 6.7.
d3d12_device_caps_init_shader_model: Enabling support for SM 6.8.
d3d12_device_determine_ray_tracing_tier: DXR support enabled.
d3d12_device_determine_ray_tracing_tier: DXR 1.1 support enabled.

Thanks for help !

Ddoitsujin maintainer 2026-03-13 github

Game probably checks for more than just RT support, and I don't think we can expose FL12_2 on Alchemist due to missing features.

Can always try VKD3D_FEATURE_LEVEL=12_2, but there's a chance that it just blows up.

BBlisto91 2026-03-13 github

Still missing a bit for anv to be able to report feature level 12_2 out of the box via vkd3d-proton yea. If that is indeed the issue.
See https://gitlab.freedesktop.org/mesa/mesa/-/issues/12425

Launch options