DXVK 3.0.2 arrived on July 17, and the standout feature this time isn’t a game fix—it’s a new diagnostic tool that helps users and developers get to the bottom of one of Vulkan’s most maddening errors. When a GPU driver crashes or hangs, Vulkan throws VK_ERROR_DEVICE_LOST, a message that tells you the device is gone but almost nothing about why. DXVK’s maintainer, Philip Rebohle, has added a DXVK_DEBUG=hang option that spits out detailed logs right before the crash, giving you a fighting chance at identifying the culprit.

This release also ships targeted fixes for five games—Granblue Fantasy: Relink, Dying Light: The Beast, Halo: Combat Evolved, Overwatch, and Tom Clancy’s Splinter Cell: Chaos Theory—but the new hang logging steals the spotlight. It’s a direct response to the pain of diagnosing GPU hangs that leave no trace behind. While the tool doesn’t repair anything on its own, it turns an opaque failure into something you can actually troubleshoot.

New diagnostic firepower for GPU hangs

DXVK is the open-source translation layer that converts Direct3D 8, 9, 10, and 11 calls into Vulkan. It’s best known as the engine inside Valve’s Proton compatibility stack that lets thousands of Windows games run on Linux and Steam Deck, but you can also use it standalone on Windows itself—often to coax better performance out of older titles or to work around DirectX bugs. Version 3.0.2, published on GitHub on July 17 and reported a day later by Phoronix, adds the DXVK_DEBUG=hang option as a new environmental variable.

When a Vulkan application encounters a device loss—meaning the GPU driver has crashed, reset itself, or otherwise given up—the default behavior is to return VK_ERROR_DEVICE_LOST and bail out. The mistake could lie in the application’s rendering code, in DXVK’s translation, in the Vulkan driver, or even in the hardware itself. The new debug mode inserts logging checkpoints throughout DXVK’s command stream. If the device is lost, the last recorded checkpoint narrows down the operation that was in flight at the time of the crash, producing a log that shows roughly where things went off the rails.

According to Rebohle’s release notes, the feature “works best on AMD and Nvidia GPUs,” meaning the checkpoints are placed at positions that are most useful for those vendors’ driver stacks. It won’t prevent hangs, and you have to enable it ahead of time—there’s no retroactive detection—but for anyone wrestling with reproducible crashes, it provides actionable evidence that previously didn’t exist.

The option is disabled by default, so it won’t add any overhead to normal gameplay. When you’re ready to investigate a problem, you set DXVK_DEBUG=hang in the environment and launch the game as usual. If the hang occurs, DXVK writes a log before exiting, and that log can be shared with developers or used to craft a focused bug report. For support teams trying to diagnose Proton or Wine issues, this is a major step forward from the “it just crashes” reports they often receive.

Alongside the debugging upgrade, DXVK 3.0.2 introduces a handful of game-specific corrections. These aren’t patches to the games themselves; they’re adjustments inside DXVK that alter how the translation layer handles particular rendering patterns those titles use.

Granblue Fantasy: Relink saw spurious GPU hangs on Nvidia hardware, and maintainers identified and fixed the root cause. The same Nvidia-specific hang issue could have affected other titles that stress the driver in a similar way, so the fix may have broader reach.

Dying Light: The Beast had a performance regression when AMD FidelityFX Super Resolution was enabled. The underlying problem was more general: games that create a new DXGI factory every frame trigger an inefficient code path in DXVK. The workaround is targeted at Dying Light, but the release notes explicitly say the fix could help other Direct3D 12 games that exhibit the same pattern. If you saw stuttering or degraded frame rates with FSR turned on, this update should restore smoothness.

Halo: Combat Evolved benefits from a rendering workaround that addresses visual corruption. The exact nature of the glitch isn’t detailed, but DXVK often has to handle edge cases in older titles where the original DirectX implementation allowed non-standard behavior that Vulkan exposes differently.

Overwatch gains a potential swapchain fix when the game runs at non-native display resolutions. If you’ve been playing in a window or at a lower resolution and noticed tearing or presentation issues, this may clear them up.

Tom Clancy’s Splinter Cell: Chaos Theory had its night-vision rendering corrected. This is a classic compatibility-layer fix: a specific shader or render-state that worked under DirectX didn’t translate cleanly to Vulkan, and the correction restores the intended effect.

These are all delivered through DXVK’s usual update mechanism. There’s no separate patch to download; you just replace the DLLs or wait for your Proton distribution to do it for you.

Who benefits—and who doesn’t

The practical impact of DXVK 3.0.2 depends entirely on how you run your games.

Proton users (Steam Deck, Linux gamers) are the biggest audience. Valve typically integrates DXVK releases into Proton Experimental quickly, and then they trickle into the stable Proton versions. If you’re playing any of the five fixed titles through Steam and Proton, you’ll get the improvements automatically when your Proton build updates. You don’t need to do anything except ensure your system is current.

