Star Citizen Alpha 4.10.2 PTU Wave 3 is now available to all players on a US-only test channel, with long-term persistence enabled. This build is less about flashy new systems and more about stability, mission reliability, and cleaning up several frustrating bugs that have been affecting everyday play in Stanton. For anyone jumping into the PTU, the real value of this patch is understanding what Cloud Imperium wants tested and which fixes are most important to verify before the build moves to LIVE.

What you’ll learn: this overview breaks down the current PTU focus, the event mission changes in Stanton, the most notable fixes, and the bugs that still need attention. If you are planning your next session, optimizing mission runs, or protecting your progression budget for ships and components, this patch has a few practical changes worth knowing.

The Main Focus of 4.10.2 PTU Wave 3

The headline for this PTU is simple: stability, bug fixing, and LTP validation. The previous time-to-kill tech preview is not part of this test, so weapon and shield behavior has effectively returned to the normal baseline for now. That means players should not treat this build as a balance preview for combat meta changes. Instead, it is a functional test focused on whether core systems behave more consistently across sessions and whether mission content in Stanton is more reliable.

Long-term persistence matters here because it directly affects player progression. Ships, components, inventory, and mission-related items all feed into the wider economy of credits and aUEC. When persistence works poorly, losses can feel arbitrary. When it works properly, planning upgrades and ship purchases becomes much easier, especially for players managing a long-term hangar path or looking for aUEC for ship upgrades without wasting time replacing bugged-out losses.

No TTK Tech Preview This Time

One of the most immediate takeaways is what is not in this build. The TTK rebalance test from earlier PTU waves has been removed, so players should expect normal weapon and shield interactions instead of the more experimental combat values seen previously.

That is probably the right call for this stage of testing. Combat balance is only useful to evaluate when the broader environment is stable enough to produce consistent outcomes. If mission markers fail, targets do not spawn, or ship systems behave unpredictably, then combat data becomes less meaningful. For bounty hunters and PvE-focused pilots, this return to baseline should make mission performance easier to judge while CIG continues refining those broader systems.

Stanton Event Missions Are a Major Testing Target

The other big pillar of this PTU is the current in-system event content in Stanton. These event missions are available through the Contracts tab in the Mobiglas, and they appear to be one of the key areas CIG wants players to stress test.

The most welcome change is a balance pass on event contracts and rewards. Previously, event progression could feel wildly out of step with the reputation required to unlock rewards. Earning tens of thousands of reputation while missions only granted tiny amounts created a grind that did not feel proportionate to the effort involved. That issue affected both pacing and motivation, especially for players who prefer efficient Star Citizen mission aUEC routes and want their time investment to feel worthwhile.

If this rebalance lands well, event participation should feel less punishing and more in line with the challenge level of the contracts. It may also help event content become a more realistic part of a broader aUEC making guide approach, rather than something players avoid because the progression curve is too steep.

Civilian NPCs Removed From UGF Locations

Another notable event-related adjustment is the removal of civilian NPCs from UGF locations following feedback from both internal staff and players. This should reduce confusion and lower the risk of accidental failures or reputation damage during combat-heavy runs.

For bunker-style or hostile-clearance content, cleaner target identification is a major quality-of-life improvement. Friendly and civilian presence can add atmosphere, but if it interferes with readability during active engagements, it creates more frustration than depth. This change should make those locations easier to run efficiently, especially for players focused on repeatable combat income.

Event Ship Components and Inventory Occupancy

The PTU notes also point to inventory occupancy now passing correctly on new event ship components. That sounds technical, but in practice it matters a lot. Problems with event-earned items or installed components can undermine the reward loop entirely, particularly when players are trying to convert event participation into meaningful progression.

Anything that improves item persistence and component handling is good news for players budgeting around repairs, upgrades, and replacement costs. In a game where ship setup can represent a serious investment, stability improvements indirectly support the wider loop of Star Citizen money making because fewer bug-related losses mean more of your in-game income stays productive.

