FLIGHT MANUAL / 01 · START

Getting started

KMS installs into a legal KSP 1 copy. It never includes the game itself and never silently overwrites an unknown modification.

Requirements

Use the 64-bit Windows build of Kerbal Space Program 1.12.5. Keep at least 25 GB free on the drive that holds the game; the complete visual profile, build cache, backups, and logs can be large.

KMS is developed against a dedicated portable game copy. Steam is not required. A direct-store ZIP or clean installed copy is a valid source.

KEEP THE ORIGINAL CLEAN

Copy the clean game into a separate KMS folder. Do not turn your only known-good KSP installation into a beta test bed.

Prepare your game

  1. Exit KSP and confirm KSP_x64.exe is not running.
  2. Back up saves, craft, screenshots, and any custom flags you care about.
  3. Choose a short path on a roomy drive, such as D:\Games\KSP-KMS.
  4. Launch the clean copy once, reach the main menu, and exit. This proves the base game works before mods are introduced.

Install the beta

  1. Download the single KMS Installer executable from Beta Access after signing in.
  2. Run KMS-Installer-<version>-win-x64.exe and acknowledge the Windows unsigned-app warning.
  3. Choose the KSP root containing KSP_x64.exe and GameData.
  4. Review the embedded release, required official downloads, optional components, target drive, and preservation policy.
  5. Select Install / Update. KMS verifies, stages, backs up, commits, and writes a receipt automatically.
  6. Use Launch KSP or Open Docs when the success screen appears; retain the displayed backup path.
CLOSE KSP FIRST

The installer refuses to alter the selected copy while its KSP_x64.exe is running. Saves, craft, screenshots, and personal PluginData settings are not payload targets.

First launch checklist

  1. Start KSP normally and allow ModuleManager to rebuild its cache.
  2. At the main menu, confirm no fatal loading dialog is present.
  3. Open the KMS operations panel and review component health.
  4. Load a disposable sandbox save before opening an established career.
  5. Open local Mission Control only after the main menu or a flight scene is stable.
http://127.0.0.1:8085/telemachus/

Know the installation layout

KSP_x64.exe and GameData identify the game root. KMS-managed files live under GameData/KodyKSPSuite and other declared component paths. Transaction backups live outside GameData so ModuleManager never scans them.

The .kms folder contains the installation receipt and machine-local state. Saves remain under saves/<campaign>; the installer must never treat them as payload files.

Definition of a ready install

A ready install reaches the main menu without a fatal dialog, produces no repeating KMS exception, reports the expected component versions, loads a disposable vessel, and shows an offline-safe local Mission Control page.

A long mod list or a successful process start is not proof of readiness. Use the health panel and log baseline before moving a valuable career save.

Where to go next

Read Modules before choosing an optional profile. Read Troubleshooting before reporting a failure so the diagnostic bundle contains the right logs. Communications and Navigation explain how the constellation systems differ from stock CommNet.