BustedLoops
Loops health
← Latest Intel
ISSUEIroncladOperations SeatFlight Controls

Workaround

Ironclad operations seat cannot use jump or zoom after a Command Module handoff

Tracked since 21 Aug 2026 · Last researched 21 Aug 2026

Problem

Jump and zoom controls do not respond in the Ironclad operations seat after a Command Module flight handoff in Alpha 4.9.x LIVE.

This is the handoff-specific operations-seat state, not a general Ironclad docking, radar, quantum, power, or input failure.

Applies to Alpha 4.9.x LIVE · Current

Best current action

Switch an operations-seat mode with middle mouse

Click middle mouse to cycle the operations-seat mode, then check jump and zoom. This has not been independently reproduced.

Try this before redocking the Command Module; redocking is inconsistent and adds risk.

What to do

  1. While seated in the Ironclad operations seat, click the middle mouse button to cycle the available mode.
  2. Check whether jump and zoom controls return.
  3. Stop if the symptom is a different Ironclad control or docking failure.
Moderate SupportLow riskAlpha 4.9.x LIVE current community report; exact hotfix unresolved

Other options

Fly from the operations bridge seat

This checks whether the ship remains flyable through a different control path; it does not restore the lost jump or zoom controls.

Steps

  1. Enter the Ironclad operations bridge.
  2. Use the left operations pilot seat for flight.
  3. Treat the result as a control-path check, not a Command Module repair.
Best SupportedLow riskAlpha 4.9.x LIVE specialist guide; exact hotfix unresolved

What not to try

Undock and redock the Command Module

ContradictedMedium risk

Redocking can briefly reset a control conflict, but the failure can return and the extra docking step adds risk.

Related

Build status

The issue remains current in Alpha 4.9.x LIVE; no exact hotfix or official resolution is established.

Build not confirmed · Known Issue Continues · LIVE

Data sources

RSI Patch Notes · Reddit · Specialist Community