DXVK 3.0.2 is now available, adding better diagnostics for Vulkan device-loss crashes and a small set of targeted fixes for Windows games running through Vulkan translation layers. As reported by Phoronix, the release addresses problems in Dying Light: The Beast, Granblue Fantasy: Relink, Halo: Combat Evolved, Overwatch, and Tom Clancy’s Splinter Cell: Chaos Theory.
DXVK translates Direct3D 8, 9, 10, and 11 calls into Vulkan. It is most familiar as a component of Valve’s Proton compatibility stack on Linux and SteamOS, but it can also be used directly by Wine-based setups and by developers testing D3D applications through Vulkan.
The practical headline is a new
That error is notoriously unhelpful on its own: it says the Vulkan device is no longer usable, but not where a workload, driver, or application went wrong. The new mode is intended to narrow the likely crash location and generate more useful material for bug reports. DXVK says it works best on AMD and Nvidia GPUs.
For Windows users, this is not a new Windows graphics-driver diagnostic feature, nor does it repair a native DirectX game crash. It matters chiefly to people using DXVK in a nonstandard Windows configuration, Wine users, and developers or support staff investigating failures in Proton-style environments. The logging has to be enabled before reproducing the crash; it is not a universal cure for GPU hangs.
Other changes include:
DXVK’s GitHub release notes mark version 3.0.2 as the current release, published July 17, while Phoronix reported the update on July 18 UTC. Users relying on Proton will generally receive the changes when Valve or their chosen Proton build incorporates them; standalone DXVK users can update their own deployment and enable hang logging only when troubleshooting.
DXVK translates Direct3D 8, 9, 10, and 11 calls into Vulkan. It is most familiar as a component of Valve’s Proton compatibility stack on Linux and SteamOS, but it can also be used directly by Wine-based setups and by developers testing D3D applications through Vulkan.
Better evidence when the GPU driver falls over
The practical headline is a new DXVK_DEBUG=hang option. According to DXVK maintainer Philip Rebohle’s release notes, it produces additional logs when a GPU hang or driver crash leads Vulkan to return VK_ERROR_DEVICE_LOST.That error is notoriously unhelpful on its own: it says the Vulkan device is no longer usable, but not where a workload, driver, or application went wrong. The new mode is intended to narrow the likely crash location and generate more useful material for bug reports. DXVK says it works best on AMD and Nvidia GPUs.
For Windows users, this is not a new Windows graphics-driver diagnostic feature, nor does it repair a native DirectX game crash. It matters chiefly to people using DXVK in a nonstandard Windows configuration, Wine users, and developers or support staff investigating failures in Proton-style environments. The logging has to be enabled before reproducing the crash; it is not a universal cure for GPU hangs.
Game-specific repairs
The 3.0.2 patch also contains a workaround for a performance regression in games that create a new DXGI factory every frame. DXVK specifically calls out Dying Light: The Beast when AMD FidelityFX Super Resolution is enabled, while noting the issue could affect other Direct3D 12 games.Other changes include:
- A fix for spurious GPU hangs in Granblue Fantasy: Relink on Nvidia hardware, which may help other affected titles.
- A workaround for rendering problems in Halo CE.
- A potential swapchain fix for Overwatch at non-native display resolutions.
- A correction for incorrectly rendered night vision in Splinter Cell: Chaos Theory.
DXVK’s GitHub release notes mark version 3.0.2 as the current release, published July 17, while Phoronix reported the update on July 18 UTC. Users relying on Proton will generally receive the changes when Valve or their chosen Proton build incorporates them; standalone DXVK users can update their own deployment and enable hang logging only when troubleshooting.
References
- Primary source: Phoronix
Published: Sat, 18 Jul 2026 00:46:00 GMT
Loading…
www.phoronix.com