Scenario File Options: Difference between revisions
imported>Tschachim m (link) |
imported>Lassombra |
||
Line 190: | Line 190: | ||
|- | |- | ||
|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. | |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. | ||
|} | |||
==Checklist Information== | |||
These values are defined between the lines <checklist> and </checklist> | |||
{|class="wikitable" | |||
!width = "100"|Option || Function | |||
|- | |||
|FILE || This is the file name of the checklist file to use. | |||
|- | |||
|AUTO || This defines whether to automatically execute the checklists. | |||
|} | |||
Additionally there are two items to define in the launch vehicle before the scenario starts. These are NOT defined between <checklist> and </checklist> | |||
{|class = "wikitable" | |||
!width = "100"|Option || Function | |||
|- | |||
|LEMCHECK || This is the file name of the checklist the LEM should use. | |||
|- | |||
|LEMCHECKAUTO || This defines whether the LEM should automatically execute the checklists. | |||
|} | |} | ||
Revision as of 15:09, 9 January 2008
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 CSM and LM call signs, various masses, fuel masses and other parameters.
Option | Function |
---|---|
TCP | Specifies the height of the rocket above the ground in meters prior to launch. This can be adjusted if the mission is flown from a different launch pad to the default for the spacecraft (e.g. the Skylab 'milk stool' for the Saturn 1b). |
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. Quickstart mode is level 0, Standard mode is level 5. |
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. |
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 (S-IC or S-IB). |
SIEMPTYMASS |
Specifies the empty mass in kilograms of the first stage (S-IC or S-IB). |
SICSHUT |
Specifies the mission time of center engine shutdown of the first stage (S-IC or S-IB). |
SISHUT |
Specifies the mission time of shutdown of the remaining engines of the first stage (S-IC or S-IB). |
SIIFUELMASS |
Specifies the mass in kilograms of the fuel in the second stage (S-IVB for Saturn 1B or S-II for Saturn V). This is not used for the INT-20. |
SIIEMPTYMASS |
Specifies the empty mass in kilograms of the second stage (S-IVB for Saturn 1B or S-II for Saturn V). This is not used for the INT-20. |
SIICSHUT |
Specifies the mission time of the center engine shutdown of the S-II stage of Saturn V and derivatives. |
SIIPUT |
Specifies the mission time of the PU-shift (change of mixture ratio) the second stage (S-IVB for Saturn 1B or S-II for Saturn V). |
SIISHUT |
Specifies the mission time of shutdown of the remaining engines of the S-II stage of Saturn V and derivatives. |
S4FUELMASS |
Specifies the mass in kilograms of the fuel in the S-IVB 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. |
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. |
ATTACHSTATE | Specifies which 'things' are attached to the spacecraft. This is a bit-field, created by combining the following values as appropriate.
Defaults are generally safe to use, but you may need to specify the value in the scenario for unusual missions (e.g. Apollo 5 with no LES or CSM and a nosecap uses 93). |
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.
This value is not saved in scenarios written out by orbiter, it is purely intended to allow you to set the docking probe state in initial scenarios without having to specify the full value for ATTACHSTATE. If you specify both HASPROBE and ATTACHSTATE in the same scenario, then whichever value comes second will be used for the docking probe state. |
SLASTATE | Specifies the state of the SLA panels on the SIVB. Bit 8 should be set to 1 if the panels are hinged, or 0 if they separate from the SIVB. Bits 0-7 specify the angle to which they will open if hinged, defaulting to 45 degrees with an upper limit of 150 degrees; if they're not hinged, they currently always separate at 45 degrees.
In most cases the default will work fine (hinged to 45 degrees on Saturn 1b, not hinged on Saturn V), but special missions may require manually setting this state. |
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. |
Mission parameter options
These are options specifying things such as the earth parking orbit parameters, lunar landing site, various mission time parameters 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. |
TLIMJD | Specifies the desired MJD of the TLI burn.I |
LOIMJD | Specifies the desired MJD of the first LOI burn.I |
FREERETURNPECMJD | Specifies the desired MJD of the free return pericynthion.I (currently unused) |
FREERETURNPECALT | Specifies the desired altitude (in meters) of the free return pericynthion.I (currently unused) |
TLIOFFSETLON | Specifies the longitude of desired target offset (in radian) of the TLI burn.I |
TLIOFFSETLAT | Specifies the latitude of desired target offset (in radian) of the TLI burn.I |
TLIOFFSETRAD | Specifies the radius of the desired target offset (in meters) of the TLI burn.I |
MOONMJD | Specifies the desired MJD of the lunar landing.I |
MOONBASE | Orbiter base name of the planned landing site on the Moon, if any.I |
MOONLAT | Latitude (in degrees) of the planned landing point on the Moon, if any. |
MOONLONG | Longitude (in degrees) of the planned landing point on the Moon, if any. |
MOONALT | Altitude (in meters) of the planned landing point on the Moon, if any. |
EARTHEIMJD | Specifies the desired MJD of the Earth landing entry interface, if any.I |
SPLASHLAT | Latitude (in degrees) of the planned splashdown site on the Earth, if any.I |
SPLASHLONG | Longitude (in degrees) of the planned splashdown site on the Earth, if any.I |
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.
CMPAD entries are used once to set up the values in the AGC when the scenario is loaded, then thrown away. So they will not be saved to a scenario file when you exit Orbiter. |
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. |
Checklist Information
These values are defined between the lines <checklist> and </checklist>
Option | Function |
---|---|
FILE | This is the file name of the checklist file to use. |
AUTO | This defines whether to automatically execute the checklists. |
Additionally there are two items to define in the launch vehicle before the scenario starts. These are NOT defined between <checklist> and </checklist>
Option | Function |
---|---|
LEMCHECK | This is the file name of the checklist the LEM should use. |
LEMCHECKAUTO | This defines whether the LEM should automatically execute the checklists. |
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. |
<biblio force=false>
#I This setting is automatically transferred to Interplanetary MFD (IMFD). #References </biblio>