Elite Dangerous: Best GraphicsConfiguration.xml for Deep Space

The primary goal for deep space optimization is to eliminate the “pixelated” look of the Milky Way and the “flat” appearance of planet surfaces during approach. The engine defaults to a 2048×2048 skybox, which can look grainy on modern 1440p or 4K monitors. We will be pushing this to 4096 or even 8192 and increasing the StarInstanceCount to make the galaxy feel as dense and awe-inspiring as it does in real life.

Hardware Compatibility & Expectations

  • VRAM Impact: Increasing texture sizes for the galaxy and planets primarily eats into your VRAM. 8GB+ VRAM is recommended for 4K textures, while 16384 (16K) textures for planets are strictly for high-end GPUs like the RTX 4080/5090.
  • CPU/Loading Times: Higher NebulasCount and StarInstanceCount will increase the loading time for “Witchspace” (hyperspace jumps), as the game must generate the new skybox for your destination system.
  • Atmospheric Clarity: These tweaks are particularly effective in Odyssey for improving the transition from space to thin atmospheres.

Backup and Preparation

It is highly recommended to use the Override file so your changes aren’t wiped by game updates.

  1. Completely exit Elite Dangerous.
  2. Navigate to your local AppData folder (path below).
  3. If GraphicsConfigurationOverride.xml doesn’t exist, create it with Notepad++.
  4. If you edit the main file, keep a copy named GraphicsConfiguration.xml.bak.

File Location

The Override file (recommended) is located here: %LocalAppData%\Frontier Developments\Elite Dangerous\Options\Graphics\GraphicsConfigurationOverride.xml

The Main config file (for reference) is usually here: Steam\steamapps\common\Elite Dangerous\Products\elite-dangerous-64\GraphicsConfiguration.xml

Best Config Settings for Deep Space Immersion

Paste the following into your GraphicsConfigurationOverride.xml to override the “Ultra” presets with enthusiast-grade values:

<?xml version="1.0" encoding="UTF-8" ?>
<GraphicsConfig>
    <Planets>
        <Ultra>
            <TextureSize>8192</TextureSize>
            <WorkPerFrame>512</WorkPerFrame>
        </Ultra>
    </Planets>
    <GalaxyBackground>
        <High>
            <TextureSize>4096</TextureSize>
            <NebulasCount>60</NebulasCount>
            <NebulasInBackgroundCount>80</NebulasInBackgroundCount>
        </High>
    </GalaxyBackground>
    <GalaxyMap>
        <High>
            <HighResNebulasCount>10</HighResNebulasCount>
            <LowResNebulaDimensions>128</LowResNebulaDimensions>
            <StarInstanceCount>128000</StarInstanceCount>
        </High>
    </GalaxyMap>
</GraphicsConfig>

Pro Tip: If the galaxy looks too “brown” and murky for your taste, you can add <MilkywayInstancesBrightness>0.5</MilkywayInstancesBrightness> to the GalaxyBackground section to dim the dust clouds and make the stars pop.

Key Parameters Explained

ParameterRecommended ValueImpact
GalaxyBackground > TextureSize4096Doubles the clarity of the Milky Way band and nebulae in the skybox.
Planets > TextureSize8192Dramatically sharpens planet surfaces during orbital flight and landing.
StarInstanceCount128000Increases the number of individual stars rendered in the background sky.
WorkPerFrame512Speeds up the rendering of terrain detail as you approach a planet.
NebulasCount60Renders more distant nebulae, making the deep space view feel “populated.”

In-Game Settings vs. Config

To complement your high-end deep space config, match these in-game Graphics settings:

  • Supersampling: Set to 1.0x if using DLDSR (Nvidia) or 1.25x for native. Avoid 2.0x as it is too taxing for minimal gain.
  • Anti-Aliasing: Set to SMAA. In Odyssey, TAA can be quite blurry; SMAA keeps the star fields crisp.
  • Ambient Occlusion: Set to Ultra. This adds vital depth to the craters and ridges of planetary surfaces.
  • Terrain Work: Move the slider to the far right. This works in tandem with the WorkPerFrame config edit.

Troubleshooting & Common Fixes

  • Long Hyperspace Jumps: If jumps take more than 20-30 seconds, your StarInstanceCount or TextureSize is too high for your hardware. Lower StarInstanceCount to 64000.
  • Stuttering Near Planets: This is often caused by WorkPerFrame being too high. Lower it to 256 if you experience frame drops during landing.
  • Settings Not Applying: Ensure you are using the correct XML syntax. The <GraphicsConfig> tag must wrap everything else. Check Read-only if the game keeps resetting your values.

Frequently Asked Questions (FAQ)

Does 8K (8192) Galaxy Background work?

The engine technically supports it, but many players report that it causes the game to crash or “hang” during jump transitions. 4096 is the most stable high-end sweet spot.

Why is my galaxy background so bright?

Frontier occasionally changes the lighting in updates. If the core looks like a white blob, use the MilkywayInstancesBrightness tweak (values between 0.3 and 0.7) to bring back the contrast.

Does this help with “Planet Pop-in”?

Yes. Increasing TextureSize to 8192 and WorkPerFrame to 512 forces the engine to start the high-detail rendering process much earlier, making the transition from orbit to surface much smoother.

Conclusion and Expected Results

By manually refining your GraphicsConfigurationOverride.xml, you are removing the technical “fog” that limits the beauty of the 1:1 scale Milky Way. You can expect razor-sharp nebulae, dense star fields, and dramatic planetary detail that truly rewards long-range exploration.

Leave a Comment