Star Citizen Carrier Bed Logout Bug: Docked Fighters Can Disappear

Returning to a carrier and finding its fighter missing is a miserable end to a shared session. Alpha 4.10.2’s known-issues guidance confirms a bed-logout problem affecting docked craft, with the Idris, Polaris and Tyilui specifically named.

The reported sequence is a bed logout aboard the larger ship, followed by the loss of a fighter docked with it. No workaround is currently listed. That leaves crews with a practical reason to reconsider ending a session with a valuable support craft still aboard.

Finish the sortie before the crew logs off

For now, our advice is to plan an ordinary return to port and deal with each ship separately before ending the evening. Treat that as a cautious way to avoid relying on carrier bed persistence, not a tested fix. It does not establish that every docking arrangement, ship or logout method is safe.

This is especially relevant when one player supplies the carrier and another brings the fighter. Agreeing where the smaller ship will finish its trip is less frustrating than discovering a missing craft when the group next meets. The carrier’s owner should not assume that everyone aboard is ready to log out just because the main objective is finished.

A missing craft does not mean a broken hangar-service feature

Repairing and rearming a ship inside a carrier is a different question from keeping that ship through a logout. Our ship hangar services guide covers the servicing side. It should not be read as a promise that a serviced craft will persist through this bug.

The official notice does not give a fixed build or a recovery guarantee. Until that changes, avoid treating a relog, a different bed or a character repair as a confirmed solution. We would rather finish the night at port than build the next session around an assumption that the fighter will still be there.