Saros patch 1.004.002 is small on paper, but it fixes the kind of bugs that ruin runs

Here’s the blunt version: Saros didn’t need a flashy roadmap update this week. It needed the boring patch that stops good runs from dying to nonsense. Update 1.004.002, released May 13, does exactly that. On paper, this is a tiny post-launch cleanup patch. In practice, it hits a cluster of problems that matter far more than new cosmetics or some token “community requested” toggle: boss phase-transition bugs, trophy unlock issues, healing behavior outside intended zones, clipping problems, one progression blocker, a rare crash, and PS5 HDR tuning that apparently wasn’t quite right at launch.

That may not sound glamorous, but if you’ve been playing Saros, you already know this is the stuff that decides whether a run feels hard in the right way or hard because the game briefly forgot its own rules. And for a Housemarque game, that distinction matters more than usual.

This is not a balance patch, and that’s the point

The most important thing about update 1.004.002 is what it does not do. It doesn’t rebalance weapons. It doesn’t rework encounters. It doesn’t mess with progression. Housemarque is not admitting that Saros launched with foundational design problems. It’s cleaning up edge-case failures in a game that was already broadly well regarded for feel, movement, and presentation.

That lines up with the broader read on Saros since launch. The game has generally been seen as a polished refinement of Housemarque’s third-person bullet-hell formula, with a more approachable progression structure than Returnal. The studio didn’t release a broken mess and then scramble into emergency surgery. What happened instead is more familiar, and honestly more annoying in a different way: players found the rare bugs that don’t show up in a clean review run but absolutely show up after thousands of real-world hours across the player base.

That’s the story here. This patch is Housemarque doing maintenance on trust. If a boss phase transition misfires, or a trophy pops at the wrong time, or an enemy heals where it shouldn’t, the player stops blaming themselves and starts blaming the game. In a precision-heavy action roguelite, that’s poison.

The boss fixes matter more than any bullet point in the notes

The headline fix is aimed at “rare issues with phase transition” in the Shepherd and Priestess fights. That wording matters. It suggests Housemarque is not changing how those bosses are designed; it’s fixing the scripted handoff between encounter states. In other words, the problem wasn’t “this boss is unfair.” The problem was “this boss sometimes failed to behave like a boss fight is supposed to behave.”

That sounds technical, but every action game player understands the difference immediately. A brutal phase change is fine if it’s readable and reliable. A broken one is rage-fuel. And because Saros lives or dies on rhythm, spacing, and pattern recognition, even a rare transition bug can sour the entire encounter. You’re not learning. You’re debugging.

The same logic applies to other gameplay fixes in the patch. Enemies healing outside intended areas might read like a minor line item, but it points to encounter logic leaking outside its boundaries. Clipping through elevators is another classic “small until it happens to you” problem. So is the fix for the Ancient Depths failing to appear after defeating the Prophet, which is exactly the kind of progression bug that turns a demanding run-based game into a support-ticket simulator.

If there’s an uncomfortable observation here, it’s this: these are the kinds of bugs players are weirdly willing to tolerate in sprawling open-world games, but not in a Housemarque game. Fair or not, the studio has trained its audience to expect mechanical cleanliness. When your reputation is built on responsiveness and clarity, a busted state transition lands harder than it would almost anywhere else.

Trophy bugs are never “just trophies” when your game is built around mastery

Housemarque also fixed the “Vincible” and “Untouchable” trophies unlocking at the wrong time. That’s important for a simple reason: trophy problems in a game like Saros aren’t cosmetic bookkeeping. They mess with the game’s feedback loop.

These trophies are tied to performance. If they unlock early, late, or inconsistently, they stop serving as confirmation that the game correctly understood what the player achieved. For Platinum hunters, that’s maddening. For everyone else, it still matters because it introduces doubt into the stat-tracking and trigger logic underneath the hood.

And no, this patch doesn’t appear to change trophy requirements. It fixes the timing and unlock behavior. That’s a meaningful distinction. The issue wasn’t that Housemarque decided the achievements were too strict or too generous. The issue was that the game was occasionally misreading when players had actually earned them.

Again, this is why the patch matters more than its size suggests. Trophy bugs are often treated like side content problems. In a run-based action game obsessed with execution, they’re evidence that the game’s rule-tracking may have been less airtight than it needed to be. Fixing that is less about PlayStation profile vanity and more about restoring confidence that the machine is counting correctly.

The HDR fix is small, but it says something about launch polish on PS5

The other notable tweak is PS5 HDR peak luminance adjustment, described as allowing the game to reach maximum luminance correctly. Translation: Saros wasn’t fully hitting the display output it should have, and Housemarque has now tuned that behavior.

That won’t matter equally to every player. If your setup is basic or you never touch HDR calibration, you may barely notice. But in a game where particle effects, contrast, and readability do a lot of heavy lifting, HDR output isn’t some luxury checkbox. It affects how cleanly visual information lands in motion. Housemarque games are built on visual chaos that still needs to remain readable. If highlights were undershooting, that’s not just a screenshot problem. It can be a clarity problem.

There’s a mild irony here. Saros has been praised for its visual presentation on both PS5 and PS5 Pro, with strong image quality and generally stable performance. But even polished games can ship with calibration quirks that only become obvious once thousands of players run them across wildly different displays. That’s less scandal and more reminder: launch polish is not the same thing as perfection, especially when HDR enters the chat and starts behaving like HDR.

The real question is whether this is the end of the cleanup phase

If I were pressing Housemarque on anything right now, it wouldn’t be “when is the content roadmap?” It would be much simpler: how many more rare-but-run-killing bugs are still sitting below the waterline?

Because update 1.004.002 reads like a studio working through high-priority player pain points after launch telemetry and bug reports rolled in. That’s good. It also means this is probably not the last patch of this kind. When you see fixes for boss-state transitions, clipping, unintended healing, progression gates, and rare crashes all bundled together, you’re looking at a post-launch stabilization pass, not a victory lap.

That’s not a knock. Frankly, this is what competent support looks like. The mistake would be pretending this patch is bigger than it is, or pretending it means there were no meaningful launch issues. There were. They just weren’t systemic enough to demand a redesign. They were the kind of sharp edges that can still cut deep in a game this exacting.

What to watch next

• Whether Housemarque issues another hotfix within the next one to two weeks. If that happens, it likely means more edge-case stability issues surfaced after this patch went live.
• Whether players report retroactive trophy correction or if some affected saves remain awkwardly stuck. Patch notes say the unlock timing was fixed; they do not automatically guarantee every prior edge case was cleaned up.
• Whether boss transition complaints around Shepherd and Priestess actually disappear from player reports. That’s the easiest real-world test of whether this was a true fix or just a reduction in occurrence.
• Whether HDR feedback improves specifically from players on high-end displays. If the luminance cap is now behaving properly, that should show up fast in side-by-side impressions.

The verdict: this is a good patch because it is an unglamorous patch. No feature theater, no fake “major update” branding, no attempt to distract from the actual work. Saros update 1.004.002 fixes the exact kinds of issues that make an excellent action game feel cheap when they appear. If you bounced off a broken trophy trigger or a run-killing edge case, it’s worth jumping back in. If you were waiting for new content, keep waiting. This one is for stability, fairness, and trust – and right now, that’s the smarter use of Housemarque’s time.