Wuthering Waves crashing since the 3.6 engine upgrade — Frame Generation and DX12 first
By DayOneFix Editorial · August 11, 2026
If Wuthering Waves started crashing on you after 3.6, try these two things before anything else: turn Frame Generation off, and switch from DX12 to DX11. Both are toggles 3.6 itself introduced or leaned on, and both have day-one crash reports attached. The details and the reasoning are below.
3.6 replaced the engine’s underlying programming layer — the riskiest class of update a live game ships — so the failure modes people are hitting are the new foundation’s, not the old client’s. If your problem is a PS5 powering itself off, that is a different fault with a different fix: see WuWa on PS5, which also covers what 3.6 did and did not change for consoles.
What Kuro announced
- The engine’s underlying programming layer was replaced. The official program quotes an average gain of ~10 FPS across all platforms — explicitly including low-end phones, which is where the claim matters most.
- DLSS 4.5 on PC, with visibly reduced frame-generation artifacts compared to the current implementation.
- Echo management rework: full stat preview before equipping, and one-click multi-cost loadouts — the single most requested QoL item in the game’s history.
- Smaller strokes: mailbox cap raised to 200, one-click sharing for pulls and challenge results.
Why “replaced the programming layer” is a bold move
Swapping an engine’s underlying layer mid-life is the riskiest class of update a live game can ship — the upside is real (a flat FPS gain with no visual downgrade), and the failure mode is equally real: device-specific crashes, shader recompilation stutter on first boot, and regressions on exactly the low-end hardware the change is meant to help. A 42-day version built on a new foundation will tell us quickly which way it went.
What we said we would check, and where it stands
Before launch this page listed four things to verify. Being straight about which ones we actually closed:
| What we said we would check | Where it stands |
|---|---|
| Does the ~10 FPS average hold on low-end Android? | Not measured by us. We do not have a low-end Android test bench, and we are not going to launder other people’s numbers as ours. |
| First-boot shader stutter after the update | Not measured by us, and no widespread report surfaced either. |
| Are DLSS 4.5 frame-generation artifacts actually reduced? | Overtaken by events — what surfaced was not artifacting but Frame Generation crashing, which is the section above. |
| Any device models that regress | Partly answered: the pattern that emerged was GPU-specific DX12 failures rather than device-model regressions. Also above. |
3.6 went live 20 August 2026 at the usual ~11:00 (UTC+8) window (countdown).
The two crash causes, in the order to try them
The widespread 3.6 crash reports are about the upgrade’s own new toggles, not the old client. Community-sourced, labelled as such:
- Frame Generation → crashing for some setups. Multiple day-one reports of crashes that start exactly when FG is enabled — the same failure pattern Mortal Shell II players reported with FG during Advance Access on 17–19 August 2026. If your 3.6 crashes began after touching the new graphics settings: turn Frame Generation off first and retest before anything else.
- DX12 mode →
DXGI_ERROR_DEVICE_HUNGon some GPUs (reported on an RTX 5070 Ti among others), with DX11 stable on the same machines. The workaround that works today is the honest one: run DX11 until a patch addresses it. DXGI device-hung errors are driver/engine interaction failures — reinstalling the game does not touch them; a clean GPU driver install sometimes does. - Neither issue has an official Kuro acknowledgement yet as of this check; if one lands, it replaces this community framing.
Sources
Official 3.6 special program via multiple independent Chinese roundups. Performance claims are quoted as claims and were never independently measured here — the table above says so line by line rather than leaving the promise open. The Frame Generation and DX12 crash patterns are community reports from 3.6 launch day, labelled as community reports; no official Kuro acknowledgement had been posted as of the last check.