SCSKiller DXVK Async: gplasync vs Old Async Compared

Shader compilation stutter has ruined countless PC gaming sessions, and if you've searched for a fix, you've probably run across the term SCSKiller DXVK async. SCSKiller is the developer behind DXVK-gplasync, the maintained continuation of the original DXVK-async patch. This comparison breaks down how gplasync stacks up against the original async hack and vanilla DXVK, so you can pick the right tool for your setup — and know exactly what trade-offs you're accepting.

Why Shader Stutter Happens in the First Place

When a game built on DirectX 9, 10, or 11 runs through a translation layer like DXVK, every shader must be compiled into Vulkan-compatible code the first time it's needed. On a busy screen — a new area, a battle transition, a crowded city street — dozens of shaders compile at once, and the frame that's rendering simply has to wait. The result is a hitch, freeze, or multi-second hang.

Community discussions around titles like Lightning Returns: Final Fantasy XIII describe "crazy shader stutter," with freezes lasting a couple of seconds when entering new zones. The official DXVK project on GitHub remains actively maintained but deliberately excludes async compilation from the mainline build, which is why patched forks exist at all.

SCSKiller DXVK Async vs. Original Async vs. Vanilla DXVK

Here's the side-by-side comparison most players actually need:

Why the original DXVK-Async died

The original async patch worked by not waiting for shaders to finish compiling. The frame renders immediately, and anything whose shader isn't ready just doesn't draw. As maintainers on the wine-tkg-git project explained, this could produce graphical bugs — including seeing through walls while shaders compiled — which is unacceptable in competitive games. Worse, that see-through-walls behavior resembled how wallhacks function, so anticheat systems could theoretically flag it. The patch was ultimately dropped from ProtonGE builds entirely.

What SCSKiller's gplasync changes

SCSKiller's DXVK-gplasync rebuilt the concept using a GPL-based approach, keeping async compilation alive in a project that's still updated to track modern DXVK releases. Community reports from the wine-tkg issue tracker suggest it achieves the same stutter elimination while being less likely to trip anticheat software — though no third-party DLL injection method is ever fully risk-free in online games.

Real-World Results: What Players Report

The most detailed community case study comes from a Lightning Returns: Final Fantasy XIII Steam forum thread, where a player spent two weeks tuning the game and shared results:

One player noted the fix "saved my life" for a game that was otherwise nearly unplayable. Another reported stutter nearly gone, with only asset streaming hitches remaining. That said, results weren't universal: several players with RTX 4060, ROG Ally, and RTX 3070 Ti systems reported little to no improvement, and some experienced persistent texture flickering. Your mileage will genuinely vary depending on the game, GPU driver, and how the title handles its shader pipeline.

How to Set Up DXVK-gplasync

The setup process is straightforward and takes under ten minutes. The community-tested steps for Lightning Returns generalize well to other DX9–DX11 titles:

Quick troubleshooting checklist

• No HUD showing? Verify the environment variable was applied system-wide and restart the game fully.
• Textures flicker or render black? That's async working as designed — the shader wasn't ready. It usually caches after first exposure.
• Can't tolerate the artifacts? Remove dxvk.enableAsync = true from your config; you'll trade occasional black textures back for stutter.
• Nothing improved at all? The game may not benefit — remember that DirectX 12 titles don't use DXVK at all, so async patches are irrelevant there.

Known Limitations and Who Should (and Shouldn't) Use It

The fundamental trade-off of any async approach: instead of waiting for shaders, the renderer draws the frame without them. Missing shaders mean missing geometry or black textures for a split second. In single-player games this is usually a fair exchange — most players in community threads said they'd take "black textures over stutter hell any day of the week." In competitive online games, that same behavior can look like a wallhack and carries real anticheat risk.

A quick decision guide:

It's also worth remembering that shader stutter isn't always the culprit. One frustrated player blamed their "terrible" Ryzen 5600X for years of stutter, only to discover the DirectX translation layer was the bottleneck — while another tried the same fix and still got poor results, pointing to other issues like asset streaming. Diagnose before you patch.

Verdict: Is SCSKiller DXVK Async Worth It?

For single-player games plagued by shader compilation stutter, SCSKiller's DXVK-gplasync is currently the best-maintained way to get async compilation. It keeps pace with upstream DXVK releases, delivers the same dramatic stutter reduction the original async patch was famous for, and carries less anticheat concern than its discontinued predecessor. The cost is occasional missing textures or geometry — a trade most single-player players will happily make.

If you play primarily competitive online titles or DX12 games, though, this tool simply isn't for you, and forcing it into those scenarios risks more than it solves.

FAQ

What is SCSKiller DXVK async? SCSKiller DXVK async refers to DXVK-gplasync, a community-maintained fork of DXVK that adds asynchronous shader compilation. Instead of freezing frames while shaders compile, it renders them immediately, eliminating most stutter at the cost of brief visual artifacts.

Is DXVK-gplasync safe to use with anticheat software? Community reports suggest GPL-based async is less likely to trigger anticheat than the original DXVK-async, which behaved similarly to wallhacks. However, no unofficial DLL modification is guaranteed safe — avoid it in competitive multiplayer games.

What's the difference between gplasync and the original DXVK-async? The original async patch is discontinued, unmaintained, and was removed from ProtonGE due to anticheat and licensing concerns. gplasync rebuilt the feature with a GPL-compatible approach and continues tracking modern DXVK versions.

Why didn't DXVK async fix my DirectX 12 game? DXVK only translates DirectX 9, 10, and 11 to Vulkan. DirectX 12 games never touch DXVK, so async patches have no effect — stutter in those titles needs different solutions entirely.