The “Clausewitz Engine” used by Stellaris struggles with the sheer volume of entities (ships, stations, and pops) in the 2400+ era. On the galaxy map, the game constantly renders dust clouds, nebula effects, and individual ship models that move between systems. By disabling these visual layers via the settings.txt and console, you can reduce the “Draw Call” overhead. This configuration is particularly effective for players on mid-range CPUs or those who prefer a “Performance Mode” aesthetic that mimics a clean tactical interface.
Hardware Compatibility & Expectations
- CPU Bottlenecks: Stellaris is heavily dependent on single-core clock speed. These tweaks help by reducing the work the main thread spends on UI and rendering tasks.
- Integrated Graphics / Laptops: Essential for making the galaxy map fluid when zooming in and out.
- Compatibility: Modifying
settings.txtis Ironman and Multiplayer compatible, as it does not change the game’s checksum.
Backup and Preparation
Ensure the game is closed before making these changes, as the launcher may overwrite the file if the game is running.
- Exit Stellaris.
- Navigate to the Paradox Interactive folder in your Documents.
- Right-click settings.txt, select Copy, and save a backup to your desktop.
- Open the original file with Notepad++.
File Location
Stellaris configuration is stored in the local user directory: C:\Users\%USERNAME%\Documents\Paradox Interactive\Stellaris\settings.txt
Best Config Settings
Search for these parameters in the graphics section of your settings.txt and set them to no or 0. These changes disable the most taxing planetary and map effects:
graphics={
size={
x=1920
y=1080
}
multi_sampling=0
vSync=no
shadows=no
reflections=no
bloom=no
tessellation=no
draw_sky=no
draw_water=no
draw_city=no
draw_trees=no
draw_postview=no
maxanisotropy=0
}
Pro Tip: To significantly boost galaxy map FPS, use the in-game console (
~key) and typetweakergui draw.dust borders.usemesh. Uncheck draw.dust to remove the nebula clouds that hog GPU resources.
Key Parameters Explained
| Parameter | Recommended Value | Impact |
| multi_sampling | 0 | Disables Anti-Aliasing; a major performance boost for the UI and map icons. |
| bloom | no | Removes the glow from stars and lasers, reducing the “shimmer” lag on the map. |
| draw_dust | Console Toggle | Disables the “Nebula Dust” layer. This can gain you up to 30+ FPS on the galaxy map. |
| vSync | no | Disables vertical sync; essential for reducing input lag in heavy late-game menus. |
| maxanisotropy | 0 | Disables texture filtering for star and planet surfaces to save VRAM. |
Advanced Strategy: Reducing Simulation Lag
While graphics tweaks fix the “stutter,” “Simulation Lag” (the slow days) requires specific game setup choices:
- Xeno-Compatibility: Always set to OFF. This prevents the creation of thousands of hybrid species that clog the game’s trait calculations.
- Habitable Worlds: Set to 0.25x. Fewer planets mean fewer pops, which is the #1 way to keep the late-game fast.
- Logistics Growth Ceiling: Higher values slow down pop growth as planets fill up, naturally capping the lag.
- L-Gates & Gateways: Set to 0 or Minimum. These create complex “shortest path” calculations for every ship in the galaxy.
Troubleshooting & Common Fixes
- Map Looks “Empty”: If the galaxy looks too bare after the dust tweak, re-enable
borders.usemeshin the tweakergui to see empire borders. - Stuttering when Paused: This is often caused by the “Outliner.” Closing individual sections (like “Fleets” or “Planets”) in the outliner can reduce frame-time spikes.
- Settings Resetting: If your
settings.txtchanges are ignored, right-click the file, go to Properties, and check Read-only.
Frequently Asked Questions (FAQ)
Does disabling 3D units work in Stellaris?
Unlike HOI4, there is no single draw_units toggle in the config. However, using the command debug_sky in the console can sometimes hide background elements to focus on the UI.
Why does the game lag more when I select a large fleet?
When a fleet is selected, the engine constantly recalculates its total “Fleet Power” and paths. Deselecting fleets and keeping the “Fleet Manager” closed helps significantly.
Does genocide actually help with lag?
Yes. In Stellaris, fewer pops = fewer daily job/ethics/resource calculations. Using a Colossus to “crack” worlds is a common (if ruthless) performance optimization strategy.
Conclusion and Expected Results
By manually refining your settings.txt and stripping away the galaxy map’s “visual noise,” you allow the engine to run more fluidly. You can expect sharper UI response, smoother zooming, and improved stability during the late-game crisis. The galaxy is now yours to command, without the 15 FPS penalty.