Standalone DXVK users on Windows are a smaller but significant group. People inject DXVK alongside games to bypass DirectX limitations—for example, to play older titles at high frame rates where the original API stumbles, or to work around graphical bugs. If you’re in this camp, you can download DXVK 3.0.2 from the project’s GitHub releases and swap the DLLs. The hang debugging option is particularly valuable for you because Windows-native Vulkan debugging tools are less common; DXVK_DEBUG=hang gives you a cross-platform diagnostic that works the same way on Windows as it does on Linux.

Developers and support staff gain a powerful new troubleshooting aid. The hang logs are meant to be shared in bug reports, and they provide a concrete starting point for investigations that previously required reproducing the crash under a profiler with Vulkan validation layers enabled—a complex and often slow process. The checkpoints can highlight whether the hang occurred during shader compilation, buffer mapping, or presentation, dramatically speeding up triage.

Native Windows gamers who don’t use DXVK should not expect any change. If you launch Granblue Fantasy: Relink, Overwatch, or the other titles through their normal DirectX paths—which is what virtually all Windows users do by default—DXVK never enters the picture. The fixes are entirely inside the translation layer, so they have no effect on a standard Windows installation.

A short history of DXVK’s critical role

DXVK began in 2017 as a one-person project by Philip Rebohle, aiming to bring Direct3D 11 games to Linux via Vulkan. It was absorbed into Valve’s Proton effort in 2018 and has since become the backbone of Linux gaming. The project moved through version 1.x and 2.x releases over the years, steadily adding support for more game-specific quirks and performance optimizations. The 3.0 series, which started earlier this year, modernized the codebase and added initial support for Direct3D 8 and 9, broadening its reach into classic titles.

Device loss has been a persistent headache the entire time. GPU drivers can crash for dozens of reasons: overheating, overclocking, driver bugs, memory corruption, or even power supply dips. When a crash happens, the driver notifies Vulkan, and the application must deal with VK_ERROR_DEVICE_LOST. DXVK, sitting between the game and Vulkan, had no way to pass useful information upward. This diagnostic gap led to bug reports that said little more than “the game froze and then quit,” which is nearly impossible to act on without local access to the failing hardware.

Version 3.0.2 is the first release to directly address that gap. The hang debug option doesn’t solve every problem—if the system hard-locks or the GPU physically resets without reporting the error, there may be nothing to log—but it covers the majority of recoverable device losses that users see in practice.

How to put DXVK 3.0.2 to work

If you’re a Proton gamer, patience is your simplest option. Check your Proton version in Steam’s compatibility settings. Proton Experimental often gets DXVK updates within a day or two. You can force an update by opting into the Proton Experimental beta or selecting it for the specific game. Keep an eye on Proton’s changelog for confirmation that 3.0.2 has been merged.

For standalone users on Windows or Linux, head to the DXVK GitHub releases page. Download the tarball for your architecture and extract the appropriate DLLs—d3d8.dll, d3d9.dll, d3d10core.dll, and d3d11.dll—into the game’s executable folder. Back up the originals first. Then, when you want to chase a crash, set the environment variable. On Windows, you can do this from a command prompt before launching the game:

set DXVK_DEBUG=hang
game.exe

On Linux, the equivalent is:

DXVK_DEBUG=hang %command%

You can also set it globally, but it’s best to use it only when troubleshooting, since the extra checkpoints could introduce a tiny performance penalty.

Once you reproduce the crash, DXVK will write a log file—typically game.exe_dxgi.log—to the game’s directory or your user folder. Attach that log to any bug report you file. Developers will appreciate the thread ID and the approximate location of the failure.

For the game-specific fixes, no extra steps are needed. If you were experiencing the described issues in Granblue Fantasy: Relink, Dying Light: The Beast, Halo: Combat Evolved, Overwatch, or Splinter Cell: Chaos Theory under DXVK, updating to 3.0.2 should resolve them. Verify by launching the game and testing the previously broken scenario.

What comes next

DXVK shows no signs of slowing. The debug tooling in 3.0.2 is likely to evolve—Rebohle has a history of iterating on feedback, and if users provide logs that reveal common crash patterns, future releases may include automatic workarounds for those cases. Valve’s Proton will continue to be the primary delivery vehicle, and given how quickly Proton Experimental adopted the previous DXVK point releases, integration should happen within the week.

For Windows users who turned to DXVK as a workaround, the hang debugger adds a compelling reason to keep it in their toolkit. Windows-native Vulkan debug layers can be finicky, and having a single environment variable that works across platforms lowers the barrier to useful bug reporting. The five game fixes, while modest, reinforce DXVK’s role as the most polished compatibility layer for running DirectX titles outside their native environment. If you rely on DXVK—whether on a Steam Deck, a Linux desktop, or a Windows gaming rig—this update is worth grabbing for the debugging power alone.