FLIGHT MANUAL / 10 · SUPPORT

Troubleshooting

Do not reinstall everything first. Preserve the failing state, collect evidence, and change one variable at a time.

Fatal loading errors

  1. Exit KSP and preserve KSP.log before another launch overwrites it.
  2. Capture Logs/ModuleManager/ModuleManager.log and ModuleManager.ConfigCache.
  3. Record the loading-screen file shown immediately before failure.
  4. Check duplicate assembly names and versioned dependencies.
  5. Run the KMS profile verifier before removing mods manually.

Crash or hang

Collect KSP.log, Player.log, crash folder if one exists, the save, affected craft, installed receipt, and approximate wall-clock time. A Windows 'not responding' state during initial database loading is not by itself a crash; a stopped process or crash dump is.

Repeated exceptions

A stack trace repeated every frame is a performance bug even if play continues. Note the first exception, its assembly, scene transition, and what object was being destroyed or replaced. Later copies are usually symptoms of the same missing guard.

STOP THE LOG STORM

After evidence is saved, exit the game. Continuing for hours can generate huge logs and hide the initiating event.

Comms and GNSS

Export link endpoints, route, per-hop margin/capacity, ground-station state, receiver-visible satellites, and power state. Report whether the problem affects one vessel, one body, one save, or every new sandbox craft.

Diagnostic bundle

A diagnostic bundle should redact usernames, absolute personal paths where practical, auth cookies, invitation tokens, and unrelated saves. It should contain hashes and manifests so support can reproduce the installed graph without redistributing your game.

Important evidence locations

<KSP root>/KSP.log
%USERPROFILE%/AppData/LocalLow/Squad/Kerbal Space Program/Player.log
<KSP root>/Logs/ModuleManager/ModuleManager.log
<KSP root>/GameData/ModuleManager.ConfigCache
<KSP root>/.kms/installed.json

Safe isolation process

Reproduce in a copied save, preserve logs, then disable the narrowest implicated KMS bridge or optional module. Do not randomly remove dependency folders from the live profile.

If the fault disappears, restore the module and reproduce once to distinguish causation from cache or timing changes. Record both runs.

A useful bug report

  1. State expected behavior and actual behavior in one sentence each.
  2. List exact actions from scene load to failure.
  3. Attach the installed receipt, fresh KSP.log, and affected save or craft when safe.
  4. Include screenshots only when they add UI or geometry evidence.
  5. Name the first exception and UTC time; do not paste thousands of repeated copies.