Wuthering Waves on PS5: crashes, performance, and what 3.6 actually changed for consoles
By DayOneFix Editorial · August 20, 2026
The short version: 3.6’s headline performance work is for PC, not PS5. The update’s engine upgrade centres on DLSS 4.5 and higher frame-rate targets — PC technologies — and the official 3.6 update content notice makes no console-specific performance commitments. We read it looking for one. PS5 players noticed the same thing, loudly, on launch day.
Why does my PS5 turn off completely while playing Wuthering Waves?
A full shut-off with no warning is the PS5’s thermal protection tripping — not the game. It cuts power like a breaker rather than showing an overheat message first, which matches Sony’s documented behaviour. A detailed player report from this week describes the pattern exactly: crashes after ~10 minutes regardless of activity, and the console powers off entirely — and the community diagnosis in that thread landed on thermal protection for precisely this reason.
What that player had already tried, none of which fixed it — worth knowing so you skip the same dead ends:
- Uninstalling and reinstalling the game
- Clearing the cache
- Rebuilding the database
The fix that community consensus points to for the shut-off pattern is physical: dust the vents and intakes (compressed air), ensure airflow around the console. A game cannot survive a console-level power cut, so reinstall loops will not help.
How do I fix Wuthering Waves crashing on PS5?
If the game closes but the console stays on, start by letting the 3.6 patch fully finish — including the additional in-game download — then work through standard PS5 software steps. The usual order after a version update:
- Let the patch fully finish — 3.6 also runs an additional in-game download after the launcher/store update; an interrupted one causes instability.
- Standard PS5 hygiene: close other applications, then clear the cache and rebuild the database — the right tools for software crashes even though they cannot fix thermal ones.
- If it started exactly with 3.6 and survives all of the above, report it with your region and repro steps — and check whether it is widespread before assuming your install is broken.
The optimization complaints are older than 3.6
“PS5 version has always been badly optimized” is a long-running community sentiment — map lag and performance-mode grumbles predate this version. That is context, not a verdict: we have not measured PS5 frame delivery ourselves, so we report the sentiment as sentiment. What is verifiable is the other half: console-specific performance work was not part of 3.6’s announced scope, and if Kuro announces a console performance patch, this page gets it the same day.
FAQ
Did the 3.6 update improve performance on PS5? No. The 3.6 engine upgrade centres on DLSS 4.5 and higher frame-rate targets — PC technologies — and the official 3.6 update content notice makes no console-specific performance commitments. If Kuro announces a console performance patch, this page gets it the same day.
Does reinstalling Wuthering Waves fix the PS5 shutting off? No. The player report that defined this pattern had already tried reinstalling, clearing the cache, and rebuilding the database — none of it helped, because a game cannot survive a console-level power cut. The community-consensus fix is physical: dust the vents and intakes and ensure airflow.
Has the PS5 version always run badly? “PS5 version has always been badly optimized” is a long-running community sentiment — map lag and performance-mode complaints predate 3.6. We have not measured PS5 frame delivery ourselves, so we report that as sentiment, not a verdict.
Related
- The 3.6 engine upgrade, for PC — what it fixes
- Server status and patch-day checks
- 3.6 codes tracker
- 3.6 banners — both phases, confirmed
Sources
The PC-facing scope of the 3.6 engine upgrade is from Kuro’s official 3.6 materials as documented on our performance page; the absence of console commitments was checked against the official 3.6 update content notice of 18 August. The shut-off report and its tried-and-failed steps are from a detailed player thread of 19–20 August (r/WutheringWaves), with the thermal-breaker diagnosis being that thread’s community consensus — consistent with Sony’s documented PS5 thermal behaviour. Optimization sentiment labelled as community sentiment. Checked 20 August 2026, version 3.6 launch day.