One of the best practical fixes in this build is the correction to ship power state on retrieval. Ships should now change power state correctly when called from the ASOP terminal, and engines should no longer remain enabled when the ship arrives.

This may sound minor, but it addresses one of those immersion-breaking and occasionally dangerous bugs that players remember because it creates chaos in hangars. Ships unexpectedly hovering, drifting, or colliding with hangar geometry were not common every session, but when it happened, it was memorable for all the wrong reasons.

For everyday play, this fix improves reliability at the exact moment every session begins. That matters whether you are heading out for cargo, bounties, salvage, or event content. Fewer retrieval issues also mean less wasted time before a run, which is especially valuable for players with limited sessions who want smoother progression or even compare their grind time against options like how to smooth out Star Citizen progression with additional aUEC.

Confirmed Crash Fix: Mission Markers

The one explicitly confirmed bug fix in this build is a client crash tied to applying mission markers. If you were experiencing shutdowns around mission tracking, this is one of the highest-priority fixes to verify.

Mission markers are a basic layer of usability for almost every profession. When they fail, the impact spreads across delivery work, bounty contracts, event objectives, and investigation gameplay. A crash tied to something so fundamental is exactly the sort of issue a stability-focused PTU needs to eliminate before release.

If this fix holds, it should help make contract chains more dependable and reduce the number of abandoned runs caused by technical failure rather than player error.

Potential Mission Fixes Players Should Actively Test

Most of the remaining changes in 4.10.2 PTU Wave 3 are still listed as potential fixes. In other words, they need real player verification.

Eliminate Specific Missions With Missing Targets

One major issue under review is the bug where no targets spawn during event Eliminate Specific missions. If this fix works broadly, it could also improve related frustrations in both ship and planetary bounty content.

Missing targets are one of the most damaging bugs for combat players because they waste travel time, fuel, and setup effort. For anyone who relies on bounty loops as a source of steady income, this is exactly the kind of problem that disrupts a reliable Star Citizen bounty hunting aUEC routine.

Scavenger Hunt Drop-Off Markers

Another potential fix addresses missing drop-off markers during the event Scavenger Hunt mission. Delivery and recovery objectives live or die by marker clarity, so this is a critical test point.

Even when the underlying mission works, poor marker behavior can make it feel broken. If the drop-off stage now tracks correctly, that should improve event flow and reduce needless mission abandonment.

Dumbwaiter Detection for Courier Objectives

The PTU also includes a potential fix for dumbwaiters at event locations not being detected by courier missions. This is a smaller issue on paper, but it directly blocks objective completion when it occurs.

Courier and interaction-based contracts often look simple, yet they become disproportionately frustrating when object detection fails. If CIG has resolved this properly, it should make support tasks within the event chain much smoother.

The event contract SCU request string now displays correctly. This is not a dramatic gameplay fix, but it improves readability and reduces confusion during logistics-focused objectives. In a game built around cargo values, quantities, and transport planning, even text clarity matters more than it might in other genres.

Two Standout Quality-of-Life Fixes

Bounty Mission Titles Now Show Target Ship Type

This is one of the best usability updates in the patch. Bounty mission titles now include the target ship type, which gives players valuable information before they commit to a contract.

That means less guesswork when choosing between a light fighter, a sturdier combat ship, or a group setup. It also helps players avoid taking a contract that their current ship cannot reasonably handle. Better pre-mission information saves repair costs, reduces failed runs, and improves route planning for combat-focused players.

For pilots trying to maximize earnings and reduce wasted sorties, this is a meaningful improvement to the overall Star Citizen reputation and aUEC loop. It lets you choose battles more intelligently instead of discovering too late that the target is far heavier than expected.

RSI Apollo Medical Module Collision

The other standout fix involves the RSI Apollo and its modular medical rooms. After installing tier 1 or tier 2 med bays, players often found those rooms behaving like incomplete shells, with collision issues that could cause clipping or falling through the ship.

