Config File Options

Many options can be added to the config files to alter the way Project Apollo runs. When loading a scenario the Saturn V and Saturn 1b DLLs can read any scenario option from the config file and use it to set the default: so any option which isn't set in the scenario will use the value from the config file instead.

Examples of the more useful options to include:

TCP

TCP specifies the height of the rocket above the ground prior to launch. This is set to a default in the current config files, and it can be adjusted there if, say, you were to create your own launch pad addon which wasn't the same height as the standard ones.

SATTYPE

SATTYPE specifies the type of Saturn spacecraft the config file refers to. For example, the Saturn INT-20 config file uses the Saturn V DLL, but sets the SATTYPE variable to the correct value to indicate an INT-20.

Current values are:

1 Saturn V
2 Saturn 1b
3 Saturn 1 (not currently implemented)
4 Saturn INT-20


The long-term intention is to replace the Saturn V and Saturn 1b DLLs with one Saturn DLL which handles all variants and use the SATTYPE option to determine which is used for which configuration file.

SIENG

Specifies the number of active engines on the first stage of the spacecraft (max 8). For example, the INT-20 config file sets this to 4, but you could create a file for the 3- or 5-engine INT-20 variants by setting it to 3 or 5.

Note that if you set the engine number higher than the maximum number of engines on the stage it will be silently ignored.

SIIENG

Specifies the number of active engines on the second stage of the spacecraft (max 5).

SIIIENG

Specifies the number of active engines on the third stage of the spacecraft (max 1).

Other options

In theory, any of the Scenario File Options can be placed in the config file, but many make little sense there. Similarly, a number of these options make little sense in the scenario file except to override the defaults (e.g. setting TCP to a different value for the Skylab 'milk-stool' launches).