Mortal Shell II known issues: what's broken, what's acknowledged, what to do meanwhile
By DayOneFix Editorial · August 21, 2026
| Issue | Status | What we know / workaround | Source |
|---|---|---|---|
| Crashes that began with the launch-day patch | Acknowledged | Multiple players report stable Advance Access play until the first update, then constant crashing. A developer replied in the official bug forum apologising and collecting repro details — acknowledged, not yet fixed. | Steam bug-report forum, incl. developer reply (20–21 Aug) |
| Intro crash at the torch / broken wall cutscene | Open | Independent reports pin the same spot: right after grabbing the torch near the intro boss, crash to desktop within seconds — 'crashes every time' for affected players. | Multiple Steam reports, same location (20–21 Aug) |
| Crash when cleansing a beacon | Open | Reported with error-report numbers submitted to the developer; not location-consistent like the intro crash but recurring. | Steam bug-report forum (20–21 Aug) |
| Frame Generation crashes (carried over from Advance Access) | Open | Reported through two Advance Access hotfixes without resolution. Workaround: turn Frame Generation off and retest before anything else. | Advance Access player reports (17–19 Aug) |
| "Pure virtual function" error crash | Open | Engine-level error message on crash; no consistent trigger identified by reporters. | Advance Access player reports (17–19 Aug) |
| Lazlo's Detonation Shell skill crash | Open | One player reproduced it seven times in a row on skill use during Advance Access. Workaround until patched: avoid the skill. | Advance Access player report (19 Aug) |
| Shell lock-out bug | Open | Reported on the launch-day Reddit bug megathread; players locked out of shells they should have access to. | r/MortalShell launch bug megathread (21 Aug) |
How this table works: every row is a problem we could source to player reports or the developer’s own posts — the light goes green only when a fix actually ships, not when one is promised. Same rule as our homepage status board.
The launch itself is going well — “Very Positive” at ~80% with nearly 24,000 concurrent players on the first full morning. The issues below are the friction inside that success, and one of them has a developer response already.
The one with an official response
The post-patch crash wave is the row that matters most: multiple players were stable through Advance Access and started crashing constantly after the first update. A developer replied in the Steam bug forum — apologising and asking for repro details (trigger, location, error pop-ups). That moves it to Acknowledged: the studio knows, a fix has not shipped yet. If you are in this group, submitting your crash pattern in that thread is genuinely useful.
The practical bits
- Crashing since the update, generally? Verify files, then check whether disabling Frame Generation stabilises you — the FG crash pattern survived two Advance Access hotfixes and looks alive in the launch build.
- Intro torch crash: no workaround confirmed yet; some players report passing the cutscene after multiple retries. If you crash there, you are not alone and it is not your install.
- Lazlo’s Detonation Shell: avoid the skill until patched if it crashes you.
- A full console shut-off (PS5 powering down) is a different animal — that is thermal protection, not the game; see the pattern we documented for WuWa this week.
Related
Sources
Every row’s source is named in the table: Steam bug-report forum threads of 20–21 August (including the developer reply), Advance Access reports of 17–19 August, and the launch-day r/MortalShell bug megathread. Review score and player count from Steam at our 21 August morning check. Statuses change only on evidence, and the last-checked stamp above is written by the data file itself.