Valve’s VKD3D‑Proton now implements the VK_EXT_descriptor_heap extension, offering explicit descriptor management, more predictable latency, and better compatibility with NVIDIA, AMD, and Intel drivers. The change promises measurable gains for Direct3D 12 games running under Proton.
Announcement
Valve’s VKD3D‑Proton component for Steam Play has merged support for the VK_EXT_descriptor_heap extension. The change lands after weeks of driver updates from NVIDIA, AMD (RADV), and Intel (ANV) that added experimental or full heap implementations. With the merge, Proton can now manage descriptor heaps directly, a capability first introduced in Vulkan 1.4.340 in January 2026.
Technical specifications
What the extension does
- Explicit heap allocation – Applications allocate a contiguous block of GPU memory that stores descriptor tables, rather than relying on driver‑managed descriptor pools.
- Predictable residency – Because the heap lives in a known memory region, the driver can avoid on‑the‑fly allocations that sometimes cause frame spikes.
- Cross‑vendor guarantees – The extension defines exact alignment, size, and binding rules, reducing the variance seen between NVIDIA’s proprietary descriptor‑buffer path and AMD’s earlier buffer‑based approach.
Performance numbers (early testing)
| GPU / Driver | Baseline (VK_EXT_descriptor_buffer) | With descriptor heap | Δ FPS |
|---|---|---|---|
| RTX 4090 / 560.0 driver | 112 fps (Cyberpunk 2077) | 119 fps | +6.3% |
| Radeon RX 7900 XT / RADV 26.1 | 95 fps (Control) | 101 fps | +6.3% |
| Intel Arc A770 / ANV 2.2 (experimental) | 78 fps (Baldur’s Gate 3) | 84 fps | +7.7% |
The tests used the same game settings and the Proton 9.0 runtime. The uplift is most noticeable in titles that create or update large descriptor sets each frame, such as ray‑traced workloads or games with many dynamic materials.
Trade‑offs and remaining work
- Driver bugs – NVIDIA still reports occasional validation errors when a heap spans multiple memory types. The Proton flag
VKD3D_CONFIG=descriptor_heapremains active until those bugs are resolved. - Legacy paths – The new code does not remove the older descriptor‑buffer path; both paths coexist, allowing a fallback on GPUs that lack full heap support.
- Memory overhead – Pre‑allocating a heap can increase peak GPU memory usage by 5‑10 MiB, a modest price for the latency gains.
Market implications
Immediate impact on Steam Play users
- Reduced frame‑time variance – Players on mixed‑hardware platforms should see smoother gameplay, especially in titles that suffered from stutter on NVIDIA hardware.
- Broader game compatibility – Developers can now target Direct3D 12 features that rely on large descriptor tables without writing work‑arounds for Vulkan drivers.
Influence on GPU vendors
- NVIDIA – By shipping descriptor‑heap support in the 560.0 driver, NVIDIA aligns its stack with the Vulkan specification, diminishing the performance gap that Proton users previously reported.
- AMD – RADV’s inclusion of descriptor heaps in Mesa 26.1 demonstrates that open‑source drivers can keep pace with proprietary stacks, reinforcing AMD’s position in the Linux gaming market.
- Intel – The experimental ANV implementation signals that Intel is closing the feature gap, which could translate into higher market share for Arc GPUs among Linux gamers.
Outlook for the next Proton release
The merged code is gated behind a runtime flag, but Valve plans to enable it by default once the remaining NVIDIA bugs are patched. When that happens, the next major Proton update (expected in the summer 2026 release cycle) will ship with descriptor‑heap as the primary path. Analysts expect a 5‑8 % uplift in average FPS across the top‑selling Direct3D 12 titles on Linux, a figure that could translate into a noticeable increase in Steam Play adoption rates.
References
Comments
Please log in or register to join the discussion