Star Citizen Alpha 4.10 is not on the LIVE servers yet. The current public game remains Alpha 4.9, while 4.10 has reached Release Candidate testing on the PTU. The latest verified build is 4.10.0-PTU.12497254, labeled RC1 and available to All Waves on the US-only PTU channel.
Last updated: August 24, 2026. This page separates confirmed information from release-window estimates. Cloud Imperium Games has not published a firm Alpha 4.10 LIVE date and has not issued final 4.10 LIVE wipe instructions. The official RSI PTU status page still identifies 4.10 as the test build and 4.9 as the LIVE build.
The short answer is that 4.10 is close, but RC1 is not the same as a completed LIVE release. CIG is using the late PTU cycle to stress-test mission instancing, Siege of Orison, Recco Battaglia content, cargo missions, fuel balance, the Kruger S-65 Stingray, and backend stability and recovery. A release can follow quickly if the candidate passes, but another RC build is possible if a blocking problem appears.
Star Citizen 4.10 Current Status
| Status Item | Verified Information |
|---|---|
| Current LIVE version | Alpha 4.9 |
| Current 4.10 test build | 4.10.0-PTU.12497254 |
| Candidate label | RC1 |
| PTU audience | All Waves, requiring an eligible backer account and game package |
| PTU server region | US-only in the current patch notes |
| PTU persistence | Long Term Persistence enabled between the listed PTU releases |
| Official LIVE date | Not announced |
| Estimated LIVE window | Late August 2026 if final stress testing finds no release blocker; this is an estimate, not a CIG date |
| LIVE wipe status | No 4.10 LIVE wipe has been announced; final confirmation must come from LIVE release notes |
The build number is more useful than the general term 4.10 because PTU patches can arrive daily. If CIG publishes a newer 4.10 build after 12497254, this article's status block needs an update even if the candidate label remains RC1. The RSI Launcher, the PTU status page, and the newest Spectrum patch-note post should take priority over cached search snippets.
When Will Star Citizen 4.10 Go LIVE?
There is no confirmed release date. CIG originally targeted the 4.10 cycle for August, but the patch remained in testing beyond the earlier mid-August expectation. The studio then described the current phase as the home stretch and requested concentrated testing before rolling the build to LIVE.
The official Alpha 4.10 PTU stress-test announcement asked players to put Siege of Orison, Recco Battaglia, cargo missions, and the Kruger Stingray under real load. That language is a strong signal that the patch is approaching deployment, but it is not a dated release commitment.
A reasonable editorial estimate is late August 2026, provided RC1 or a follow-up candidate passes the final tests. Do not convert that estimate into a guaranteed day. CIG may publish another build, extend the test, temporarily remove a feature, or ship a release with selected content disabled while a blocker is corrected.
| Signal | What It Means | What It Does Not Mean |
|---|---|---|
| All Waves PTU | CIG wants broad testing and higher concurrency | The build is guaranteed to release unchanged |
| RC1 label | The build is a candidate for LIVE validation | RC1 must be the final build |
| Final stress test | Teams are validating load, recovery, and high-priority activities | A release date has been announced |
| LIVE environment warming or deployment notice | A release is actively being prepared | Every player will enter immediately without queues or hotfixes |
Get any Star Citizen service from ExpCarry: raids, dungeons, PvP, leveling, gold, farming, coaching, and custom orders.
What RC1 Means for Alpha 4.10
RC means Release Candidate. In this case, CIG has explicitly labeled build 12497254 as RC1, meaning it is being evaluated as a candidate for the LIVE release. If no blocking defect is found, it can become the basis of the public build. If testing exposes a serious mission, persistence, crash, performance, or economy problem, CIG can issue another candidate instead.
The label does not mean the patch has passed certification, that every known issue is fixed, or that its present tuning is permanent. Star Citizen remains in Alpha, and even a LIVE build can receive rapid hotfixes. Players should read RC as close to release rather than already released.
RC1 build 12497254 is especially important because it arrived after several All Waves builds in quick succession. The sequence shows active iteration on Siege instance state, the Stingray damage model, server recovery, cargo behavior, Recco mission progression, interaction systems, and general performance. The frequency of builds is positive evidence of active fixing, but it also shows that the release package was still changing.
Star Citizen 4.10 Wipe Status
No 4.10 LIVE wipe has been announced. The RC1 PTU notes say Long Term Persistence is enabled, but that line describes persistence within the PTU test cycle. It does not independently guarantee that all LIVE aUEC, ships, items, reputation, refinery jobs, cargo, personal inventory, and character state will transfer into the final release.
The final LIVE release notes are the authority. CIG's release documentation is where any persistence reset, preservation rule, or exception should be confirmed. Until that document exists, the accurate status is no wipe announced, not wipe impossible.
| Wipe Term | Practical Meaning |
|---|---|
| No wipe announced | CIG has not told players that 4.10 LIVE will reset progression |
| LTP enabled on PTU | The test environment is checking persistence between PTU releases |
| LTP preserved in LIVE notes | CIG states that the relevant long-term progression is intended to be preserved, subject to any exceptions listed in the release notes |
| Full wipe | Earned progression is reset according to the categories named by CIG |
| Selective or partial reset | Only specified databases or progression categories are cleared |
Players do not need to liquidate every item because of an unverified rumor. Store important ships correctly, finish valuable refinery or cargo jobs, remove items from risky temporary locations, and take a record of major balances and inventories. If the final notes preserve LTP, normal play can continue. If they announce a reset, the document should explain what survives.
Anyone planning a post-patch ship or equipment goal can use the Star Citizen aUEC calculator after the final LIVE economy and persistence status is known. Current PTU income, prices, and rewards should not be treated as permanent LIVE values.
Star Citizen 4.10 Patch Notes Summary
The official Alpha 4.10 PTU RC1 patch notes list stability, bug fixes, LTP between PTU releases, instanced Siege of Orison, hydrogen fuel balance, quantum-drive balance, the Arlington Lever Action Rifle, Orison Relief Support, Recco Battaglia, Wikelo Inventory Updates, and the Kruger S-65 Stingray among the active testing targets.
| Patch Area | 4.10 Direction | Current Confidence |
|---|---|---|
| Mission instancing | Private mission spaces and the rebuilt Siege of Orison flow | Core 4.10 testing focus |
| Siege of Orison | Small-party instanced FPS operation replacing the legacy public structure | Core 4.10 content |
| Recco Battaglia | Returning story and mission content with progression fixes | Core testing focus |
| Orison Relief Support | Orison-related support activities and mission fixes | Core testing focus |
| Fuel balance | Hydrogen consumption and tank changes plus quantum-drive tuning | Core systems change under active balance testing |
| Arlington rifle | New lever-action FPS weapon | Core testing focus |
| Kruger S-65 Stingray | New medium fighter temporarily opened to selected active PTU testers and included in late-cycle testing | Present in current PTU testing; final LIVE availability and acquisition require release notes |
| Wikelo inventory | Updates to available inventory and related progression | Present in late PTU testing |
| Stability and recovery | Server-load distribution, crash recovery, persistence, and mission-state corrections | Ongoing release-blocking focus |
This is not a promise that every experimental asset seen in an early PTU build will ship. Content can be removed, delayed, retuned, or disabled. The final LIVE notes should replace this preview table once 4.10 deploys.
Instanced Siege of Orison
The headline 4.10 activity is a rebuilt Siege of Orison that uses Mission Instancing. The legacy version was a large public event spread across Solanki, Brushwood, Hartmoore, and the Admin Center and included ship combat. The reworked version removes ship combat and creates a private, closed FPS instance for a solo player or a party of up to four.
The reworked route uses three islands: Solanki, Hartmoore, and the Admin Center. Players enter from Orison through the Crusader Industries Showroom rooftop and the Instance Transit Platform. Inside the instance, the group clears Nine Tails resistance, resets Security Network Control Towers, defeats island lieutenants, restores IFFI control, and ultimately confronts Mendo Ren.
Instancing is more important than a single event. CIG is testing closed mission spaces with controlled access, party ownership, isolated objectives, transport transitions, respawn handling, and recovery behavior. That is why premature completion, instance-elevator access, server recovery, AI positioning, and mission-state synchronization have received repeated fixes.
Players should not interpret instancing as a guarantee of perfect performance. The mission still depends on backend services, entity streaming, AI, inventory, transport, and server recovery. A private space removes interference from unrelated players, but it does not remove every source of desync or mission failure.
Recco Battaglia and Orison Relief Support
Recco Battaglia returns as a major 4.10 testing target. Earlier PTU builds used accelerated reputation or progression so players could reach later stages quickly, but build 12488012 explicitly removed that acceleration. RC1 still lists Recco Battaglia as a testing focus, so older accelerated PTU rates should not be treated as current or as evidence of the final LIVE progression speed.
Recent candidate fixes have targeted story calls, travel objectives, redirects to Levski, mission-location assignment, and progression after unusual travel or respawn behavior. These fixes matter because a story chain can appear playable while still failing when a player exits quantum travel early, dies between stages, or shares a destination with another group.
Orison Relief Support is also part of the focus. In PTU testing, this mission set has involved delivering materials and medical supplies and crafting requested support items after the Nine Tails attack on Orison. The final release notes still need to confirm exact contract availability, rewards, prerequisites, and economy values.
Hydrogen Fuel and Quantum Drive Balance
Alpha 4.10 includes a broad fuel-balance pass covering both Hydrogen and Quantum fuel. CIG's roadmap describes changes to fuel-tank capacities and consumption rates intended to better align ships with their sizes and roles. Because the PTU values are still being tuned, players should judge effective range and endurance from the current build rather than assuming one early data set is final.
Players should compare effective range rather than raw capacity. Test a repeatable route, start with a known fuel level, record distance and consumption, and repeat the route after a new build. Atmospheric flight, boost usage, ship mass, component selection, and travel behavior can make two casual observations incomparable.
The practical LIVE preparation is modest. Do not replace every quantum drive or reorganize a fleet based on one PTU spreadsheet. Wait for the release build, check current component statistics, and run a short route before committing a long cargo, salvage, mining, or exploration operation. Fuel values can continue moving until deployment and may receive a follow-up balance patch.
Kruger S-65 Stingray
The Kruger S-65 Stingray entered late 4.10 PTU testing as a medium fighter. CIG temporarily made it available to testers who had put substantial time into the PTU testing cycle. That test-access method does not establish the permanent LIVE purchase location, price, pledge availability, or unlock requirement.
The RC1 cycle has included potential fixes for the Stingray's damage behavior. One issue made the cockpit take damage incorrectly and become unusually resistant to targeted fire. Another left the tail section outside the intended shield protection, allowing damage to pass directly to the hull. These examples show why early combat impressions and time-to-kill results should not be treated as final balance evidence.
Evaluate the LIVE Stingray only after confirming its final armor, shields, weapon configuration, fuel values, component access, and acquisition method. PTU access can be designed to generate test data rather than describe the finished progression path.
Arlington Rifle, Equipment, and Wikelo Updates
The Arlington Lever Action Rifle is a confirmed 4.10 testing focus. It adds a distinct manual-action FPS weapon to the current equipment pool. Damage, fire behavior, ammunition availability, attachments, acquisition, and economy placement should be checked again in the LIVE release because test-build loot and shop distribution can change.
Wikelo inventory updates are also present in the late PTU cycle. Do not assume that every item visible during testing will keep the same requirement or cost. Reputation gates, mission items, blueprints, materials, and offer availability are all common balance levers.
Players comparing replacement FPS kits before Siege or other 4.10 missions can review current Star Citizen armor options, but the game client should decide which protection class and inventory capacity fit the final patch. Any new 4.10 equipment should be treated as provisional until it appears in the LIVE notes and actual LIVE loot or store tables.
Important Fixes in RC1 Build 12497254
RC1 is primarily a validation build, so several changes are listed as potential fixes rather than proven permanent solutions. A potential fix means CIG has changed the relevant code and needs players to reproduce the original scenario. It should not be reported as completely solved until broad testing confirms the result.
- Siege premature completion: The instance could be marked complete immediately after the briefing or before the player activated the correct session area.
- Stingray cockpit damage: Incorrect damage behavior could make the cockpit nearly invulnerable to aimed fire.
- Stingray tail protection: The tail could sit outside shield protection and take direct hull damage.
- ASOP retrieval: A vehicle's Retrieve action could remain permanently grey after an incorrect storage transition.
- Server recovery AI: Siege NPCs could ignore assigned defense zones after a server-crash recovery and rush players immediately.
- Recover Cargo duplication: Contract cargo could duplicate in large quantities inside a freight elevator after mission completion.
- Refueling completion: Some refueling contracts could fail to complete after the target ship was successfully fueled.
- Recco story calls and markers: Early quantum exit or redirection could leave calls missing or travel objectives stuck on the HUD.
- Mission-location collisions: Multiple players could be sent to the same Battaglia location and arrive at an occupied or invalid objective.
- Item Recovery pricing: Weapons and racks in personal locations could appear without the intended claim cost.
The build also includes further server-load balancing and performance work. That category is intentionally broad because backend improvements are evaluated through concurrency, session duration, recovery tests, and service telemetry rather than one visible gameplay change.
Current RC1 Known Issues and Validation Areas
RC1 currently lists two official Known Issues: a delay before the instance elevator moves and a brief client stall or freeze when the main instance streams in at the second forcefield. The other rows below are recent RC1 potential-fix areas that still deserve validation; they are not additional entries in the official Known Issues list.
| Area | Current RC1 Status | What Players Should Know |
|---|---|---|
| Instance elevator | Official Known Issue: the elevator can take a noticeable time to start moving after the button is pressed | Wait for the elevator response before assuming the instance is broken |
| Main-instance streaming | Official Known Issue: the client can stall or freeze for a few seconds at the second forcefield while the main instance streams in | A short stall is documented in RC1; a persistent lockup should still be reported |
| Siege premature completion | RC1 potential fix: the instance could complete before the intended objectives began | Treat the fix as provisional until it survives wider testing |
| Server-recovery AI | RC1 potential fix: Siege NPCs could abandon assigned Defend Areas after server recovery | Report repeatable post-recovery behavior with the build number and mission stage |
| Stingray damage model | RC1 potential fixes cover cockpit damage and the tail section sitting outside intended shield protection | Do not treat PTU time-to-kill or durability tests as final balance data |
| Vehicle retrieval | RC1 potential fix: the ASOP Retrieve action could remain permanently grey after an incorrect storage transition | Re-test the same retrieval flow before reporting the issue as solved |
| Recover Cargo duplication | RC1 potential fix: contracted cargo could duplicate in large quantities in a freight elevator after mission completion | Do not exploit duplication; document a reproduction and report it |
| Battaglia and refueling mission state | RC1 potential fixes cover stuck Battaglia calls or markers, duplicate mission locations, and refueling contracts failing to complete | Capture the exact mission stage and sequence of actions if the problem still reproduces |
Use the Issue Council for reproducible defects. Include 4.10.0-PTU.12497254 or whatever newer build is actually shown in the launcher, plus the server region, approximate time, location, mission name, party size, and the actions immediately before the failure. A report that only says the mission is broken is much harder to verify.
How to Access the 4.10 PTU
All Waves does not mean every free account can enter. The current access rules require an eligible backer account with an active game package. The PTU channel can also be disabled between tests, and the present patch notes identify US-only servers.
- Sign in to the RSI website and open account settings.
- Select Public Test Universe and copy the account when the option is available.
- Open the current RSI Launcher and select the PTU channel.
- Install or update the PTU client separately from LIVE.
- Check that the launcher shows 4.10.0-PTU.12497254 or a newer build before testing.
- Read the matching patch notes because test focus and known issues can change between builds.
PTU progress is isolated from LIVE. Credits, ships, equipment, mission progress, and rewards earned during testing do not become LIVE progression. Account copies may also be reset during the test cycle, so PTU should be used for validation and previewing rather than permanent farming.
How to Prepare for the 4.10 LIVE Update
Preparation should protect time and reduce confusion without reacting to rumors. Finish time-sensitive work, store important assets properly, note current balances, and avoid beginning an operation that cannot be completed before a possible maintenance window. There is no need to stop playing solely because RC1 exists.
- Complete refinery jobs, cargo deliveries, and long mission chains that are already close to finishing.
- Store ships at a recognized location instead of leaving them in an uncertain or destroyed state.
- Move valuable equipment out of temporary containers or vehicles when practical.
- Record aUEC, purchased ships, reputation, and rare inventory for troubleshooting.
- Save control, graphics, and custom configuration files before updating.
- Wait for the final LIVE notes before assuming a full or partial wipe.
- After deployment, verify fuel range, item availability, missions, and ship loadouts before risking valuable cargo.
Large patches can produce queues, entitlement delays, missing items that later return, and temporary backend instability. Do not immediately rebuy an expensive ship or component because it is absent during the first minutes after deployment. Confirm the service status, relog safely, and allow the entitlement process time to complete.
How to Check Whether This 4.10 Status Has Changed
Alpha 4.10 can change quickly during the release-candidate stage. To verify whether the status above is still current, compare the RSI Launcher, the official PTU status page, and the newest Spectrum patch notes. The build number, PTU audience, RC label, server region, LIVE version, wipe statement, and deployment notice are the fields that matter most.
| What Changes | What to Verify |
|---|---|
| A new PTU build releases | Check the new build number, candidate label, active known issues, testing focus, and potential fixes |
| CIG announces a LIVE deployment | Use the official date and time instead of the late-August estimate |
| Final persistence information appears | Check exactly which progression categories are preserved, reset, or subject to exceptions |
| 4.10 deploys to LIVE | Confirm the LIVE build number and use the final release notes instead of PTU assumptions |
| A hotfix releases | Check whether it changes known issues, missions, economy values, persistence, or availability |
| A feature is removed or disabled | Treat the feature as unavailable until CIG restores or re-confirms it |
If a newer official source conflicts with this page, follow the newer source. In particular, do not treat an estimated release window as a confirmed date: only a CIG deployment announcement or final LIVE release notes can settle the release timing and persistence status.
Star Citizen 4.10 Release FAQ
- Is Star Citizen 4.10 LIVE? No. At the time of this update, LIVE is 4.9 and 4.10 remains on the PTU.
- What is the latest 4.10 build? The latest verified build is 4.10.0-PTU.12497254, labeled RC1.
- When will 4.10 release? CIG has not announced a firm date. Late August is a reasonable estimate if final testing succeeds, but it is not guaranteed.
- Will Alpha 4.10 wipe progress? No LIVE wipe has been announced. PTU LTP is enabled, but final LIVE release notes must confirm preservation or reset details.
- Can every player access the PTU? It is open to All Waves/All Backers, but the RSI PTU rules still require a backer account with an active game package.
- Does RC1 mean the patch is finished? No. It means the first release candidate is being validated and can still be replaced.
- What is the biggest 4.10 addition? Mission instancing and the reworked Siege of Orison are the central new activity and technology test.
- Are PTU rewards permanent? No. PTU progression and rewards do not transfer to LIVE.
- Should players trust exact PTU prices and payouts? No. Economy, acquisition, reputation speed, and rewards may change before LIVE.
Conclusion
Star Citizen Alpha 4.10 has reached the final part of public testing but is not LIVE. Build 4.10.0-PTU.12497254 is RC1, available to All Waves on the US-only PTU channel, while Alpha 4.9 remains the public LIVE version. CIG has not announced an exact release date. The late-August window is an evidence-based estimate from the RC and stress-test stage, not a promise.
No 4.10 LIVE wipe has been announced, and PTU Long Term Persistence being enabled is not a substitute for final LIVE confirmation. The patch centers on mission instancing, the rebuilt Siege of Orison, Recco Battaglia, Orison Relief Support, fuel and quantum-drive balance, the Arlington rifle, Wikelo updates, the Kruger S-65 Stingray, and stability work. Check the newest official patch notes before making decisions, because another candidate, a changed feature list, or revised wipe instruction can replace any pre-release detail.
