Mortal Shell 2 launched into the familiar Unreal Engine 5 launch-window chaos: shader compilation freezes, D3D12 GPU faults, a crash on the Continue button. I've kept a crash tracker since those first weeks: every entry is a verified symptom, the real error string where present, a fix, and a status tag tied to a build. As of build 1.000.015 (last verified November 6), it holds 54 issues: 22 fixed by patches, 13 with workarounds only, 10 pending, plus a few acknowledged, investigating, partial, or unverified.
This is the October report: which crashes died, which survived, and what the notes teach about debugging a live game.
The tracker behind this post
A word on method, because it separates this from fix-guide sprawl. Each entry carries one of six statuses — fixed, workaround, pending, acknowledged, investigating, partial — and a version stamp for where that status was last verified. Sources are tiered: developer-published patch notes first, developer Steam replies next, then community reports cross-checked across independent threads. Nothing gets marked fixed on a single forum post; workarounds are labeled reporter-verified or unconfirmed. The full Mortal Shell 2 crashing fixes tracker covers all 54 entries under that same discipline.
What October actually fixed
September 24 — Hotfix 1.000.011. The densest stability release of the fall: dungeons refusing to load when using Egon's Stone, players falling through elevator lifts, and trophy fixes for "Seeking the Past" and "Bring My Ova Back to Me". Ten tracker entries flipped to fixed in a single release — the biggest movement in the game's dozen tracked updates.
October 14 — Hotfix 1.000.012. Four more entries closed: Slayer Seal and Punch issues, a soft lock backing out of Mether's Breath's second warning, Genessa Clones stuck with the Obsidian Hammer, and blocked Gragu possession.
October 16 — PS5 Hotfix 1.000.013. Two named console fixes: stuttering (around death and pick-ups) and a soft lock when interacting with the collector. Announced by the developer on Reddit rather than a Steam news post — monitor Steam only and you'd have missed it.
October 23 — Rotten Autumn Hotfix 1 (build 1.000.015), notes published October 30. The Rotten Autumn content update (1.000.014) landed October 20 — Photo Mode, and a dungeon pool that jumped from 36 to 51 — with the hotfix following three days later at roughly 800MB on PC. The notes arrived a week after the build. For crash triage, the money line sits in Stability & Performance: "Several crash fixes and stability improvements (including Zmey and dungeon crashes)" — the first patch-note line to name Zmey crashes directly — plus smoother dungeon transitions: "background checkpoint saves, less hitching and better memory handling". The same notes also fixed the Orrem elevator-floor form, the Proxima invincibility exploit (tracker entry #46 flipped to fixed), and night mode triggering inside the hub.
The crashes that survived October
The Continue-button crash is still open. Three independent players have reported it since late August on different hardware: the game consistently crashes on first load while continuing an existing save. The developer acknowledged the crash cluster on August 26 — "We are aware of these crashing issues and are looking into a solution" — but this specific form hasn't been named in any notes since. Two reporter-verified workarounds: set a 30 FPS lock in settings before pressing Continue, or load a fresh save slot first, then your real one — both re-applied after every restart.
The night-mode merchant bug is the newest open wound. After the October 14 hotfix, talking to The Collector during night mode can make the merchant UI vanish and lock input. The developer confirmed on October 15 the team is investigating — a regression from a stability hotfix, unresolved as of 1.000.015.
Also pending: achievements that never pop (shell-unlock ones, while the unlock-all-shells achievement does trigger), trials spawning no enemies (reloading is player-reported, unconfirmed), the Smert invincibility from kick-spamming during Last Vow, the Ritual Grounds chest stuck locked, and Mether's Pulse upgrades doing nothing to flask healing.
The triage order that still works
Phase 1, thirty seconds each: confirm you're on the Week 1 Update (1.000.008) or newer, verify file integrity in Steam, disable Frame Generation and Ray Tracing, set NVIDIA Shader Cache Size to Unlimited, and switch FSR to TSR. Phase 2, two minutes each: a clean GPU driver reinstall with DDU from Safe Mode, deleting corrupted input save files (the keybind-menu crash), Borderless to Fullscreen, and the preset dropped to High with a 60 FPS cap. Phase 3, five minutes each: clear shader caches, set a static page file at 16/32 GB, try the community Ultimate Engine Tweaks mod, and push textures to High for the out-of-video-memory form. Stop when the crash stops — stacking Phase 3 fixes on a Phase 1 success only pollutes your next debugging session.
The do-not-do list: -UseFixedTimeStep (a Unity-era flag that migrated into UE5 guides through copy-paste drift), globally disabling Control Flow Guard (a security feature, with documented stability trade-offs), and trusting any "confirmed memory leak" claim that names neither build nor error signature.
A quick word on Steam Deck
Deck players get a split answer: Playable on Valve's compatibility scale, running under proton-11.0-2RC with no forced compatibility tool, at a combat-locked ~30 FPS playable without changes. The annoyance: the graphics menu is locked on Deck by default, with global illumination stuck on Low. The closest thing to a documented Mortal Shell 2 Steam Deck fix for that lock is a launch-option bypass — add SteamDeck=0 %command% to unlock the full menu, where TSR beats the default upscaler on the Deck's panel. The crash side is Proton-specific: users report D3D12 GPU crashes under Proton, plus a separate Valve-tracked AMD graphics-queue timeout whose suggested first step is a single-queue launch option. Don't reach for -dx11 on Linux — it trades crashes for visible rendering glitches.
What reading patch notes like a debugger teaches
Notes lag builds. Build 1.000.015 shipped October 23; its notes arrived October 30. Date every fact to the build, not the announcement.
Named fixes don't name forms. "Including Zmey and dungeon crashes" names the target, not the symptom — keep workarounds up until a form is confirmed dead in the wild; note lines are covering claims, not confirmations.
Patches breed regressions. The merchant UI bug arrived with a stability hotfix. Re-test save/load, fast travel and merchants after every patch.
High-end hardware isn't safe. The tracker's most persistent crash forms draw reports from top-spec machines as often as budget ones. Minimum specs predict whether a game runs, not whether it's stable.
This tracker is a fan-run project and is not affiliated with Cold Symmetry. Every status cites its source tier, with the build and date verified on the tracker page.
Top comments (0)