Patch 1.5 goes live: network routing, CPU workarounds, and a pile of softlock fixes

Patch 1.5 landed – it’s boring, necessary, and exactly what players were screaming for

There’s no flashy DLC or new level – just plumbing. Patch 1.5, pushed to Steam on Feb. 27, is a stability-first update that changes how the game talks to Epic Online Services, applies hardware workarounds for modern Intel chips and some AMD driver combos, and unsticks a string of progression-blocking softlocks. That kind of maintenance work rarely gets praise, but it’s the difference between a playable experience and a multiplayer trainwreck.

• Biggest change: EOS packet routing was reworked to lower ping and reduce desyncs.
• Hardware fixes: Workarounds added for overheating crashes on 13th/14th‑gen Intel CPUs and for certain AMD driver/hardware pairings.
• Progression bugs: Multiple softlocks fixed across Opera House, Forest Village, Bunker Puzzle, Barn, and Orphanage scenes.
• Known limits: Shader precompilation can still hang on some AMD CPUs and the game still enforces disconnection at >300ms ping.

Why this matters – and why the routing change is the leadoff

Players running into desyncs and disconnects don’t care whether a team fixed a texture or tweaked AI — they care about the game staying in sync long enough to finish a mission. Reworking EOS packet routing is the kind of backend tweak that can materially cut both latency spikes and the subtle state mismatches that lead to desyncs. In regions where EOS doesn’t have local servers, routing matters more than ever. This is an operational fix, not a prestige feature.

Hardware workarounds: useful, but not a miracle

The patch adds explicit workarounds for overheating crashes encountered on 13th and 14th‑gen Intel CPUs and a stopgap for “certain AMD hardware and driver combinations.” That will stop some immediate blue‑screen‑style exits. But workarounds are exactly that — they paper over driver or microcode faults rather than fix the root cause. Expect some users on unusual AMD stacks (the team cites a Ryzen 5 3400G as an example) to still see painfully long shader precompiles. Those hardware-level quirks typically need vendor driver updates or firmware changes to disappear for good.

The softlocks they actually fixed (and the one-short-of-fix)

Patch 1.5 clears a handful of reproducible progression-blockers: blocking volumes not re-enabling in the Opera House tank section, triggers bypassed in Forest Village, respawn misstates after the Bunker Puzzle, frozen movement in the Barn, and stuck progression in the Orphanage’s stacked beds room. That’s real, quality-of-life salvation for players who were grinding to an otherwise impossible halt.

One caveat: the transition from the tank scene to the final “Sheep Beast” encounter now has a partial black-screen fix — the developers note the edge case may still occur. Partial fixes like that are useful but remind you that complex scene transitions and state handoffs are fragile, especially in multiplayer.

The uncomfortable observation

There’s a design choice in play here: the game still forcibly disconnects clients with ping over 300ms to avoid catastrophic desyncs. That’s a defensible safety measure, but it’s also a blunt instrument that locks out players in high‑latency regions or on flaky home networks. The studio says it’s looking at raising that threshold alongside other server-side changes in a follow-up patch in “a couple of weeks.” That’s the right plan — but the timeline matters. If you live somewhere with middling internet, your ability to play remains at the mercy of the next patch.

Why you should care about the wider pattern

This isn’t unique. Other Steam posts in the past week — from a major multiplayer shooter scheduling stability fixes for March 3, to a long-running strategy title warning players about save-breaking beta changes and offering rollback branches — show the same reality: post‑launch life is messy and iterative. Patches are increasingly about stability, routing and rollback options rather than content. It’s the new normal for live, multiplayer-first projects.

What I’d ask the developers if I had one question

Which metric will you use to justify raising the 300ms disconnect threshold — average client desync rate, server tick recovery success, or something else? Also: can you list the specific AMD driver versions and GPU models affected so users can make an informed choice about rolling back drivers?

What to watch next

• Follow the studio’s next patch in “a couple of weeks” — the team says that update will revisit the 300ms threshold and deploy additional network/server changes.
• Look for driver updates from AMD and microcode/firmware updates for Intel CPUs; true fixes to shader precompilation and overheating crashes may require vendor patches.
• Watch community reports for any regressions after the patch. Recent Steam posts across other games show that fixes can sometimes introduce new issues or force rollback branches.

TL;DR

Patch 1.5 is a targeted, necessary stability pass: EOS routing tweaks to reduce ping/desyncs, workarounds for 13th/14th‑gen Intel and some AMD setups, and multiple progression softlock fixes. It won’t fix every edge case (shader precompile and the 300ms disconnect rule remain), but it buys time and improves playability while the studio prepares a follow-up update.