The primary goal for KSP 2 launch stability is Physics Load Reduction. Unlike KSP 1, the second game features much more aggressive “scatter” objects. This configuration focuses on disabling the environment props that do not have actual collisions but still consume CPU “ticks,” freeing up your processor to handle the actual structural integrity (struts and joints) of your rocket.
Hardware Compatibility & Expectations
- VRAM Intensive: KSP 2 requires significantly more VRAM than its predecessor. If you have 8GB or less, setting
TextureQualityto Low/Medium is mandatory to avoid “Stutter-Death” during staging. - CPU Single-Thread: Despite improvements, the physics for a single vessel are still largely calculated on one core. Higher GHz is better than more cores for launch stability.
- SSD Requirement: Launchpad transitions involve massive asset loads. Running KSP 2 on an HDD will cause “Scene Load” hangs that can result in your rocket spawning inside the ground.
File Location
The configuration file is not in the game’s root directory, but in your local AppData: %USERPROFILE%\AppData\LocalLow\Intercept Games\Kerbal Space Program 2\Global\Settings.json
Best Settings.json for Launch Stability
Open the file with Notepad and modify the following parameters. These specific “Scatter” tweaks are the most effective way to gain 10–15 FPS on the launchpad:
{
"Graphics": {
"ScatterState": false, // Disables Environment Props (The #1 FPS fix)
"ScatterSystemSuspended": true, // Prevents the system from "waking up" during launch
"ScatterDensity": 0, // Sets decorative density to zero
"CloudQuality": 0, // 0 = Low (Massive boost during atmospheric ascent)
"WaterQuality": 0, // 0 = Low (Reduces reflection lag near KSC)
"Antialiasing": 0, // AA is notoriously bugged; off is safer for FPS
"Vsync": 1, // Keeping VSync ON prevents physics jitter/vibration
"ShadowDetails": 1 // 1 = Low (Reduces the load of craft-on-pad shadows)
},
"Physics": {
"MaxPersistentDebris": 0 // Prevents the game from tracking old stages
}
}Pro Tip: If your rocket “wobbles” or explodes for no reason on the pad, ensure Vsync is enabled in the config. Without a frame cap, the physics engine can over-calculate, leading to “Phantom Forces” that rip large vessels apart.
Strategic Launch Optimization
To ensure your vessel survives the transition from VAB to the launchpad:
- The “Strut-Check”: KSP 2’s “Autostrut” is less reliable than KSP 1’s. Manually place physical struts between heavy fuel tanks.
- Throttle Management: Do not launch at 100% throttle if your TWR (Thrust-to-Weight Ratio) is above 2.0. High aerodynamic pressure at low altitudes is the leading cause of “mid-launch disassembly.”
- Avoid “Environment Draw Distance”: In the settings, keep this at Medium. Setting it to High forces the game to render the terrain of distant continents while you are still on the pad.
Essential Launchpad Stability Steps
| Action | Recommended Setting | Impact |
| Bypass Launcher | Run KSP2_x64.exe directly | Saves system RAM and reduces background CPU usage. |
| Clean Space Center | Set Debris to 0 | Stops the CPU from calculating physics for crashed stages near the KSC. |
| Physics Delta-Time | 0.03 – 0.04 | Slows down game-time to ensure the CPU can finish physics math before the next frame. |
| Fullscreen Mode | Exclusive Fullscreen | Reduces input lag and provides better GPU priority. |
Troubleshooting & Common Fixes
- The “Sideways Camera” Bug: This often happens when loading a workspace. If your camera is glitched, press the Home key to reset the view to its default orbital position.
- FPS Drops Below 10: This is usually a “Fuel Flow” calculation error. Minimize the number of fuel lines and use simpler tank-to-tank connections if possible.
- Game Won’t Start After Edit: If you make a syntax error in the
.json(like a missing comma), the game will crash. Delete theSettings.json, and a fresh one will be generated on the next launch.
Frequently Asked Questions (FAQ)
Does “ScatterState: false” remove trees?
Yes, it removes decorative rocks, trees, and grass. While the world looks “barer,” the performance gain is massive because the engine stops checking for collisions between your landing legs and every blade of grass.
Why is my FPS higher in orbit than on the pad?
In orbit, the game stops rendering “Terrain Shaders” and “Scatter.” The launchpad is the most demanding part of the game because it has to render the high-detail KSC buildings and the planetary surface simultaneously.
Will my KSP 1 settings work?
No. KSP 2 uses a completely different engine (Unity with custom rendering pipelines). Settings from the first game are not compatible and use different file extensions.
Conclusion and Expected Results
By manually forcing ScatterState to false and CloudQuality to Low in your Settings.json, you are stripping away the most inefficient decorative layers of KSP 2. You can expect a 15-25% FPS increase during liftoff, smoother transitions through the “Max-Q” aerodynamic phase, and significantly fewer physics-related crashes when launching heavy, multi-part payloads.