Scenario File Options: Difference between revisions
imported>Mark Grant No edit summary |
imported>Mark Grant No edit summary |
||
Line 23: | Line 23: | ||
|- | |- | ||
|FDAIDISABLED||Set to 1 to disable the OpenGL FDAI rendering. This can give a significant performance boost on slow machines. | |FDAIDISABLED||Set to 1 to disable the OpenGL FDAI rendering. This can give a significant performance boost on slow machines. | ||
|- | |||
|HASPROBE||Allows you to override the default docking probe state. Set to 1 if the spacecraft has a docking probe, or 0 if it doesn't. | |||
|- | |||
|MISSNTIME||Current mission time in seconds since launch. | |||
|- | |- | ||
|IGMST||Inertial Guidance Mode start: set to the time in seconds after launch at which the autopilot switches to inertial guidance mode and starts trying to hit the target orbit rather than follow the pre-planned pitch program. | |IGMST||Inertial Guidance Mode start: set to the time in seconds after launch at which the autopilot switches to inertial guidance mode and starts trying to hit the target orbit rather than follow the pre-planned pitch program. | ||
Line 40: | Line 44: | ||
|S4FUELMASS|| | |S4FUELMASS|| | ||
Specifies the mass in kilograms of the fuel in the SIVb stage of Saturn V and derivatives. | Specifies the mass in kilograms of the fuel in the SIVb stage of Saturn V and derivatives. | ||
|- | |||
|SMMASS||Empty mass of the Service Module, in kilograms. | |||
|- | |||
|CMMASS||Empty mass of the Command Module, in kilograms. | |||
|- | |- | ||
|S4PL|| | |S4PL|| | ||
Line 63: | Line 71: | ||
|- | |- | ||
|MOONALT||Altitude (in meters) of the planned landing site on the Moon, if any. | |MOONALT||Altitude (in meters) of the planned landing site on the Moon, if any. | ||
|- | |||
|LANDFAIL||Landing failures. Set to 1 to disable all random landing failures in your scenario, or 0 to create a random set of failures. | |||
|- | |||
|LAUNCHFAIL||Launch failures. Set to 1 to disable all random launch failures in your scenario, or 0 to create a random set of failures. | |||
|- | |||
|SWITCHFAIL||Switch failures. Set to 1 to disable all random switch failures in your scenario, or 0 to create a random set of failures. | |||
|- | |||
|UNMANNED||Set to 1 for an unmanned mission. | |||
|- | |||
|LEMN||Set to the LEM vessel name (e.g. Eagle for Apollo 11). This is the name the LEM will be given when it is created. | |||
|} | |} | ||
Revision as of 19:19, 31 October 2006
The Project Apollo scenarios have a vast number of options that you can specify. Some of the more useful are:
General options
These are options specifying things such as the fuel mass, the intended orbit after launch, etc.
Option | Function |
---|---|
TOAPO | Specifies the desired launch apogee altitude in kilometers. |
TOPER | Specifies the desired launch perigee altitude in kilometers. |
TOHDG | Specifies the desired launch azimuth in degrees. |
APOLLONO | Apollo mission number. This is used to provide mission-specific events such as mission audio or system failures. |
VECHNO | The Saturn vehicle number: typically this will be in the 200s for a Saturn 1b, and 500s for a Saturn V. This is used to name the separated stages and components of the spacecraft. |
REALISM | Sets the realism level from 0 (lowest) to 10 (highest). Lower realism level missions will be easier to fly. |
DLS | Set to 1 to delete the launch site when the spacecraft passes out of visible range. This can give a significant performance boost on slow machines. |
FDAIDISABLED | Set to 1 to disable the OpenGL FDAI rendering. This can give a significant performance boost on slow machines. |
HASPROBE | Allows you to override the default docking probe state. Set to 1 if the spacecraft has a docking probe, or 0 if it doesn't. |
MISSNTIME | Current mission time in seconds since launch. |
IGMST | Inertial Guidance Mode start: set to the time in seconds after launch at which the autopilot switches to inertial guidance mode and starts trying to hit the target orbit rather than follow the pre-planned pitch program. |
SIFUELMASS |
Specifies the mass in kilograms of the fuel in the first stage (SIc or SIb). |
SIEMPTYMASS |
Specifies the empty mass in kilograms of the first stage (SIc or SIb). |
SIIFUELMASS |
Specifies the mass in kilograms of the fuel in the second stage (SIVb for Saturn 1b or SII for Saturn V). This is not used for the INT-20. |
SIIEMPTYMASS |
Specifies the empty mass in kilograms of the second stage (SIVb for Saturn 1b or SII for Saturn V). This is not used for the INT-20. |
S4FUELMASS |
Specifies the mass in kilograms of the fuel in the SIVb stage of Saturn V and derivatives. |
SMMASS | Empty mass of the Service Module, in kilograms. |
CMMASS | Empty mass of the Command Module, in kilograms. |
S4PL |
Specifies the payload of the SIVb stage. Current values are:
|
AUTOSLOW | Set to 1 to slow to 1x time acceleration when 'something important' happens. For manned flights, this is typically when a piece of mission audio is played, for unmanned flights it is typically a stage separation, engine burn, etc. |
MOONLAT | Latitude (in degrees) of the planned landing site on the Moon, if any. |
MOONLONG | Longitude (in degrees) of the planned landing site on the Moon, if any. |
MOONALT | Altitude (in meters) of the planned landing site on the Moon, if any. |
LANDFAIL | Landing failures. Set to 1 to disable all random landing failures in your scenario, or 0 to create a random set of failures. |
LAUNCHFAIL | Launch failures. Set to 1 to disable all random launch failures in your scenario, or 0 to create a random set of failures. |
SWITCHFAIL | Switch failures. Set to 1 to disable all random switch failures in your scenario, or 0 to create a random set of failures. |
UNMANNED | Set to 1 for an unmanned mission. |
LEMN | Set to the LEM vessel name (e.g. Eagle for Apollo 11). This is the name the LEM will be given when it is created. |
Audio options
Option | Function |
---|---|
LANG | Set to the appropriate string for the audio language you want to use. Currently we only ship English audio, but if, say, you downloaded a French audio add-on you could set this to French instead and the French files would take precedence. |
AGC options
AGC options are specified between AGC_BEGIN and AGC_END. Options outside those lines will be ignored.
Option | Function |
---|---|
YAAGC | Set to 1 to use the Virtual AGC rather than the C++ AGC |
EMEM | Set an AGC erasable memory location to a specified value. Addresses and values are both specified in octal (base-8), so to set address 10 (decimal) to 17 (decimal) you would specify EMEM0012 21 . In general you should use LMPAD and CMPAD instead of specifying specific memory locations as both C++ AGC and Virtual AGC use the same scenario values to store different data.
|
Virtual AGC options
These options are set in the standard CSM configuration, not between the AGC_BEGIN and AGC_END lines. If you try to set them inside the AGC configuration they will be ignored.
Option | Function |
---|---|
CMPAD | Set a Virtual AGC erasable memory location in the CM AGC to a specified value. Addresses and values are both specified in octal (base-8), so to set address 10 (decimal) to 17 (decimal) you would specify EMEM0012 21 . If the scenario uses the C++ AGC rather than Virtual AGC, these values are ignored.
|
LMPAD | Set a Virtual AGC erasable memory location in the LM AGC to a specified value. Addresses and values are both specified in octal (base-8), so to set address 10 (decimal) to 17 (decimal) you would specify EMEM0012 21 . If the scenario uses the C++ AGC rather than Virtual AGC, these values are ignored.
Note that the LEM PAD is loaded when the LEM is created, so setting these values when the LEM already exists in the scenario will have no effect. |
LMPADCNT | Sets the number of LEM PAD entries. The LEM PAD is saved in a table until the LEM is created, so the DLL needs to know how large a table to create. Any values beyond this count will be ignored. |
Scenario information
These values aren't typically set in a newly created scenario, but are saved to the scenario from the DLL when exiting Orbiter.
Option | Function |
---|---|
NASSPVER | This gives the version number of the DLL which saved the scenario... for 7.0 it's 70000. |