Star Citizen’s Siege of Orison Stream Exposed a Bigger Alpha 4.10 Problem

Star Citizen’s Siege of Orison Stream Exposed a Bigger Alpha 4.10 Problem

ethan Smith·8/20/2026·3 min read
Star Citizen’s August 5 Siege of Orison developer stream collapsed under desync, weapon, inventory, AI, and mission-progression bugs on an internal build.

A controlled developer showcase is supposed to be the safest possible place to demonstrate progress. Instead, Cloud Imperium Games’ August 5 Star Citizen Live: Gamedev – Siege of Orison broadcast put failures in the game’s basic combat and mission systems in full view.

The session was built around the reworked, instanced Siege of Orison co-op FPS event planned for Alpha 4.10. It ran on an internal/private environment rather than the public test universe, yet desync repeatedly disrupted the action. Weapons failed to behave reliably, reloads and swaps caused friction, inventory access interrupted the flow, and AI enemies were slow, idle, frozen, or inconsistent in combat. Performance also dropped sharply around encounter areas.

The decisive problem was mission state. The developers were unable to progress through the encounter cleanly, leaving the run effectively unfinishable after roughly 90 minutes to two hours. That makes this more damaging than a routine rough PTU session: the presentation was meant to show the intended Siege of Orison experience, but it demonstrated a build CIG considered ready to show publicly struggling with its central gameplay loop.

FinalBoss // Gear

Level up your setup

01Flight sticks & HOTASon Amazon02High-refresh gaming monitorson Amazon03Gaming chairson Amazon

Affiliate links · As an Amazon Associate, FinalBoss earns from qualifying purchases.

Screenshot from Star Citizen
Screenshot from Star Citizen

For players comparing the stream with their own install, the distinction matters. Alpha 4.9 LIVE, released July 15-16 as build 4.9.0-LIVE.1825000, is separate from Alpha 4.10 PTU work. The live patch included more than 166 bug and crash fixes since 4.8, including 73 from Issue Council reports. Meanwhile, August PTU updates continued to target Siege of Orison desync, mission flow, server crashes, elevator states, loading barriers, and performance near Orison.

The practical checks are straightforward: test sprinting and interaction prompts, reloads and weapon swaps, gear equipping and inventory transfers, objective updates, respawn flow, elevators, and NPC combat behavior. Those are the exact systems that failed under the stream’s pressure.

Screenshot from Star Citizen
Screenshot from Star Citizen

With Star Citizen announced in 2012, in early access since 2017, and funded by more than $1 billion, Alpha 4.10 needs to show that Siege of Orison can complete consistently before it can serve as evidence of improved delivery cadence.

Was this worth your time?

e
ethan Smith
Published 8/20/2026