The Sinking City 2 Reinvents Survival Horror With Linear Frogwares Gameplay

The Sinking City 2 is the kind of sequel that trades one identity for another—and largely pulls it off. Frogwares’ follow-up shifts away from the open-world investigation structure that defined its predecessor and rebrands itself as a classic, linear survival horror experience built around confined exploration, limited inventory, counted ammunition, and backtracking that rewards careful, patient play. The Lovecraftian setting is meticulously crafted, the audiovisual presentation is strong, and the story lands as a self-contained adventure focused on love as much as cosmic dread. The combat, however, is the most noticeable weak point, and a few enemy-wave sections and tight resources can undercut the pacing.

Key takeaways

• The sequel changes course from the original’s open-world detective style to a more classic, linear survival horror structure.
• Players explore enclosed areas with puzzle-like room layouts, shortcuts, limited inventory, scarce ammunition, and deliberate backtracking.
• Developed in Ukraine over more than three years during wartime, with production repeatedly interrupted by outages, bombings, mobilizations, and destroyed homes.
• The game is built on Unreal Engine 5 and generally runs well on an RTX 3070, though some players report stutters when transitioning between zones.
• Its combat is described as unreliable—especially melee—while certain hospital and market segments rely on repetitive enemy waves and ammo-box waits.

A bold reinvention into classic survival horror

The Sinking City 2 no longer plays like the 2019 entry. Instead of an open-world investigation adventure with downtime and detective pacing, it leans into straight survival horror fundamentals: tightly structured progression, rooms that function like puzzle chambers, frequent shortcut unlocking, and a constant pressure to conserve bullets. The result is a game that feels at home for fans of modern survival horror remakes and returns—systems and pacing shaped around tension, not investigation wandering.

That shift is presented as a decisive improvement to the overall experience. While some players who loved the first game’s detective framing may miss the investigative identity, the sequel’s design emphasizes survival pressure and rhythm over board-like case solving. The project’s focus is less about studying clues and more about enduring spaces that repeatedly ask you to plan, remember routes, and manage what you can carry.

Lovecraftian atmosphere, level design, and an audio-first horror mood

Where the sequel particularly shines is atmosphere. Arkham is portrayed as flooded and decayed throughout the “20s” era—submerged streets, rotting interiors, a muted palette, and the persistent sense that nothing is safe. The visual presentation is credited to strong work per location, and the game’s look is described as excellent on Unreal Engine 5. Performance is reported as generally solid on PC with an RTX 3070, with the caveat that some players have mentioned occasional stutters during zone transitions.

Level design supports the tone. Each area is described as a labyrinth that encourages returning through earlier routes, learning where you’ve been, and celebrating the shortcuts that connect back to save rooms. Sound is highlighted as a “final touch” that locks in the dread: water movement, creature sounds, and an oppressive ambience that stays with you.

There’s also a localization note: the game is not dubbed into Spanish and features English voices only, but it includes Spanish text and subtitles that make following the story straightforward.

A complete, stand-alone story centered on Calvin and Faye

The Sinking City 2 tells a story that stands on its own. You play as Calvin Rafferty, an occult investigator who enters a condemned version of Arkham to rescue his partner, Faye Bennett. Faye is trapped in a supernatural coma after a ritual goes wrong. The game is positioned as accessible even if you haven’t played the first entry, since it is designed to function as an independent adventure.

The script’s emotional core is described as a sincere love story underneath the cosmic horror. The relationship between Calvin and Faye is framed as the true heart of the adventure—presented not as filler romance, but as the driving force that pushes Calvin deeper into the nightmare. The narrative is also praised for its handling and for providing a satisfying conclusion, a quality that doesn’t always show up in Lovecraft-inspired terror.

The combat and resource strain that hold it back

Despite its many strengths, The Sinking City 2 has a clear weak point: combat. It’s described as the least polished part of the experience, not because of challenge alone but due to poor reliability in execution. Melee is said to feel stiff and fail when it matters, leading to hits that were expected to be avoidable. Enemy grabs are also criticized as unfair and difficult to anticipate, with encounters worsening when ammunition is already scarce.

Some sections are singled out for breaking the careful survival rhythm. In places such as the hospital and the market, exploration is reduced and the game leans into arenas where you must endure repeated waves of enemies that keep coming while you wait for ammunition to refill. These moments are described as undermining the tension the rest of the campaign builds, turning survival into a more mechanical exercise.

Resource management is another pressure point. While the genre’s scarcity philosophy is understood, the inventory constraints are described as consistently stressful—forcing constant juggling of limited space and highlighting an imbalance. The first half is characterized as particularly tight on supplies, with later parts easing up. Puzzles, in contrast, are treated as a stronger element overall, ranging from simpler to more elaborate offerings, though none are said to fully stall progress.

Made through wartime hardship—real signals and real stories inside the game

One of the most striking contextual details is how the game came to exist at all. Frogwares is an Ukrainian studio, and development reportedly lasted more than three years during active war. Work was repeatedly halted by the conflict: blackouts that lasted weeks, interrupted days due to bombings, team members mobilized to the front, and homes destroyed. The project’s existence is described as a near miracle—and that background changes how the final product is viewed.

That reality is also said to appear directly in the game. Some in-game sirens are described as real recordings of air-raid alarms heard daily in Ukraine. In a hospital area connected to prosthetics, the game reportedly includes x-rays and real stories tied to war victims—an experience presented as emotionally jarring once you understand what you’re looking at. The message is clear: these aren’t cosmetic additions or marketing beats, but lived experiences integrated into the work.

Because of that, the game’s flaws—especially the combat—are framed with added perspective. When the sequel stumbles, it’s not treated as purely a technical shortcoming; it’s also seen against the larger story of perseverance behind the development itself.