Mouse and world interaction stop working after you log back in
Tracked since 30 Aug 2026 · Last researched 30 Aug 2026
Problem
After you log back into the Persistent Universe, the mouse may stop interacting with the game and several world controls can fail at once. Doors, kiosks, mobiGlas, and menu options may all become unusable.
CIG still lists this as a rare issue in 4.10.x LIVE. There is no working recovery at the moment, and Character Repair does not correct it.
Applies to Star Citizen Alpha 4.10.x LIVE (base client 4.10.0-LIVE.12519617; hotfix channel 12545750 observed through 2026-08-28) · Current
Current conclusion
No reliable fix is confirmed
Do not run Character Repair for this issue. Record what happened before the failure, especially how you previously logged out, and add it to STARC-212814 so CIG can investigate.
Diagnostic checks
These checks can identify the affected state, but they are not fixes.
Record what happened and report STARC-212814
CIG is asking affected players for the events leading up to the failure. Reporting will not restore your controls, but it is the only current action CIG recommends for this exact issue.
What to check
- Gather what you were doing before the issue appeared, including how you previously logged out.
- Add that information to Issue Council report STARC-212814.
What not to try
Do not use Character Repair for this issue
CIG says Character Repair will not restore the lost mouse and world interaction. The process cannot be stopped or reversed once it begins, returns your character to the spawn point, moves equipped gear into inventory, and does not restore items that were already missing.
Boundaries and evidence
Use this page only when interaction fails across several parts of the game after you have entered the PU. A stuck cursor, bad keybind, slow server response, one broken kiosk, or Error 41013 blocking the reconnect is a different problem.
No current player result was found that restores controls for this exact post-login failure, and we did not independently test a recovery.
The affected 4.10.x hotfix, exact trigger, duration, and fix date are not known.
The STARC-212814 report body is not publicly visible, so its full reproduction steps and contribution history could not be checked.
If Error 41013 stops you before you enter the PU, use the Error 41013 reconnect page instead.
Data sources
RSI Known Issues · RSI Support · RSI Status · Specialist Community
