Kerbal Space Program 2: Best settings.json for Interstellar Travel

The key to reaching another star system without your ship krakening is the Max Physics Delta-Time. In KSP2, if the physics simulation can’t keep up with the frame rate, the “game time” slows down. For interstellar vessels—which are often massive and part-heavy—you want to force the engine to prioritize simulation accuracy over smooth visuals.

File Path

You can find the global configuration file in your AppData directory. Unlike KSP1’s .cfg, this is a standard JSON file.

%USERPROFILE%\AppData\LocalLow\Intercept Games\Kerbal Space Program 2\Global\Settings.json

Technical Note: Before editing, ensure KSP2 is closed. After saving, you do not need to set this to Read-only, as the 2026 build respects manual JSON edits unless you hit “Reset to Defaults” in-game.

Optimized Settings.json Configuration

Open the file and search for the following keys. If they are missing, you can add them within the appropriate nested objects (usually under Graphics or Physics).

Parameter	Recommended Value	Technical Purpose
PhysicsDeltaTimeMax	0.02	Forces more physics steps per second; essential for preventing joint failure at $0.1c$.
ScatterState	false	Disables “Environment Props” (rocks/grass) that eat CPU cycles during planet-side launches.
MaxDebrisCount	0	Interstellar missions create stages; clearing debris instantly keeps the save file size low.
Antialiasing	0	KSP2’s internal AA is notoriously heavy; disable it to gain up to $15\%$ FPS on 4K.
CloudQuality	0	Clouds are the #1 GPU killer in KSP2. Set to Low/Off for high-altitude/interstellar stability.

{
  "Graphics": {
    "Antialiasing": 0,
    "ScatterState": false,
    "ScatterSystemSuspended": true,
    "CloudQuality": 0,
    "ReflectionRefreshRate": 0,
    "ScreenSpaceReflection": false
  },
  "Physics": {
    "PhysicsDeltaTimeMax": 0.02,
    "MaxDebrisCount": 0
  }
}

HowTo: Preparing for a 4.5 Light-Year Voyage

Follow these steps on GameEngineer.net to ensure your mission doesn’t end in a crash-to-desktop:

1. The “Physics Delta” Trade-off: Setting PhysicsDeltaTimeMax to 0.02 (or even 0.01 for massive ships) will make the game run in “slow motion” if your CPU struggles. However, it prevents the Kraken from shaking your ship apart during high-thrust burns.
2. Max Patches to Display: In the in-game Gameplay settings, set “Max Patches” to 1. This limits the orbital trajectory lines shown in the map view, which significantly boosts FPS when navigating complex star systems.
3. Unbreakable Joints: For interstellar “Megaships,” even the best settings won’t stop part-wobble. Use the “Stronger Struts” mod or enable “Unbreakable Joints” in the Cheat Menu (ALT+F12) to simulate the structural integrity required for relativistic speeds.
4. Clear the Log: KSP2 often writes “Null Reference Errors” to the Player.log. If your game slows down over a long session, delete the log file in the AppData folder to stop the OS from bottlenecking I/O.
5. Time Warp Logic: When traveling between stars, use “Stable Warp.” Avoid 4x Physics Warp while engines are running unless you have set your Delta-Time to 0.02 as shown above.

Technical Explanation: Physics Steps vs. Visual Frames

In the Enfusion-based architecture of KSP2, physics is calculated on a fixed timestep. If your PhysicsDeltaTimeMax is the default 0.04, the game allows the physics engine up to 40ms to calculate a frame before it “gives up” and moves to the next visual frame.

For an interstellar craft with 300+ parts moving at $30,000 \text{ km/s}$, a 40ms gap can result in parts clipping into each other, leading to a “Kraken” explosion. By tightening this to 0.02, you force the engine to calculate twice as many sub-steps. While this may lower your “visual” FPS, it ensures the mathematical model of your ship remains coherent, which is the difference between a successful arrival at Debdeb and a disintegrated cloud of debris in the void.