The Sinking City 2 Patch Notes — PC 1.0.2 vs Console 1.0.1

WHAT CHANGED

Match the platform and symptom before applying a fix—PC Hotfix 1.0.2, console Patch 1.0.1, and current known-issue workarounds solve different problems.

The Sinking City 2 has different current patch lines by platform: PC is on Hotfix 1.0.2 after Hotfix 1.0.1, while PlayStation 5 and Xbox Series X|S have console Patch 1.0.1. The matching “1.0.1” labels do not mean that the PC hotfix and console patch have identical contents.

Start with the symptom table below. A patch note proves that a named bug was fixed; it does not prove that every similar-looking problem has the same cause.

Symptom-to-action map

1. 01Choose platformDo not start from the symptom alone
2. 02PCSteam / GOG / Epic → current record 1.0.2
3. 03ConsolePS5 / Xbox Series → current record 1.0.1
4. 04Use PC fix listThen follow the named workaround
5. 05Use console fix listDo not project a PC fix onto console

Choose platform→PCPCChoose platform→consoleConsolePC→Use PC fix listConsole→Use console fix list

Read the route as text

1. Choose platformDo not start from the symptom alone
2. PCSteam / GOG / Epic → current record 1.0.2
3. ConsolePS5 / Xbox Series → current record 1.0.1
4. Use PC fix listThen follow the named workaround
5. Use console fix listDo not project a PC fix onto console

PC: Hotfix 1.0.1, then Hotfix 1.0.2

PC Hotfix 1.0.1 fixed rare crashes in “A New Day” and after the “Cold Comfort” arena, a removable Prism during puzzle validation, the third brain-puzzle lamp, and missing textures. Hotfix 1.0.2 followed on Steam, GOG, and Epic with an outdated-driver warning, PSO-hitch improvements, and a rare navigation-mesh crash fix.

PS5 and Xbox Series: Patch 1.0.1

Console Patch 1.0.1 adds general performance and optimization work plus stability, gameplay, and visual fixes. Examples include the shotgun reload loop, interrupted levers becoming unusable, missed subtitles, several mission crashes, achievement progress after console save transfer, and puzzle or traversal blockers. Xbox-specific fixes reduce low-health ghosting and improve shadows in dark areas.

PC known issues and workarounds

The current official known-issues list still includes:

• visual glitches after changing presets or individual settings during gameplay;
• artifacts on the Low preset, especially when used outside necessity;
• instability, ghosting, or artifacts in DLSS Performance and Ultra Performance;
• hardware-dependent level-of-detail issues;
• temporary Night Shade mask twitching after cutscenes or QTEs;
• a lingering Acheronian Juggernaut shadow;
• Slither Pawns falling through the floor.

For settings-related glitches, Frogwares recommends making changes from the title screen. If the issue appears after a midgame change, restart the game or reload the save. For DLSS, the official note recommends Balanced or a higher-quality mode instead of Performance or Ultra Performance.

These known-issue steps apply to the current PC build. They do not prove that the same symptom on PS5 or Xbox has the same cause. Console players should first confirm Patch 1.0.1 is installed and use Frogwares Support for symptoms not named in its console notes. For expected PC hardware targets, use The Sinking City 2 system requirements.

PC crash recovery and the support packet

Frogwares' official order is: verify the installed files, launch once with -clearPSODriverCache, reinstall and reboot if needed, then perform a clean graphics-driver update. Stop when the crash no longer reproduces; changing several variables at once makes the cause harder to identify.

If the crash remains, prepare the evidence Frogwares explicitly requests before opening a ticket:

1. dxdiag.txt;
2. a screenshot or video of the crash error;
3. an archived copy of %LOCALAPPDATA%\TSC2;

We additionally recommend writing down the platform/store, current patch, mission or room, and the last repeatable action before the crash. Those fields are editorial additions, not items claimed as mandatory by the cited Frogwares crash article; they make the report easier to reproduce.

For a non-crash bug, the official report guide still asks for as much detail as possible and specifically calls out dxdiag.txt and a screenshot. Preserve the original save folder before experimenting with files.

Return to The Sinking City 2 overview for the release status, platforms, media, and the complete answer library.

Sources & evidenceOpen the references used for this page

• Frogwares Support: PC Hotfix 1.0.1
• Frogwares Support: Hotfix 1.0.2
• Frogwares Support: console Patch 1.0.1
• Frogwares Support: current known issues
• Frogwares Support: ordered PC crash recovery and diagnostic files
• Frogwares Support: how to report a bug
• Frogwares Support: performance troubleshooting
• Frogwares Support: Frame Generation on a 60 Hz monitor
• The Sinking City 2 on Steam