DXVK 3.1 Lands With Targeted Fixes and Intel GPU Groundwork
The latest Vulkan translation layer update stabilizes the massive 3.0 rewrite while quietly preparing Valve's Proton stack for Intel discrete GPUs.
DXVK 3.1 shipped today, bringing a focused set of bug fixes and infrastructure tweaks to the translation layer that powers most Windows gaming on Linux. It is not the seismic shift that v3.0 was a couple months ago. This is the follow-up patch that actually stitches the seams after June's architectural overhaul.
Philip Rebohle, known on GitHub as doitsujin, is the sole maintainer behind the project. The repository has accumulated roughly 17,900 stars, 1,200 forks, and over 8,200 commits across its lifetime. Licensed under Zlib, DXVK translates Direct3D 8 through 11 calls into Vulkan at runtime, which means Windows titles can run through Wine without ever touching Microsoft's graphics stack.
What Actually Changed in 3.1
The release nails a long-standing cloud rendering bug in Battlefield 3. DXVK 3.1 now implements D3D11 buffer render targets, which older Frostbite engine titles rely on to paint certain visual layers. The implementation emulates the feature by creating an internal 1D texture. It is strictly a correctness fix rather than a performance play, though it finally makes those misbehaving clouds render properly.
Intel-specific extensions are now loaded automatically when an Intel GPU is detected. This change does nothing for you today if you are not running an Intel discrete card, but it is a direct prerequisite for future Proton D3D11 Intel vendor extension support. It mirrors how AMDAGS and NVAPI work right now. If Valve ever decides to fully back Intel discrete GPUs for gaming, this is the groundwork.
DXVK also added basic DXGI present parameter handling. The change fixes UI rendering in VirtualDJ and various game launchers including Ubisoft Connect. When your driver supports VK_KHR_incremental_present, DXVK can forward dirty rectangles straight to Vulkan, which trims compositor overhead. It is a quality-of-life bump for menus and overlays rather than anything that moves frames in a competitive shooter.
The real headline here is what got fixed. A D3D9 fog regression that broke The Witcher 1, Mabinogi, and several others is finally gone. Nvidia users who hit out-of-memory crashes with descriptor heaps enabled can now rely on a baked-in workaround. You can also flip dxvk.enableNvCudaInterop to disable DLSS if you need a clean escape hatch. Ghost Recon Breakpoint's water and shader pipeline issues on Nvidia are patched. RaceRoom Racing Experience's web UI on Proton 11 finally renders correctly.
Community reaction has been deliberately muted. Six reactions on the v3.1 release page compared to 233 for v3.0. If you are keeping score, that is the expected pattern after a massive architectural earthquake. The v3.0 jump replaced the legacy shader compiler with dxbc-spirv, moved to descriptor heaps, switched the D3D9 fixed-function pipeline to ubershaders, and now mandates Vulkan 1.4. Most users are still running in those shoes, and patch notes like these are exactly what keeps the stack from fraying at the edges.
The Technical Baseline
DXVK 3.0 requires Vulkan 1.4. AMD's Windows drivers for RDNA1 and RDNA2 GPUs have lost feature updates and now fall back to the older binding model. Affected users either stick with DXVK 2.x or pivot to Linux entirely. Build requirements remain Wine 10.0+, Meson 0.58+, MinGW-w64 10.0+, and glslang. The project stays under the Zlib license and continues to sit as the de facto backbone of Valve's Steam Play / Proton compatibility layer.
It is a pragmatic update that does not try to do everything at once. The D3D11 buffer target fix is strictly correctness over speed, which makes sense for legacy Frostbite titles. The Intel extension prep is quietly the most strategically interesting piece, even if you will not see the payoff in a benchmark today. However, at the same time, DXVK's trajectory now hinges heavily on upstream Proton decisions. Valve's packaging choices will dictate whether these changes actually reach most gamers.
Keep in mind that if you are running a 32-bit D3D9 setup or older Frostbite titles, updating to 3.1 will likely smooth out some of the rough edges from June.
Head here to grab the latest release and full changelogs.
