Part of the Tips & FAQ Series:
- No Man's Sky Tips & Tricks Hub: Core principles (Start Here).
- Settings, Controls & Troubleshooting: Crashes, saves and input problems.
- Platforms & Versions Guide: What runs where.
Quick Answer
- The three settings that cost the most frames, in order, are Shadow Detail, Reflection Quality and Volumetric/Cloud Quality. Drop those three before touching anything else.
- Most No Man's Sky "lag" is not framerate — it is stutter, caused by shader compilation and terrain streaming. Fixing it is a different job from raising FPS.
- Big bases are the single largest self-inflicted performance cost. Part count matters more than any graphics setting.
- Cap your frame rate. A locked 60 feels dramatically better than an uncapped 45–90, and reduces motion discomfort.
- On Steam Deck, target 40 FPS with a 40 Hz refresh rate rather than 60. It is the difference between stable and miserable.
- Generation-heavy moments — landing, warping, entering the atmosphere — will stutter on almost any hardware. Some of that is the engine, not your PC.
Overview
No Man's Sky performance conversations go wrong because two different problems get called the same thing. "The game runs badly" usually means one of:
- Low average framerate — a graphics settings problem, solved by turning things down.
- Stutter and hitching on an otherwise fine framerate — a streaming and shader problem, largely not solved by turning things down.
The second is far more common and far more annoying, and most optimisation guides only address the first. This one separates them.
A note on scope: exact frame numbers depend entirely on your hardware, so this guide ranks settings by relative cost rather than promising "+15 FPS". Anyone quoting you a specific figure without naming a GPU is guessing.
Settings Ranked by Cost
Ordered by how much performance you get back per unit of visual loss.
| Setting | Cost | Recommendation |
|---|---|---|
| Shadow Detail | Very high | Drop to Standard. The visual difference in normal play is small; the frame cost is not. |
| Reflection Quality | Very high | Standard or off. Screen-space reflections are expensive and mostly visible on water and polished surfaces. |
| Volumetric / Cloud Quality | High | Standard. Enhanced clouds are beautiful from orbit and cost you frames constantly. |
| Anti-Aliasing | Moderate | Use TAA. On modern GPUs, prefer an upscaler set to Quality over native + heavy AA. |
| Terrain Tessellation | Moderate | Off unless you are photographing terrain. |
| Planet Quality | Moderate | Standard. Controls detail density on surfaces. |
| Texture Quality | Low, but VRAM-bound | Keep high if you have the VRAM. If you are VRAM-limited, this is the first thing that causes stutter, not low FPS. |
| Field of View | Low | Personal preference. Wider FoV renders more and costs a little. |
| Motion Blur | Low | Off — it hides frame instability rather than fixing it, and it is a common motion-sickness trigger. |
Upscaling. If your GPU supports DLSS, FSR or XeSS, use it at Quality rather than dropping settings further. No Man's Sky's art style survives upscaling well, and it is close to free performance.
Frame cap. Set a cap you can hold consistently — 60 on desktop, 40 on a handheld. Rather than leaving it uncapped. Consistency reads as smoothness far more than peak numbers do. This also helps with motion comfort.
Fixing Stutter (The Actual Problem)
Stutter in No Man's Sky comes from three places, and settings sliders only help with one of them.
1. Shader compilation. The first hour on a new driver or after a game update stutters as shaders compile. This resolves itself with play time. Do not rebuild your settings around it, play for an hour and re-evaluate.
Clearing the shader cache is worth understanding properly, because the advice cuts both ways. Clearing it forces a full rebuild, so your next session is worse, not better. That is the right trade only when the cache is genuinely stale or corrupt. After a driver change or a major patch, where stutter persists well beyond the first hour and is accompanied by visual corruption. If you are simply an hour into a new patch, wait rather than clearing. The troubleshooting guide covers cache clearing as a crash fix, which is the case where it genuinely earns the rebuild cost.
2. Terrain and asset streaming. Landing on a planet, exiting a space station, and pulse-flying between planets all force large streaming operations. This is the engine generating a world in real time, and it hitches on fast NVMe drives too. Installing on an SSD genuinely helps; installing on a mechanical drive is the single worst thing you can do to this game.
3. Your own base. Covered below, because it deserves its own section.
Two settings-level contributors worth checking:
- VRAM exhaustion presents as stutter, not low FPS. If Texture Quality is set beyond your card's VRAM, you get hitching. Drop textures one notch and see if the hitching stops before you touch anything else.
- Background applications. Overlays in particular. Interact badly with the game's streaming. If you have unexplained hitching, test with overlays disabled.
Bases Are the Biggest Performance Cost
This is the finding that surprises people: a large base will tank your framerate harder than any graphics setting.
Every placed part is drawn, lit and. If it is a powered or logic part. Simulated. The cost scales with part count, and it scales badly.
What to do about it:
- Prefer large parts over many small ones. One large room instead of nine small pieces is a real saving.
- Watch decorative part count. Decorations are the usual culprit in a base that has become unplayable.
- Power and logic circuits cost more than static parts. A base full of switches, sensors and wiring is simulating constantly. Consolidate where you can.
- Farms are expensive. Large agricultural setups with hundreds of plants are a common source of frame drops at a player's main base.
- Glitch-built structures are not free. Glitch building often means more parts occupying the same space, not fewer.
If your framerate is fine everywhere except home, the problem is home. This also applies to visiting other players' bases and to settlements, which generate their own part load.
Steam Deck Configuration
No Man's Sky runs well on Steam Deck if you stop trying to make it run at 60.
Target 40 FPS with the refresh rate set to 40 Hz. The Deck's display supports it, the frame pacing is even, and it is far more stable than an uncapped attempt at 60 that lands at 45 and fluctuates. This is the most important setting on the device.
A working starting configuration:
| Setting | Value |
|---|---|
| Refresh rate | 40 Hz |
| Frame limit | 40 FPS |
| TDP limit | 10–12 W |
| Resolution | Native (1280×800) |
| Upscaling | FSR, Quality |
| Shadow Detail | Standard |
| Reflection Quality | Standard or off |
| Volumetrics | Standard |
| Texture Quality | High |
| Anti-aliasing | TAA |
Additional notes:
- Install to internal storage if you can. microSD works, but streaming hitches are noticeably worse.
- Expect a stuttery first session while shaders compile, then improvement.
- Battery life at 40 FPS and a 10 W TDP cap is substantially better than an unlocked configuration, and the game looks the same.
- The game is Steam Deck Verified and the default controller layout is workable, though the settings guide covers rebinding if you want the inventory shortcuts closer to hand.
What You Cannot Fix
Worth stating so you stop chasing it:
- Warp and landing hitches happen on high-end hardware. The game is generating a solar system.
- First-visit stutter on a new planet is generation, not your settings.
- Multiplayer in a busy Anomaly is heavier than solo play and always will be.
- Very large bases have a floor. Past a certain part count, no setting rescues them, the fix is fewer parts.
FAQ
Which setting gives the biggest FPS gain?
Shadow Detail, followed by Reflection Quality and volumetrics. Dropping those three from maximum to Standard recovers more than any other change.
Why does my game stutter even at high FPS?
Almost always shader compilation (resolves with play time), asset streaming (helped by an SSD), or VRAM exhaustion from Texture Quality set too high. Low average FPS and stutter are different problems.
Does No Man's Sky run on Steam Deck?
Yes, and well. It is Steam Deck Verified. Target 40 FPS at a 40 Hz refresh rate rather than 60, cap TDP around 10–12 W, and use FSR on Quality.
Will a bigger base slow my game down?
Yes, significantly. Part count is one of the largest performance factors in the game, and decorative parts and powered logic circuits are the usual offenders.
Should I use motion blur?
No. It masks frame instability rather than fixing it and is a common motion-sickness trigger.
Does installing on an SSD help?
Materially, yes. The game streams terrain continuously, and a mechanical drive turns that into constant hitching.
Is uncapped framerate better?
No. A stable cap you can hold feels better than a fluctuating uncapped rate, and it is easier on motion-sensitive players.
Key Takeaways
- Drop Shadow Detail, Reflections and volumetrics first. They cost the most and show the least.
- Stutter ≠ low FPS. Shader compilation resolves itself, streaming wants an SSD, and VRAM overrun looks like hitching.
- Your base is probably the problem. Part count, decorations and powered logic circuits cost more than any slider.
- Cap the framerate. Stability beats peak numbers, and it helps motion comfort.
- On Steam Deck, 40 FPS at 40 Hz with a 10–12 W TDP cap is the configuration that works.
- Warp, landing and first-visit hitches are the engine generating a universe. Some of it is not yours to fix.