Framerate fails after opening and closing the starmap
Tracked since 16 Sept 2026 · Last researched 16 Sept 2026
Problem
Star Citizen cannot maintain normal FPS after you open and close the in-game starmap in 4.10.1.
The slowdown can leave you with less control during combat or any other moment that needs quick, precise input.
Applies to Alpha 4.10.1 LIVE · Current
Current conclusion
No reliable fix is confirmed
CIG still lists this problem for 4.10.1 and says there is no workaround. Generic performance steps are not a proven fix for this starmap-triggered drop.
Diagnostic checks
These checks can identify the affected state, but they are not fixes.
Report a current reproduction
A detailed Issue Council contribution can give CIG the current build, your setup, and a repeatable trigger. Reporting documents the bug; it does not restore framerate in your current session.
What to check
- Search the Issue Council for an existing report that matches the starmap-triggered FPS drop.
- Contribute to an open matching report, or create a new report if none exists.
- Select the current LIVE game version and add your setup, reproduction steps, frequency, and screenshots or video.
Include whether the drop happens after one starmap use or only after repeated opening and closing.
Related
Build status
4.10.1 still lists the starmap-triggered FPS drop as a known issue with no workaround.
Known Issue Continues · LIVE
Boundaries and evidence
Use this page when opening or closing the starmap triggers the slowdown. Low FPS that is already present before you use the starmap is a different problem.
CIG has not published the affected hardware or renderer range, the trigger threshold, frequency, root cause, or a fix date.
No current independent 4.10.1 test was found that restores FPS after this exact starmap trigger.
The exact Issue Council report and its reproduction details were not publicly inspectable.
The problem and any recovery were not independently tested.
Data sources
RSI Known Issues · RSI Status · Issue Council