VKD3D-Proton 3.0.1 Release Brings Better Frame Pacing and Mobile GPU Fixes
The latest update to the Direct3D to Vulkan translation layer lands as version 3.0.1, focusing heavily on frame pacing stability and mobile chip performance. This release quietly patches a handful of stubborn game crashes while laying groundwork for descriptor heap support down the line. Players running Linux or using Proton on Steam Deck will notice smoother rendering in several recent titles without needing to tweak config files manually.
Performance Tweaks for Mobile and Copy Queues
The developers spent most of their time optimizing how the translation layer handles mobile GPUs that rely on tiling architectures. Deferred clears and discards now run more efficiently, which means fewer wasted cycles when rendering complex scenes. Render pass suspend and resume logic got a proper overhaul so drivers can actually optimize around them instead of choking on state changes. Query pool initialization moved around to prevent render pass breaks, and MSAA resolves were reworked to give graphics drivers an easier time doing their job. The copy queue finally uses a dedicated Vulkan TRANSFER queue when available, which should speed up asset streaming noticeably. Many users have reported setups choking on ExecuteIndirect commands during heavy asset streaming, which is why the new batched system matters so much for titles like Starfield and Halo Infinite.
Fixes for Frame Pacing, Reflex, and Shader Compilers
Frame pacing just got a serious upgrade with support for VK_EXT_present_timing. This feature keeps frame delivery smooth when vertical sync intervals exceed one, which eliminates the stutter that usually shows up during heavy load transitions. NVIDIA Reflex performance improved after developers decoupled the NVAPI present ID from their own internal tracking. That change lets frame generation tools signal timing issues properly instead of guessing. The shader compiler received several patches to stop new titles from crashing on startup. A regression in F1 2019 and 2020 got fixed by carrying over an old workaround into the newer code path. SV_PrimitiveID can now be read across more shader stages without throwing errors, which clears up rendering glitches in older DirectX 12 games.
Workarounds for Specific Games and Hardware Quirks
The update ships with a new workaround system that targets shader entry point names instead of relying on volatile hash values. Game developers love changing those hashes every other patch, so this change stops titles like Wuthering Waves from breaking unnecessarily. Several known game bugs get patched directly into this release, including fixes for Shadows of the Tomb Raider, Rise of the Tomb Raider, Spider Man 2, Death Stranding 2, Guardians of the Galaxy, REANIMAL, and Crimson Desert. RDNA4 users on older Mesa drivers will benefit from a shading rate workaround that gets disabled automatically once version 26.1 arrives. Monster Hunter Wilds finally stops fighting with a null shared memory pointer issue after a year and a half of troubleshooting. NVIDIA kernel fence wait performance improves thanks to a targeted optimization, while RDNA1 cards can now pretend they support barycentrics and variable rate shading just enough to run Crimson Desert without crashing.
What Comes Next for the Translation Layer
This version sits right before VK_EXT_descriptor_heap lands in the codebase, which means a lot of heavy lifting is already queued up behind the scenes. Cleaning out those legacy NV device generated command paths was long overdue. Modern drivers do not need that bloat anymore, so removing it keeps the translation layer lean and reduces confusion for anyone trying to debug rendering issues. Independent devices support made it into this build, and AGS WMMA operations now handle FSR4 ray reconstruction and denoising tasks correctly. Up-to-date dxvk-nvapi setups will also expose shader execution reordering extensions without needing manual config edits. The release notes mention Turnip passing the test suite after several compiler fixes, which points to better compatibility for Adreno mobile chips going forward.
Release VKD3D-Proton 3.0.1
This is likely the last release before VK_EXT_descriptor_heap lands. There are some practical reasons why this is 3.0.1 instead of 3.1, but numbers don't really matter that much anyway.
Grab the update and let it run its course. Most of these changes just sit quietly in the background until a game actually triggers them, so no manual tweaking is required. Enjoy the smoother frame delivery and fewer crashes on whatever hardware you are running.
