Scenario File Options - Revision history

Indy91: Explain APOLLONO vs MISSION parameter

2024-09-05T15:07:40Z

Explain APOLLONO vs MISSION parameter

← Older revision		Revision as of 15:07, 5 September 2024
Line 10:		Line 10:
	\|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).		\|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.		\|APOLLONO\|\|Apollo mission number. This is used to provide mission-specific systems and events such as mission audio or system failures. This has to be a numeric value and it will load the mission file from the Missions/ProjectApollo/ folder with the name "Apollo X.cfg", with X standing for the number after APOLLONO. If a non-numeric mission file is desired, use the MISSION parameter instead.
			\|-
			\|MISSION\|\|See APOLLONO. This parameter will load the mission file from the folder Missions/ProjectApollo with the name "X.cfg", with X standing for the file name specified after MISSION.
	\|-		\|-
	\|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.		\|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.

Thymo: Update purpose of NASSPVER

2022-09-07T21:04:19Z

Update purpose of NASSPVER

← Older revision		Revision as of 21:04, 7 September 2022
Line 348:		Line 348:

	==Scenario information==		==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.~~

	{\|class="wikitable"		{\|class="wikitable"
	!width="100"\|Option \|\| Function		!width="100"\|Option \|\| Function
	\|-		\|-
	\|NASSPVER\|\|~~This gives the~~ version ~~number~~ of the ~~DLL which saved the~~ scenario..~~. for 7.0 it's 70000~~.		\|NASSPVER\|\| The version of the current scenario file. The first two digits are reserved to indicate the current NASSP version. The remaining 3 digit number is incremented each time a breaking change is made to a scenario parameter.
	\|}		\|}

	~~<biblio force=false>~~
	~~#I This setting is automatically transferred to [http://koti.mbnet.fi/jarmonik/Orbiter.html Interplanetary MFD (IMFD)].~~
	~~#[[References]]~~
	~~</biblio>~~

	==See Also==		==See Also==

N72.75: remove some old AGC++ info

2022-09-03T11:51:32Z

remove some old AGC++ info

← Older revision		Revision as of 11:51, 3 September 2022
Line 114:		Line 114:
	\|PAYN\|\|Sets the payload vessel name (e.g. Eagle for the Apollo 11 LEM). This is the name the SIVB payload will be given when it is created; LEMN can be used as a synonym.		\|PAYN\|\|Sets the payload vessel name (e.g. Eagle for the Apollo 11 LEM). This is the name the SIVB payload will be given when it is created; LEMN can be used as a synonym.
	\|-		\|-
	\|~~MISSIONTRACKING~~\|\|Set to 1 to enable the ground and mission tracking of the [[Mission Control Center]]. This parameter is only used for initializing the MCC before launch and is not saved again in a scenario.		\|MCC_MT_Enabled\|\|Set to 1 to enable the ground and mission tracking of the [[Mission Control Center]]. This parameter is only used for initializing the MCC before launch and is not saved again in a scenario.
	\|}		\|}

Line 176:		Line 176:
	!width="100"\|Option \|\| Function		!width="100"\|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 <code>EMEM0012 21</code>. LMPAD and CMPAD should be used in prelaunch scenarios.
	\|-
	\|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 <code>EMEM0012 21</code>. ~~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~~.
	\|-		\|-
	\|}		\|}

imported>Indy91: More TLI parameters

2016-12-20T14:34:42Z

More TLI parameters

@@ Line 259: / Line 259: @@
 !width="100"|Option || Function
 |-
-|LVDC_ALFTSA||Desired angle between the S Vector (Nodal crossing of target ellipse and Earth Parking Orbit) and T (Unit Target) vector at restart preparation for first opportunity. (Constant across daily launch window.)
+|LVDC_ALFTSA||Desired angle between the S Vector (Nodal crossing of target ellipse and Earth Parking Orbit) and T (Unit Target) vector at restart preparation for first opportunity. (constant across daily launch window.)
 |-
