Loading...
Loading...
Community-submitted tips for avoiding and working around Star Citizen bugs.
Before every quantanium run: 1) Verify timer is working 2) Check that ship shields are at max 3) Have a direct route planned with no stops 4) Keep recording on. If the timer visual bugs, immediately head to the nearest refinery.
Do not wait until your cargo hold is full. Store salvage materials at the nearest station every 15-20 minutes. Server 30k events are unpredictable and will wipe unsaved progress.
The commodity duplication/deletion bug happens more during peak hours (6-10 PM UTC). If you must trade during peak, buy in small quantities and verify each purchase landed in your cargo before buying more.
Screenshot your aUEC balance before and after every trade. If a transaction bugs out, having before/after screenshots makes your MIC claim process much faster. Date and location visible helps too.
Open your cargo manifest (F1 → cargo) after every quantum jump. If it shows empty but you loaded cargo, do NOT land — log out to menu and relog. Sometimes the cargo reappears. If it does not, file your claim before landing.
Never refine more than 50 SCU at a time. The refinery bug that zeros out your output seems to happen more often with large jobs. Splitting into smaller batches takes longer but protects your investment.
Start recording (Alt+F9 in GeForce Experience or OBS) before engaging VHRT bounties. If the kill does not register, you have video proof for your MIC claim and the IC report.
Take a screenshot of your cargo manifest before each quantum jump. If your cargo disappears, this documentation will speed up your MIC claim significantly.
Server desync is more common during peak hours (6-10 PM UTC). Mining operations are especially vulnerable to desync-related losses. Schedule mining runs during off-peak hours if possible.
If you log out while your ship is deployed, there's a chance your cargo will be lost on next
login. Always store your ship at a station before logging out to prevent cargo loss.