Mortal Shell II PC Hotfix 3: FSR Map, Cosmetics and Tarstones

Published 2026-09-01 · Updated 2026-09-02

A source-scoped guide to the September 1, 2026 PC Hotfix 3 fixes for FSR map opening, Devout and pre-order Shell shades, Tarstone effects, drops, collision, and what remains unconfirmed.

Install the PC hotfix before retesting these symptoms

Checked on 2026-09-02. A public official Reddit post labels Hotfix 3 as a September 1 PC hotfix. It should be treated as a PC-only player-facing fix unless a console source names the same changes for that platform. Let Steam finish the download and verification process, restart the client, then retest the exact symptom. SteamDB or a download size can show that files changed, but the Reddit note is the source that explains the intended fixes.

FSR and map-opening behavior

The most performance-relevant item is a fix for bugs involving FSR frame generation and opening the menu map. If your PC problem was a map-open hitch, visual break, or setting conflict while using FSR frame generation, update first and retest with the same resolution, upscaler, frame-generation state, and map-opening sequence. If the problem remains, record whether it happens with FSR frame generation off as well. Do not generalize this note into a universal FPS boost or a fix for every DLSS, FSR, or XeSS issue.

Cosmetics and platform scope

The post says Devout and pre-order Shell Shades were fixed, and includes a narrow note that the PS5 entitlement issue should also be fixed for players who should have those items. It does not say Xbox received this PC hotfix or publish a complete entitlement audit. If a cosmetic is still missing, verify the platform account, edition or preorder entitlement, installed add-ons, and current platform update before reporting it. Avoid buying a second copy or deleting saves as a cosmetic workaround.

Quest, world, collision and visual fixes

Hotfix 3 names several specific repair areas: Runic Gate visual effects after save-and-quit, the Magda Stone description, a floating Styrak after auto-revive, missing statues in Eastern and Western Temple, disabled-area exploits, pause-menu sensitivity, a Dry Cruelty scythe drop in Nocteserper's Grieving Halls, multiple collision issues, and Minibeacon visual problems. These are official fix candidates to retest, not permission to invent exact routes, drop rates, or statue counts that the note does not publish.

Tarstones need source-safe wording

The same post says errors where Tarstones did not match their effects were fixed, and damaged Tarstone drop rates were adjusted. It does not publish exact new values or a full loot table. If a build guide depends on a specific Tarstone effect, compare the current in-game description and one controlled test before updating rankings. If a farming route seems better or worse after the hotfix, record the platform, patch, location, enemies, sample size, and previous source before turning it into advice.

Unresolved reports to keep separate

Steam community discussion after the update includes players asking about patch notes, download size, freezes, and frame-generation behavior. Those comments are useful leads, but the public evidence checked today does not confirm a new universal crash, a solved download problem, or a remaining FSR regression across multiple independent setups. Keep those as watchlist items until an official reply, reproducible multi-player evidence, or a later patch note narrows the symptom.

Player action checklist

For PC, update through Steam, restart the game, and retest only the affected symptom. For FSR/map problems, test the same map open with FSR frame generation on and off. For missing cosmetics, verify the entitlement and installed content before filing a report. For Tarstone behavior, trust current in-game text over older guide tables and avoid breaking rare items just to test a rumor. For console players, follow the Week 1 platform rollout note and platform update history rather than applying this PC hotfix label to your build.

Sources

Checked on 2026-09-02.