Arc Raiders finally stops crashing every raid – but Embark’s still ignoring the obvious fix

When a “small” patch quietly decides whether your co-op shooter is playable or not, that’s a problem. Arc Raiders’ Patch 1.24.0 isn’t some nice little tune-up before the Riven Tides update – it’s the emergency repair job that should’ve shipped weeks ago, while Embark somehow still refuses to fix the one live-service headache players keep shouting about.

Key takeaways

• Patch 1.24.0 finally tackles frequent, raid-killing crashes across PC, PS5, and Xbox Series X/S, plus a handful of nasty visual and audio bugs.
• AMD FSR Frame Generation now produces sharper, more accurate visuals, and a Vanguard cosmetic bug that distorted player models has been fixed.
• Embark is pausing its weekly patch cadence to finish the late-April Riven Tides update – this is effectively the last Flashpoint-era patch.
• Community Projects are still expiring with no in-game timers, a design choice players are calling “utterly ridiculous” as events keep vanishing.

Crashes first, explanations later

Arc Raiders has been living in that annoying space where the core idea is good, the atmosphere is compelling, and then your game just faceplants midway through a raid. Recent updates under the Flashpoint banner brought more content and systems, but they also dragged in a wave of stability issues – enough that some players joked the most dangerous enemy was the crash to desktop.

Patch 1.24.0, released April 14, 2026, is Embark finally hitting the brakes. On paper, it’s the usual laundry list: crash fixes, stability improvements, platform parity tweaks across PS5, Xbox Series X/S, and PC. In practice, this is the patch that’s supposed to stop “every other raid” from imploding, as some coverage bluntly described it.

We don’t get a detailed technical breakdown of every root cause here – this isn’t a postmortem, it’s a bandage – but the studio clearly chased multiple crash sources that spiked after the last content drop. If you’re the kind of player who bounced off after two or three lost runs, this is the update that might actually tempt you back in.

It also marks the final update of the current Flashpoint season. Embark is parking its weekly patch rhythm to put heads down on Riven Tides, the next big content beat slated for late April. That’s normal for live-service development – you consolidate, stabilize, and then roll the dice on the next wave – but when stability has been this fragile, that pause comes with pressure. Riven Tides doesn’t get to ship with another round of “we’ll fix the crashes next week.”

The small fixes that hit you mid-raid

Beyond “stop breaking,” Patch 1.24.0 cleans up a few issues that don’t sound dramatic on paper but absolutely mess with your experience in the middle of a firefight.

The most obvious one: a Vanguard Set bug where equipping the cosmetic could cause your player model to stretch and distort – and crucially, other players saw it too. This isn’t just an immersion break; in a third-person co-op shooter, character silhouettes are basic readability. If one squadmate looks like an eldritch balloon animal, your brain has to work harder to parse threats, allies, and cover in your peripheral vision. That’s now fixed.

Then there’s the audio issue on Stella Montis. Sound in Arc Raiders is meant to carry a lot of weight: threat cues, line-of-sight information, environmental storytelling. A bug tied to line-of-sight around Stella Montis was undermining that, leading to inconsistent or missing audio in a place where you should be picking up on danger and direction. With 1.24.0, that’s been addressed – which matters a lot more than yet another damage tweak or loot table shuffle.

On PC, AMD FSR Frame Generation finally gets the respect it deserved on day one. Players running it were reporting soft, blurry visuals – the classic upscaling problem where you’re trading clarity for frames and getting too little of either. The new patch sharpens things up and corrects visual issues when FSR Frame Gen is enabled, which is a big deal if you’re trying to keep frame rates stable on mid-range hardware without the image turning to mush.

Call this what it is: a belated attempt to make Arc Raiders look and sound like the game its trailers promised, with modern performance tech turned on. Upscaling and frame generation are no longer niche features; they’re standard on PC. If your game looks wrong with them enabled, that’s on you, not the player’s settings.

Projects without timers are a design own goal

Now to the part Embark would probably prefer people didn’t dwell on: community Projects that quietly vanish without warning.

On the bright side, Patch 1.24.0 fixes an issue where late contributors to the Weather Monitor Station Project weren’t getting their rewards properly. If you showed up near the end, helped push the community over the line, and walked away empty-handed, that should now be resolved. That’s the bare minimum – if you ask players to grind for communal objectives, their payouts better be rock solid.

