2-minute check
Is Star Citizen CPU or GPU bound? A 2-minute test
Run this when you are not sure whether lower resolution, different settings, or an upgrade will actually help. The goal is not a perfect diagnosis. The goal is the right next move.
Use referral code to start with 50,000.
Use it during signup. No price change — just the starter bonus.
Create account + claim bonus
Where to paste it New accounts only
Quick answer
Fast clue
Resolution change is the fastest clue. Big FPS jump usually points at the GPU. Little change usually points at the CPU, storage and RAM pressure, or a rough server.
- Run the same test twice before blaming the wrong part of your PC.
- If you’re CPU‑bound, lowering resolution won’t help much — you need CPU-friendly settings and smoother server/time choices.
- If you’re GPU‑bound, resolution and GPU-heavy settings are your main levers.
- This test is about direction: what to tweak first and what to ignore.
Run the 2-minute test
- Pick a repeatable test scene — Use the same location and camera angle for all tests.
- Run at your normal settings — Note how it feels (stutter vs steady low FPS).
- Drop resolution / enable upscaling — If FPS jumps a lot: likely GPU‑bound. If it barely moves: likely CPU‑bound.
- Lower CPU-heavy settings — Try shadows / crowd / draw distance style levers. If this helps: CPU‑bound signals.
- Choose next action — GPU‑bound → tweak resolution + GPU settings. CPU‑bound → tweak CPU settings + reduce background load.
Misreads to avoid
| Mistake | What happens | Fix (exact) |
|---|---|---|
| Testing different places each run | Different loads look like different bottlenecks. | Retest same scene. |
| Changing many settings at once | You can’t attribute the result. | Change one cluster per test. |
| Upgrading blindly | You spend money without knowing the limit. | Run the 2‑minute test first, then decide. |
FAQ
Can I see CPU/GPU usage instead?
You can, but in-game feel + resolution test is often enough to pick the right direction.
What if both feel bad?
Fix storage/RAM/pagefile first, then retest. Stutter can mask the true bottleneck.
Why does lowering resolution not help sometimes?
Because the CPU (or server load) is limiting frame production, not the GPU.
Should I upgrade CPU or GPU first?
Run the test. If resolution changes FPS a lot → GPU. If not → CPU or system bottleneck.
Where’s the full settings list?
Use the performance guide’s top-levers table and the simple next-step checks there.