StarRupture Hotfix 0.2.8 dropped on June 17, 2026, the fourth hotfix in just over a month and the one that finally addresses the most-reported crash in the Steam Crash Reporter: a crash on exit affecting NVIDIA RTX 40 and 50 series GPUs. It is the cleanup beat at the end of a sprint that produced 0.2.5, 0.2.6, 0.2.7, and now 0.2.8, and most of the meaningful changes in that sprint were aimed at co-op and dedicated server play.
If you run a StarRupture server, this is the run of patches you have been waiting for. Below is what changed, in the order it ships.
Release Date
Hotfix 0.2.8 is live on Steam as of June 17, 2026. The patch is small in scope (one main fix) but lands on top of three earlier hotfixes that introduced almost all of the multiplayer and dedicated server stability work since the May 6 Hotfix 0.2.4 we covered previously.
What's in Hotfix 0.2.8
Patch 0.2.8 is a single-issue release:
- Fixed crash on exit on NVIDIA RTX 40 and 50 series GPUs. This was one of the most-submitted reports through the in-game Crash Reporter. If your players were seeing the game hang or crash when leaving to desktop after a session, this is now resolved.
That is the entire 0.2.8 changelog. The reason the post is worth your attention is what shipped in the three hotfixes before it.
Hotfix 0.2.7 (June 11): Co-op Dialogue and Distance Fixes
Patch 0.2.7 fixed two issues that hit co-op groups specifically:
- Dialogues no longer get skipped for the client when the host is far away. This is the bug that made early co-op runs feel inconsistent: if the host walked off mid-conversation, the client lost the entire dialogue.
- Crash when deconstructing buildings. Building loop crashes were a known recurring issue across hotfixes; this one closes another vector.
- Crash Reporter improvements. New response window in the Crash Report Tool to help identify the cause of a crash and suggest self-troubleshooting steps. Useful for server admins triaging player reports.
Hotfix 0.2.6 (June 2): The Big Multiplayer & Dedicated Server Patch
This is the meaty one. Hotfix 0.2.6 is where most of the dedicated server work this cycle landed:
Dedicated server fixes
- Fixed an issue with dedicated servers crashing on loading game sessions in certain scenarios. This is the headline fix for anyone running a persistent StarRupture server: the load-time crash was a real blocker for hosted sessions.
- Fixed battle music looping in the Forgotten Engine Control Room on dedicated servers.
Co-op multiplayer fixes
- Fixed an issue where every player could hear each co-op player's dialogues (the audio bleed bug).
- Fixed an issue where clients couldn't hear dialogues in co-op sessions.
- Fixed co-op players turning into a T-pose animation when their grenade throw was interrupted by equipping the Harvester.
- Lobby slots now correctly display player status when hovered.
- Fixed missing Fire Wave VFX for co-op players joining mid-session.
- Fixed an issue where multiplayer settings became unresponsive after changing session visibility.
Crash and performance
- Fixed a crash that occurred on some save files upon approaching bigger bases. This one is the reason your players with hundreds of hours of build progress were dropping at the worst moments.
- Fixed a crash related to large save file size.
Building
- Fixed an issue where Pillar Support could be placed despite being unstable.
- Fixed Habitat stability status on saves from before 0.2.5.
- Fixed deconstruction of a merged Viewport in co-op sessions.
Hotfix 0.2.5 (May 18): Quality of Life and Fire Wave Crashes
The first hotfix in this cycle was the QoL beat:
- Autosave interval option added. Server admins can finally tune autosave cadence per session.
- Decreased Platform stability cost, enabling bigger constructions without scaffolding workarounds.
- Closed a long list of crashes tied to the Fire Wave sequence: crashes while running during a Fire Wave, crashes at the start of a Fire Wave, crashes from improper item spawning after a Fire Wave, and a separate batch of crashes tied to Drones using the Rail system.
- Building stability and Zipline Pole placement fixes in co-op sessions.
What This Means for Your Server
Pulling the four hotfixes together, here is what changed for hosted StarRupture servers between May 7 and June 17, 2026:
- The load-time crash on dedicated servers is fixed. If your server was failing to load sessions in 0.2.4, take a fresh restart on 0.2.8 and the issue should be gone.
- Co-op audio bugs are resolved. Dialogue bleed, client-side audio gaps, host-distance dialogue skips: all closed.
- Autosave is now configurable per session, so you can balance disk writes against rollback risk.
- Build progress is safer. The big-base save crash and large save file crash are both fixed, which means players with serious infrastructure stop dropping into the void.
- Crash reporting is more useful for diagnosing what your players actually hit. The Crash Report Tool's new response window helps server admins triage from log uploads.
If you are running a StarRupture server, the practical move is: pause it, let the panel pull 0.2.8, restart, and tell your players to verify game files in Steam so the client matches.
Worth Coming Back For?
If you bounced off StarRupture's co-op in early May because of audio bugs or load crashes, this run of hotfixes is the reason to come back. The June cycle is mostly about closing stability gaps from Update 1 rather than introducing new content, but it is the kind of patch run that turns "interesting but unstable" into "playable for a full season."
Host Your StarRupture Server with DoomHosting
A DoomHosting StarRupture server ships on dedicated Ryzen 9 hardware, with one-click setup, full FTP access for save and config tweaks, DDoS protection, and 24/7 support. We track Steam patches as they land, so 0.2.8 is already deployable on the panel today.
Spin up a server in under five minutes and bring your co-op group back to the platform now that the audio and load-time bugs are finally behind us.
