The Sinking City 2 Launch State: Early Impressions, Hotfix 1.0.1, and Known Tech Issues

The release of The Sinking City 2 marks the culmination of a profoundly turbulent three-year development cycle for Frogwares. Shifting away from the predominantly detective-focused gameplay of the 2019 original, the sequel plunges players directly into a grueling, pure survival horror experience powered by Unreal Engine 5. Now that the game is officially in the hands of players across PC, PlayStation 5, and Xbox Series X|S, we are beginning to see a clear picture of what exploring drowned Arkham actually entails.

From widespread praise regarding its genuinely terrifying atmosphere to a handful of community-reported technical hurdles, the first 24 hours of launch have been eventful. Frogwares has already deployed Hotfix 1.0.1 to address critical bugs, but players navigating the flooded streets still need to be aware of a few lingering issues. Here is a comprehensive breakdown of the early player verdicts, the latest patch notes, and the technical quirks currently affecting specific hardware setups.

A Genuinely Terrifying Shift to Survival Horror

When Frogwares announced that The Sinking City 2 would pivot strictly into survival horror territory, veteran players of the original game were both intrigued and cautious. The 2019 title, set in Oakmont, was highly praised for its intricate investigation board and weird fiction ambiance, but it wasn’t necessarily designed to induce raw, visceral fear. The sequel changes that equation entirely.

According to early impressions flooding in from the horror gaming community, the atmosphere in drowned Arkham is suffocating. Players who have reached the early restricted section of the library note that the game demands an entirely different mindset. Resource scarcity is immediate, and the combat requires methodical spacing and careful aim rather than the more forgiving action of its predecessor. Many are comparing the relentless tension to recent genre heavyweights like the Silent Hill 2 remake and Alan Wake 2. If you are just starting your journey, brushing up on your survival basics is highly recommended, as treating this like a standard action shooter will rapidly lead to a sanity-draining death.

One of the most frequently praised aspects of the early game is the audio design. Players have specifically highlighted the deeply unsettling soundscapes, particularly the slithering, wet noises emanating from piles of worms and other unseen eldritch horrors lurking just beyond the flashlight’s beam. Encounters with creatures like the Slither are reportedly nerve-wracking, heavily emphasizing the game’s core philosophy that fleeing is often a better strategy than fighting.

Hotfix 1.0.1: Immediate Crash and Puzzle Fixes

Recognizing a few progression-blocking bugs that slipped through to the launch build, Frogwares acted swiftly, pushing out Hotfix 1.0.1 within the first day. This update is relatively small in file size but crucial for those progressing through the mid-game narrative chapters.

The official patch notes highlight fixes for specific, rare crashes that were interrupting key moments. Players engaging in the “A New Day” sequence should no longer experience sudden desktop crashes. Furthermore, a frustrating crash that reportedly triggered immediately following the arena fight in the “Cold Comfort” section has been resolved, ensuring that players don’t lose their hard-earned progress after a grueling combat scenario.

Beyond stability, the hotfix also addresses mechanical bugs tied to the game’s intricate puzzles. In the “A Sight for Sore Eyes” mission, an issue where the Prism could completely disappear from the inventory during the puzzle validation process has been patched. Additionally, a visual logic bug during the same chapter’s brain puzzle—where the third lamp would inexplicably fail to light up even when the correct solution was entered—has been corrected. The developers also noted that several instances of missing textures across various environments have been restored, polishing the grim visuals of the Unreal Engine 5 environment.

Known Technical Hurdles and Hardware Reports

While the game is generally receiving positive feedback for its visual fidelity and oppressive art direction, running a dense, water-logged Unreal Engine 5 environment does come with a heavy performance cost. Several community-reported issues are currently circulating, particularly affecting players on mid-to-lower-end hardware and Linux-based systems.

GPU Instability on Mid-Range AMD Cards

Multiple players utilizing the AMD Radeon RX 6600 and similar tier GPUs have reported severe system instability. Reports indicate that the game runs at an acceptable framerate (hovering around 45 FPS on optimized settings), but is prone to random, hard freezes that completely lock up the PC, sometimes forcing an automatic system reboot. Monitoring tools during these crashes show high GPU and VRAM utilization, suggesting memory leaks or aggressive engine spikes. If you are operating on hardware that sits close to the minimum system requirements, it is highly advised to lower texture pools, disable ray-traced reflections, and ensure your graphics drivers are fully updated while awaiting further optimization patches from Frogwares.

Steam OS, Bazzite, and Streaming Conflicts

The handheld and Linux gaming communities are facing their own unique set of challenges. Players attempting to run The Sinking City 2 natively on Bazzite OS and standard Steam OS builds are currently experiencing a hard crash immediately after selecting their difficulty setting on a new game. This appears to be a proton compatibility issue with the game’s initial rendering pipeline or video playback, and no definitive workaround has been found yet for native Linux execution.

Furthermore, players attempting to stream the game from a powerful PC to their Steam Deck via Moonlight are encountering severe input flickering. Pressing a button on the Steam Deck causes the in-game UI to frantically swap between PC keyboard prompts and Xbox controller prompts. This mapping conflict extends to the camera controls, where manipulating the analog stick causes the invisible mouse cursor to fight for priority, resulting in a jittery, unplayable camera. Until a patch is issued, players using Moonlight might need to manually disable keyboard and mouse input on the host PC via device manager before launching the stream.

Cloud Gaming Quirks

For those utilizing Boosteroid to bypass the hefty hardware requirements, The Sinking City 2 was impressively available on launch day. However, cloud players have noted two distinct annoyances: a surprisingly lengthy shader compilation process upon every initial boot, and a persistent “Activate Windows” watermark appearing in the lower corner of the cloud stream, an amusing server-side oversight that only seems to affect this specific title on the platform.

A Heartfelt Note in the Credits

Beyond the terror and the technical troubleshooting, players who have already rushed to the end of the game are highlighting a deeply emotional Easter egg tucked into the credits. The final scroll is accompanied by a beautifully arranged, Ukrainian-language rendition of the classic Irish folk song, “Raglan Road.”

Given the harrowing real-world circumstances surrounding Frogwares—a studio based in Kyiv that developed this entire game amid an ongoing war—this musical choice has struck a powerful chord with the community. Players have noted that hearing a song of sorrow and longing, translated into the developers’ native tongue, adds a poignant layer of reality to a game steeped in cosmic dread. It serves as a stark reminder of the resilience required to deliver this ambitious survival horror experience against all odds.

As the launch week progresses, we expect further stability patches from Frogwares. For now, keep your lantern fueled, manage your ammunition wisely, and tread carefully through the submerged ruins of Arkham.