The bigger problem is still untouched: Projects can expire, and players still don’t get a basic countdown timer or clear in-game indication of when that will happen. According to reporting and community reaction, another Project is already slated to disappear, and the sentiment is about as subtle as you’d expect – “utterly ridiculous” is one of the more printable phrases being thrown around.

This isn’t some cutting-edge design dilemma. Destiny 2, Helldivers 2, even the most shameless battle passes on mobile all understand one simple rule: if content is limited-time, you tell players exactly how limited. Timers, end dates, progress trackers. It’s not just courtesy; it’s trust. When an event vanishes with little or no in-game warning, it feels like the game is wasting your time.

Right now Arc Raiders is sitting in the worst possible middle ground: it wants the energy of shared, time-limited objectives, but it doesn’t give players the tools to plan their play sessions around them. That’s how you turn what should be a fun communal push into a mild betrayal. And it’s not a hard technical problem – it’s a product decision.

If I had one question for Embark’s PR team, it’d be this: why are you willing to spend weeks tracking down obscure crash scenarios, but you still won’t put a visible countdown on content that literally disappears? Because from the outside, it looks less like an oversight and more like stubbornness.

Cosmetics keep coming, even as basics lag behind

Like any modern co-op shooter built for the long haul, Arc Raiders has a cosmetic pipeline to feed. Patch 1.24.0 quietly adds at least two more purchasable sets – the Nascosto and Scrappy Speckled outfits – to the in-game store.

On one level, this is just the reality of the business. Live-service games live or die on how effectively they can sell looks without selling power. Taking a break from monetizing cosmetics because your patch is focused on bug fixes would be a nice PR stunt, but it wouldn’t be financially honest. Teams staffing art and monetization pipelines aren’t the same people chasing crashes.

But optics still matter. When players see new paid cosmetics arriving in the same breath as fixes for issues that were literally making the game unplayable, this is the connection they draw: there’s always time to polish the store, yet somehow not enough time to add a basic project timer or ship without catastrophic stability issues.

Embark isn’t the first studio to get caught in that perception trap, and it won’t be the last. The only way out is consistency. If the game feels stable, transparent, and respectful of player time, nobody complains about cool new outfits. When those foundations wobble, every new skin looks like a middle finger.

Pausing weekly patches before Riven Tides is a gamble

With 1.24.0 out, Embark is hitting pause on its weekly patch cadence to focus fully on Riven Tides, due late April. In theory, that’s a healthy sign: stop doing surface-level firefighting, stabilize the current build, and concentrate on shipping the next big drop in better shape.

In practice, this means two things:

• If crashes aren’t genuinely fixed, there probably won’t be another hotfix until very close to (or bundled with) Riven Tides.
• Riven Tides is now carrying the burden of resetting player sentiment on both content cadence and basic reliability.

Flashpoint, the current season, has been a mixed bag: cool ideas in theory, some strong atmospheric beats, but undermined by technical issues and UX decisions like the timer-free Projects. Riven Tides doesn’t just need fresh objectives and enemies; it needs to prove that Embark has learned from the last few months.

The studio’s own trailers and teases have leaned into escalating threats, new tech, and more demanding cooperative play. That only works if the foundation is solid. You can’t sell “strange sensor patterns and menacing shredders near the spaceport” – as one Flashpoint trailer did – when the most ominous thing in your game is the possibility of a crash on extraction.

Patch 1.24.0 is the line in the sand. Either it stabilizes the game enough that Riven Tides can be judged on its ideas, or it doesn’t, and the narrative becomes very simple: Embark keeps building cool towers on a cracked foundation.

What to watch next

• Crash reports post-1.24.0: Over the next week, Steam reviews, subreddit threads, and console communities will tell us quickly whether the most serious stability issues are actually gone.
• Riven Tides launch (late April): Does the new content land without major technical blowback? A clean launch would be a badly needed narrative reset.
• Project UX changes: If a future patch finally adds visible timers or clearer expiry info for Projects, that’ll be a sign Embark is listening on the right issues.
• FSR and performance tuning: If the new FSR Frame Generation fixes stick and performance remains strong, it’ll make Arc Raiders far more attractive to mid-range PC players.