-||LVDC_ALFTSB||Desired angle between the S Vector (Nodal crossing of target ellipse and Earth Parking Orbit) and T (Unit Target) vector at restart preparation for second opportunity. (Constant across daily launch window.)
+||LVDC_ALFTSB||Desired angle between the S Vector (Nodal crossing of target ellipse and Earth Parking Orbit) and T (Unit Target) vector at restart preparation for second opportunity. (constant across daily launch window.)
 |-
 |}

imported>Indy91: Add LVDC++ parameters to scenario file options page (still incomplete)

2016-12-20T13:54:11Z

Add LVDC++ parameters to scenario file options page (still incomplete)

@@ Line 198: / Line 198: @@
 |-
 |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.
 |}

imported>Indy91: Add information about MISSIONTRACKING scenario parameter

2016-11-22T19:20:19Z

Add information about MISSIONTRACKING scenario parameter

← Older revision		Revision as of 19:20, 22 November 2016
Line 113:		Line 113:
	\|-		\|-
	\|PAYN\|\|Sets the payload vessel name (e.g. Eagle for the Apollo 11 LEM). This is the name the SIVB payload will be given when it is created; LEMN can be used as a synonym.		\|PAYN\|\|Sets the payload vessel name (e.g. Eagle for the Apollo 11 LEM). This is the name the SIVB payload will be given when it is created; LEMN can be used as a synonym.
			\|-
			\|MISSIONTRACKING\|\|Set to 1 to enable the ground and mission tracking of the [[Mission Control Center]]. This parameter is only used for initializing the MCC before launch and is not saved again in a scenario.
	\|}		\|}

imported>Tschachim: example for SLASTATE

2009-04-09T13:04:25Z

example for SLASTATE

← Older revision		Revision as of 13:04, 9 April 2009
Line 108:		Line 108:
	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.		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.		\|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.		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. For example for hinged panels opening to 150 degrees use "SLASTATE 150" in the scenario.
	\|-		\|-
	\|PAYN\|\|Sets the payload vessel name (e.g. Eagle for the Apollo 11 LEM). This is the name the SIVB payload will be given when it is created; LEMN can be used as a synonym.		\|PAYN\|\|Sets the payload vessel name (e.g. Eagle for the Apollo 11 LEM). This is the name the SIVB payload will be given when it is created; LEMN can be used as a synonym.

imported>Tschachim: Removed Standard mode

2008-07-21T13:32:15Z

Removed Standard mode

← Older revision		Revision as of 13:32, 21 July 2008
Line 14:		Line 14:
	\|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.		\|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.		\|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, ''Virtual AGC 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.		\|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.

imported>Mark Grant: /* General options */ - LEMN -> PAYN

2008-01-17T01:48:57Z

General options: - LEMN -> PAYN

← Older revision		Revision as of 01:48, 17 January 2008
Line 112:		Line 112:
	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.		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.		\|PAYN\|\|Sets the payload vessel name (e.g. Eagle for the Apollo 11 LEM). This is the name the SIVB payload will be given when it is created; LEMN can be used as a synonym.
	\|}		\|}

imported>Mark Grant: /* General options */ LEM fuel mass.

2008-01-13T17:33:48Z

General options: LEM fuel mass.

← Older revision		Revision as of 17:33, 13 January 2008
Line 54:		Line 54:
	\|S4FUELMASS\|\|		\|S4FUELMASS\|\|
	Specifies the mass in kilograms of the fuel in the S-IVB stage of Saturn V and derivatives.		Specifies the mass in kilograms of the fuel in the S-IVB stage of Saturn V and derivatives.
			\|-
			\|LMASCFUEL\|\|
			Specifies the mass in kilograms of the fuel in the LEM ascent stage, if appropriate.
			\|-
			\|LMDSCFUEL\|\|
			Specifies the mass in kilograms of the fuel in the LEM descent stage, if appropriate.
	\|-		\|-
	\|SMMASS\|\|Empty mass of the Service Module, in kilograms.		\|SMMASS\|\|Empty mass of the Service Module, in kilograms.