If this fix is truly resolved, it is a major improvement for anyone interested in medical gameplay or future support-role progression. Modular ships only feel worthwhile when their modules function reliably, and the Apollo is too important a platform to leave in a broken state for long.

Drake Corsair Turret Power-Down Issue Fixed

Corsair owners also have a reason to pay attention to this PTU. A bug where turrets could power the ship down at the worst possible moment has reportedly been addressed, with radar priorities and display guarding added as part of the solution.

That should make multi-crew combat less erratic and reduce one of the stranger failure points affecting the ship. For players running group content, reliability like this matters almost as much as raw firepower. It also helps justify spending on larger platforms and supports the broader idea of aUEC for multi-crew ships being an investment rather than a gamble against bugs.

Known Issues Still Causing Trouble

Not everything is fixed in 4.10.2 PTU Wave 3, and players should go in with realistic expectations.

• Idris-T kit turret issues remain, including blank MFDs, non-functional gimbals, and missing missiles on some variants.
• QV station problems still include missing floor textures, inaccessible storage doors, and ships disappearing from pads.
• TSG bugs are still present.
• Greyed-out retrieve ship button remains one of the most annoying ongoing issues for many players.
• Escort ships in Foxwell missions may still fail to jump away correctly.
• MOTH filler station problems can still leave players stuck with the filling process in progress.
• MG scripts turned in to Wikelo may still disappear, making it safer to hold onto them for now.

These unresolved issues are important because they affect planning. If you are salvaging, hauling, or moving mission items, you still need to account for the possibility of technical loss. That kind of uncertainty is exactly why some players look for ways to reduce grind pressure, whether through efficient profession choice or options such as where to buy aUEC for Star Citizen without endless grinding when time is limited.

If you are logging into this Wave 3 build, focus your testing on the systems CIG is clearly targeting.

• Run multiple Stanton event contracts and watch for marker reliability.
• Check whether event rewards and reputation gains feel more proportional.
• Retrieve several ships from ASOP terminals and confirm correct power states.
• Test bounty missions and note whether target ship types are displayed consistently.
• Try Apollo medical modules if you own access to the ship.
• Report any mission-spawn failures, especially in elimination contracts.

PTU participation is most useful when players test repeatable gameplay loops rather than only trying a fix once. If a mission works three times and fails on the fourth, that is still valuable information. Consistency is the real target.

Why This Patch Matters for Everyday Progression

Although 4.10.2 PTU Wave 3 is not a content-heavy patch, it matters because it addresses friction in the core gameplay loop. Better ship retrieval, cleaner event progression, clearer bounty information, and fewer marker-related failures all contribute to a smoother Star Citizen experience.

That has a direct effect on progression. The less time players lose to broken contracts and technical setbacks, the easier it becomes to build toward larger goals such as cargo ships, combat upgrades, or role-specific loadouts. Whether your focus is combat, logistics, or support gameplay, stable systems preserve your time and your earning potential.

For players tracking long-term ship and component costs, every avoided bug is effectively saved value. In that sense, stability patches are not glamorous, but they are often the updates that do the most to protect your actual in-game momentum.

FAQ

Is the TTK rebalance active in 4.10.2 PTU Wave 3?

No. This PTU returns to normal weapon and shield behavior for now, so it is not the current combat rebalance test environment.

What should players focus on testing first?

Stanton event contracts, mission markers, target spawning, ship retrieval behavior, and bounty title ship-type displays are the biggest priorities.

Are event rewards better in this patch?

They have received a balance pass, especially around reputation progression. The goal appears to be making event rewards feel more proportional to the effort required.

It is still listed among ongoing issues. Some players report temporary workarounds through med beds, med pens, or server hopping.

Why does this patch matter for progression?

Because fewer bugs mean fewer wasted runs, fewer lost items, and more reliable income. That is valuable for any player managing ship costs, upgrades, and long-term credits and aUEC planning.