Alain Capt

A M S O

Apollo Mission Simulator for Orbiter

VERSION 1.21

This add-on is dedicated to my good friend Dennis Hare,

Alias "LazyD",

who left us too soon in November 2007.

This version of AMSO will run only with Orbiter 2010-P1, build 100606 to

build 101016. Any other Orbiter versions WON'T work (AMSO will abort).


!!! ATTENTION !!!

Because of AMSO mesh protection scheme, AMSO may not work properly

(scrambled meshes) with Orbiter server version "Orbiter_ng.exe".

It is the case, for example, with the sample graphic engine client: D3D7Client.dll.

On the other hand, this version of AMSO has been tested intensively with

D3D9Client.dll, version RC33, with good results.

CONTENTS
Foreword………………………………….………………………………… 04

Other Add-ons………………………………………………….…………… 06

Installation…………………………………………………...……………... 07

Uninstalling…………………………………………………………………. 08

Orbiter optimum setup for AMSO………..………………………………… 09

Anti-aliasing………………………………………………………………… 09

Launch tower and Pad-39A…………….…………………………………... 10

APOLLO and LM vessels vulnerability feature……………………………. 12

Usage………………………….……………………………………………. 13

"J" Action key………………………………………………………………. 13

"K" Alternate Action key………………………………….………………... 14

"M" focus toggle key…………………………...…………………………... 15

"NUMPAD ENTER" key…………………………………………………… 16

"CTRL-J" key……………………………………..………………………… 16

"CTRL-K" key……………………………………..……………………….. 16

"SHIFT-CTRL-I" key…………………..…………………………………... 16

"CTRL-L" / "SHIFT-L" / "SHIFT-CTRL-L" keys…………………………. 17

"CTRL-NUMPAD:5" / "SHIFT-CTRL-NUMPAD:5" keys……………….. 17

"TAB" keys………………………………………..………………………... 17

Virtual cockpits……………………………………………………………... 18

Particularities of pre-APOLLO 11 missions………………………………... 19

Time acceleration management…..………………………………………… 20

Autopilots…………………………………………………………………… 21

CSM autopilot computer functions………………………..……………….. 21

LM autopilot computer functions…………………………………………... 22

PDI operation (Moon landing) …………………………………………….. 22

ABORT / ABORT-STAGE………………………………………………… 24

ASCENT operation (rendezvous) ………………………………………….. 24

Pre-landing auxiliary functions…………………………………………….. 26

Abort lunar operations………………………………………….…………... 26

POST-ABORTS auxiliary functions……………………………...………… 26

FULL STACK MANOEUVER auxiliary function…………………………. 27

ERROR MESSAGES……………………………………………..………… 28

SIM bay instruments and activities…………………………….…………… 29

Moon landing sites scenery……………………………………….………… 31

Damages and failures………………………..……………………………… 32

Lunar EVA activities……………………………………………………….. 34

Working on the Moon………………………………………………………. 35

The four launch phase abort modes………………………………………… 39

Aerodynamic lift……………………………………………………………. 40

Recovery team……………………………………………………………… 41

How to pilot the SeaKing helicopter…………………………………….…. 41

Usage of ground camera…………………………………………….……… 42

Ground cameras presets…………………………………….………………. 44

Sound customization………………………………………………………... 45

Sound customization per mission…………………………………………... 47

Technical information………………………………………………………. 50

Specifications of Saturn V …………………………………….…………… 52

Specifications of Apollo vessel…………………………………….………. 53

Specifications of Apollo LM vessel………………………………………... 54

Specifications of earth parking orbit insertion……………………………... 55

KNOWN PROBLEMS…………………………………………….……….. 57

CREDITS…………………………………………………………………… 58

COPYRIGHT(S) …………………………………………………………… 60

FOREWORD

Welcome to the latest version of AMSO!

AMSO was the precursor of all Apollo mission simulations for Orbiter.
AMSO gives you the opportunity to understand and apply all principles of space navigation. It is the perfect platform to learn all about rocket technology and space navigation, by using standard Orbiter instruments and custom add-ons like "IMFD", "LTMFD", "TransX", etc., in the context of an Apollo mission.
AMSO is not rigid at all; you can fly a whole Apollo mission totally manually (which is a real challenge!). But you can also use a very accurate Earth orbit injection autopilot. The same for the Apollo & LM vessels, which are both equipped with a sophisticated autopilot computer, behaving just like in reality and was developed by "LazyD".
Thanks to the amazing work of Luis Teixeira, AMSO looks really beautiful. All vessels are textured and sometimes it’s easy to believe you’re seeing real NASA photography! Both virtual cockpits (the command module and the LM) contribute a lot to the immersion feeling. It is also a real pleasure to explore the Moon landing sites, with the beautiful realistic scenery Luis has created.
Thanks to the new mouse interface for generic MFD, included in Orbiter since version 060504, the absence of custom panels is no longer a handicap, especially for complex instruments like IMFD.
I focus my attention on reliability, simplicity and performance. For example, with AMSO you will see perfectly smooth staging animations. Thanks to the way AMSO manages meshes, you will get a good frame rate, even with the large Apollo vessel high resolution meshes.
Thanks to the keyboard interface, you are not forced to be in the cockpit for such a great event like the Apollo 3^rd stage separation. Just go to the outside view, press the action key and admire it !!!
You may activate the new Orbiter "Damage & failure simulation" option and get random failures of several kinds, including the Apollo 13 case.
All the launch sequences are dramatic and spectacular, including the Apollo 17 night launch, with the light bathed tower and spot lights everywhere. All the moving elements of the tower are animated and you will see the tremendous exhaust flames of the first stage rushing out on the two sides of Pad 39A until the rocket clears the tower.
You will experience a funny and quite realistic "moon-walk" during EVA activities, where you will have to deploy instruments on the Moon surface, collect rocks, use a drill to take an underground sample, and even drive the lunar Rover on later Apollo missions.
From Apollo 15 forward, during the early stages of the return trip to Earth, you will perform a space EVA to recover 2 film cassettes. Earlier, during the orbital period, you will open the SIM bay to deploy a sub-satellite and two magnetometer antennas.
After the final splashdown you may play the role of the recovery team and fly a SH3 SeaKing helicopter. Fly the helicopter over the capsule, and then lift the three astronauts onboard to bring them safely to the deck of the USS Hornet carrier for the welcome back ceremony.
And finally, if you’re are unlucky and die during a mission, a risk that cannot be excluded in such a dangerous activity, an Angel will bring your soul to the Paradise of the heroes of Space.

OTHER ADD-ONS

This version of AMSO is certified to work with the following add-ons:

- ORBITERSOUND version 3.5 or over if backwards compatible. This version of AMSO has many sound customizations. To benefit from them, you need to have this add-on installed. But this is not mandatory. AMSO is designed to work also without it. For more details read chapter, "SOUND CUSTOMIZATIONS".

• 
  IMFD version 5.5 or over if backward compatible. Thanks to a mutual collaboration, IMFD implements its own IPC (Inter-Process Communications) memory block to synchronize its GET time and read data from vessels, which allows several automatic presets in IMFD programs. You can now fly to the Moon, starting with a precise TLI burn and make precise MCC correction(s) by using the “Target Intercept” program in “offset mode” (see IMFD documentation). Thanks to the display of the angular offset with the planned landing site in the IMFD “Map” program, you will be able to aim for good alignment with landing site. Finally, the IMFD “Base Approach” program uses IPC data to preset the splash down. You have numerous AMSO scenarios for Apollo 11, 13 and 17, having “ready to burn” IMFD setup examples, which can help you to understand its functions better. In this document, refer to the chapter, “TECHNICAL INFORMATION” for all the orbital parameters which can be written into a scenario to help refine the navigation of AMSO internal programs, or external applications, like IMFD via the IPC.
  

- LunarTransferMFD version 1.4 or over if backward compatible. In the same way as with IMFD addon, LunarTransferMFD will synchronize with GET time. But this addon do not use any other IPC parameters, as described in chapter “TECHNICAL INFORMATION”.

INSTALLATION
If you install an upgrade package, please note that my upgrade packages always upgrades ANY versions since the last complete package version.
1) If you’re installing the full version, I recommend fully uninstalling any previous versions of AMSO. This will eliminate all obsolete unnecessary files. Refer to the previously installed version’s documentation file, under the chapter "UNINSTALLATION" to do this correctly.
2) Unzip this archive, with the option "use folder names" ON, into your Orbiter root directory (if you use Windows unzip wizard, don't worry about this option, it is selected by default).
Don't worry, it will NOT conflict with ANY other add-ons you might have installed, or erase original Orbiter files. All the material will be placed into "AMSO" private directories, except some Moon texture tiles used for the landing sites.

REMARKS: Because the implementation structure of AMSO in Orbiter changed with the 1.10 version, ALL Scenarios you may have created yourself before this version ARE INCOMPATIBLE. But you can make them compatible again with the following correction: replace all text occurrences "AMSO_" by "AMSO\". This can be done very easily with any text editor (ctrl-H).

For scenarios made with version 1.11 and over, there are, in principle, no dangerous incompatibilities. You shouldn't normally experience bad problems, like crash to desktop. What may occur, depending on the situation depicted by the scenario, are some minor anomalies due to some missing parameters. For example, you won't hear further ATC sounds for scenarios saved during (not before) PDI lunar landing or LM ascent stage Moon orbit injection.
ATTENTION !!! Some instruments’ modules are NOT compatible with AMSO. If you have a problem, like the Saturn V laying horizontally on the launch pad, or you experience numerous crash to desktop events, PLEASE DEACTIVATE ALL THE INSTRUMENT’ MODULES WHICH ARE NOT CERTIFIED FOR AMSO (see previous chapter).
ATTENTION !!! If you have the "CamShake" plugin addon, don't activate it. This functionality is included in AMSO.

UNINSTALLATION

To uninstall this add-on, just remove the following directories:

Orbiter\Config\AMSO

Orbiter\Config\vessels\AMSO

Orbiter\Config\Earth\base\AMSO

Orbiter\Config\Moon\base\AMSO

Orbiter\Doc\AMSO

Orbiter\Meshes\AMSO

Orbiter\Modules\AMSO

Orbiter\Scenarios\AMSO

Orbiter\Sound\AMSO

Orbiter\Textures\AMSO

And the following tile files in directory Orbiter\Textures\:
Moon_0_E0043_N0028.dds Moon_1_E0010_N0074.dds

Moon_0_W0029_N0013.dds Moon_1_E0044_S0026.dds

Moon_0_W0029_N0014.dds Moon_2_W0100_S0021.dds

Moon_0_W0079_N0020.dds Moon_3_W0267_S0035.dds

Moon_0_W0080_N0020.dds Moon_4_E0533_N0015.dds

ORBITER OPTIMUM SETUP FOR AMSO

Complex flight model: This option MUST be on.

Damage & failure simulation: Activate this feature if you want to have AMSO damage & failure simulation. For more details, see the chapter "DAMAGE AND FAILURES".

Limited fuel: This option MUST be on.

Non-spherical gravity sources: AMSO is not sensitive to this feature. So the setting of this option is irrelevant.

Radiation pressure: AMSO is not sensitive to this feature. So the setting of this option is irrelevant.

Gravity-gradient torque: Earth orbit injection autopilot trajectory precision is affected if this option is on. So it is better to turn it off. Note that if you set it on, the autopilot will still be able to build orbit but not in the most optimum way.

Particle stream: MUST be on, otherwise you will miss the best of AMSO visual effects. All other visual effects are also strongly recommended, but not mandatory.

Ambient light level: In the range 15 to 30.
REMARK: If like me, in full screen mode only, you are suffering of text display flickers with your ATI Radeon graphic card (textes like the white display line on the bottom, AMSO GET display, AMSO online help display, etc…), please activate the new Orbiter option "Disable hardware pageflip" on Orbiter "Video page".

ANTI-ALIASING

For all aspects of Orbiter, I highly recommend activating the anti-aliasing feature of your graphics card by using the adequate tool (most modern graphics card driver setup programs allow building a custom parameterization setup for a given executable). Consult the documentation of your graphics card driver for more details.

LAUNCH TOWER AND PAD-39A

The Launch tower will first appear in the pre-launch configuration. The first time you press "J", the tower will turn to launch configuration with animations of all moving parts, like the crane, the crew gate, etc. During countdown and liftoff, all umbilical and tail service masts will retract in sequence, like in reality. You will see flames coming out from both side of the tower; ice plates, detached by vibrations, fall down while condensation appears around the extremely cold fuel tanks, no longer isolated by the ice. At night, you will have all spots lit. Lights switch on and off automatically at dusk and dawn (correct switching only in winter).

When you load a launch scenario, you will be 5 minutes 30 seconds before liftoff. The Saturn V and the launch tower are in pre-launch configuration. When you press the “J” Action Key, the configuration will turn to minus 5 minutes (full retraction of white chamber arm). This is why you would be advised to do this at the right time. Now you will see vapor escaping the rocket during the tanks’ pressurization. If soon after you’ve pressed the "J" Action Key, you start to hear the countdown comments of the speaker, it means you have a sound pack extension installed, which includes the pre-launch sound option. In this case, you have nothing more to do, just enjoy the liftoff. If you just hear the wind and maybe some random ATC sounds, then when the vapors have smoothly disappeared, you will be close to the final countdown sequence and you must press the “K” Alternate Action key precisely at minus 10 seconds to start the final countdown.
This whole scenery feature can be deactivated, for example, if you want to use AMSO with another tower and launch pad. See below for how to do this.
How to work the launch tower option, technically speaking
If you look carefully at the Apollo ship definition in the scenario files, you will note that the following parameter line exists:
LAUNCHTOWER 1
If you remove this line, or replace "1" by "0", AMSO will not include the launch tower and the custom pad 39A. It is as simple as that!
To remove it from existing scenarios, you will have to edit all AMSO launch scenarios and other scenarios you may have created yourself, where the Saturn V still flies with the first stage. First remove or deactivate the "LAUNCHTOWER" parameter of Apollo vessel as in the example above.
Then you must check if the scenario also has the "ship" LaunchTower defined. This will be something like:
AS-506_LaunchTower:AMSO\LaunchTower

….

END

If found, you must also delete ALL these sections.
You don't need to check scenario files "far from cape Canaveral", because the launch tower and the custom pad 39A self delete when the central engine of the first stage stops burning shortly before separation of this stage.
ATTENTION!!! For my Launch scenarios to work properly, you MUST HAVE in the configuration file "canaveral.cfg" (located in "Config\Earth\Base\AMSO) my LPAD2 object or another LPAD object defined as the FIRST LPAD object into the list.

APOLLO AND LM VESSELS VULNERABILITY FEATURE

These two inhabited vessels are vulnerable. Impact with the ground, or entering into the Earth’s atmosphere and creating too high of a dynamic pressure will lead to immediate vessel destruction.

Death of the poor astronauts is simulated with a mystical eye candy - the "Angel to Paradise". As soon as the vessel’s destroyed, the focus will be set to a giant "Angel vessel" which will always be created somewhere on planet Earth, pointed toward the sun, and will "lift off" at a fantastic speed acceleration of 10 Gs. Soon he will be surrounded by a beautiful plasma halo. You can read on the screen "REQUIESCAT IN PACE" and you will hear the piece of music "Marche funèbre" of Frederic Chopin. Note that depending on the OrbiterSound mp3 player setting, you may hear one of your own music pieces instead (see chapter KNOWN PROBLEMS for more details).
Even if you are in the cockpit, the Angel will be with you, but for the full spectacle, switch to the outside view. The rapid climb of the Angel straight up over our planet can be really outstanding!!! Try this test: load the Apollo 11 launch scenario and don't change anything to the view settings. Set full thrust with your joystick for 4-5 seconds and then cut the throttle to crash Saturn V. During the Angel’s climb use "ctrl-up/down" keys or the mouse to adapt the view angle. Near the end of the music, you should see a beautiful Earth view, with Europe on your right.
The admissible dynamic pressure for the thermal shield configuration is 250 kPa (about -12,5 G) and without is 35 kPa. Be aware that for high altitude aborts, with or without the escape tower, if you cannot build an orbit with the CSM main engine, it might be MANDATORY to maneuver the CM during the atmospheric entry, to get maximum aerodynamic lift, in order to keep dynamic pressure within an admissible range and survive. See chapters "THE FOUR LAUNCH PHASE ABORT MODES" & "AERODYNAMIC LIFT" for more details.
For the CM splashdown, the admissible impact survival speed: horizontal speed in both axes +-8 m/s and vertical speed -12 m/s.
For the LM landing the admissible impact survival speed: horizontal speed in both axes +-2 m/s and vertical speed -4 m/s.
This feature can be disabled. In order to disable this feature, please read the chapter "TECHNICAL INFORMATION".

USAGE

Upon opening Orbiter, you will find a new scenario folder called "AMSO". This folder itself contains other folders, where you will find all required scenarios to play with AMSO. The scenario’s comments give you clues on what to do at each stage.

AMSO’s usage is simple. It involves mainly only three keys:
- "J" key, called "Action" key.

- "K" key, called "Alternate Action" key.

- "M" key, called "Focus Toggle" key.
Both "Action" keys are used to trigger all events and to select a menu interface when available. The result simply depends on the actual situation context. It is the same kind of interface philosophy you can see, for example, on most digital watches.
--------------- "J" Action key:
The very first time you press the "J" action key, the launch tower arms will retract (assuming this feature is not disabled – see previous section). From this point forward, until your Saturn V stack has jettisoned the 1^st and 2^nd stages, pressing the “J” key again will trigger the appropriate “abort” sequence. Note that you will need to confirm this action by pressing once more the “J” key (or the "K" key, if you have 2 abort choices), while the message “ABORT FLIGHT?” is displayed.
When the mission has progressed to the 3rd stage, and Apollo CSM, the “J” Action key will separate the Apollo vessel from the 3rd stage (however, main engines must be stopped for this command to be accepted).
For the undocking operation, simply use the standard "CRTL-D" key to undock. For example, this means that when you have docked with the LM parked into the 3rd stage, if you press "CTRL-D", you will simply undock. When you decide to extract the LEM from the 3rd stage you must use the “J” Action key instead. Note that 8 minutes after LM extraction, the 3rd stage will maneuver and perform a main engine burn to modify its own orbit. In early missions (until Apollo 12), this is a prograde burn of the rest of the fuel which will put the 3rd stage into a solar orbit. Apollo 13 forward, the 3^rd stage will maneuver in order to impact the Moon, as it was performed in the reality.
When you are in CSM configuration and docked with a complete LM, this key will separate Apollo service module (if the LM is activated), or do a definitive undocking from the LM (if the LM is deactivated). This command allow you to simulate Apollo 13’s dramatic flight!
When you are docked with the LM ascent module, this key will execute the definitive undocking from LM ascent stage (no docking mechanism). This means that docking with LM ascent stage is no longer possible. The LM Ascent stage will then initiate some automatic maneuvers to de-orbit and crash onto the Moon.
As long as you are docked with the CSM in the LM vessel, this key allows you to toggle LM activation.
Attention! You MUST activate the LM before undocking! Then, if you are not landed on the Moon, this key will separate the descent stage. The ascent stage engine will also be fired (abort manual landing) only if you are not too close to the CSM (i.e., less than 5 km). Notice that in any case (manual flight or with autopilot) when the descent stage runs out of fuel, the ascent stage will immediately separate and fire its engine (automatic ABORT-STAGE). Finally, when you are back with the ascent stage, and docked to the CSM, this key will allow you to definitively leave the LM and close the tunnel hatch between the two vessels.
When the LM autopilot is running PDI programs (lunar landing), you can use this key to say to the autopilot to abort the landing. It will toggle a little menu to select between the simple "ABORT" (LM simply stops landing and tries to regain orbit) or "ABORT-STAGE" (LM ascent separates and attempts to regain orbit). Use the "left" or "right" arrow key to select the desired mode and use "up" key to execute the command.
When you are landed on the Moon and the crew is back in the LM, the first time you press the “J” Action key it will activate the "lift off preparation" mode. If you press this key again, you will trigger an immediate lift off, WITHOUT autopilot.
Finally, when you are close to reentry in Earth atmosphere, this key will separate the service module. The service module will automatically initiate a maneuver to create a reentry path that’s different than yours in order to move out of the vicinity of your command module.
During EVA activities, the “J” Action key will allow almost all actions. For example, taking an object from the LM, depositing this object on the Moon’s surface, climbing onto the Lunar rover, etc.. For more details, please see the latter chapter entitled, "LUNAR EVA ACTIVITIES".
--------------- "K" Alternate Action key:
Before the Saturn V launch, at 10 seconds before liftoff, you can use the "K" key to initiate the launch with accompanying audio countdown (if OrbiterSound is installed) and the autopilot activated (see following).
In orbit, the “K” Action key will you to toggle the commands menu of both the Apollo vessel (CSM) and the LM. (ATTENTION: ‘toggle’ means you must close the menu manually, except in the case of having activated a program). While in orbit, obviously the LM must already have been activated in order for the menu to work.
On the lunar surface, the LM’s commands menu cannot be activated before activating the "lift off preparation" mode. When a menu is open you can use either the "left" or "right" arrow keys to select a menu item and the "up" arrow key to execute the selected command.
During the execution of autopilot programs, this key allows disengagement of the autopilot. You will have to confirm this action by pressing the "up" arrow key. Notice that in most cases, you won't be able to re-engage an aborted program, especially if you attempt it when the process of the program is already running for some time. So use this command with caution!
Notice also that if you are not in orbit around Earth or the Moon, you won’t be able to access the autopilot commands in the menu. Sorry to those of you who might have had the idea to try the LM elsewhere!!! In a more general way, you should never be able to access a menu which has no meaning in the actual context you are currently in.
When landed on the Moon and before you enter into "lift off preparation" mode, this key will allow you to start the EVA activities.
During EVA, this key will allow to use the drill tool, to deploy the Lunar Rover, or when both astronauts are on board of the Lunar Rover, to disembark the astronaut #2 first. Combined with "CTRL" key, it will allow you to "cheat", by killing all remaining rock samples, so you don't have to search for them in order to go to next EVA station.
--------------- "M" focus toggle key:
As soon as you have both CSM and LEM vessels, you can use the "M" focus toggle key to switch the Orbiter focus from one vessel to the other one.
During EVA activities, this key will toggle focus between crewmembers (if they are both outside the LM), or between the astronaut and the LM when only one astronaut is performing the EVA.
During entry into the atmosphere, and after the parachute protection cone is jettisoned, this key will allow you to toggle the focus between the CM and the USS-Hornet carrier. But this will be possible only if the carrier is waiting for you. It won't be the case if you had to abort your flight.
To set the focus on other vessels which have finished their duty, use the Orbiter set focus function.
--------------- "NUMPAD ENTER" key:
In flying vessels, you can use the "ENTER" key on the numeric keypad, to toggle the main power throttle between 100% and 0%, at any time when flying. In CM vessel only, toggle ON/OFF the AOA-180-LOCK autopilot, used for atmospheric re-entry.
Before Earth lift off, this key will start an immediate launch with the autopilot activated. When the LM is on the Moon’s surface (if both astronauts are back inside the LM), this key will initiate an immediate ABORT LUNAR OPERATIONS and immediately lift off with the autopilot (see chapter "AUTOPILOT" for more details).
For Astronaut walking or Lunar Rover driving, this key allows you to lock/unlock the present steering command. See also chapter “LUNAR EVA ACTIVITIES”.
--------------- "CTRL-J" key:
In any vessel, this command allows you to toggle the “Online Help” feature ON/OFF. It displays, in any view, the actual effects of both main “J” and “K” command keys. This feature is dynamic, so the display will change automatically with the evolution of the vessel’s context.
--------------- "CTRL-K" key:
In both Apollo and LM vessels, this command allows you to "kill" the ATC sounds synchronized on the GET (Ground Elapsed Time). All ATC sounds synchronized to specific events (LM PDI lunar landing, LM ascent to Moon orbit) are not affected. This deactivation is not saved on exit, so you may need to redo it on reloading.
In Astronauts "vessels" during LEVA, this command allows you to cheat with rock samples collection. All remaining rocks of the active EVA station will be removed and the next EVA station will be activated.
--------------- "SHIFT-CTRL-I" key:
This command allow you to toggle ON/OFF the display of the white information’s line on bottom left and the GET (Ground Elapsed Time) on upper right of the screen. The GET display starts at liftoff and will terminate counting upon splashdown. This function is useful both in taking pictures or videos. Use the “I” command to hide Orbiter information lines. Note that the menu display and malfunction alarms are not effected.
--------------- "CTRL-L" / "SHIFT-L" / "SHIFT-CTRL-L" keys:
In both the LM and Apollo CSM/CM vessels, the "Ctrl-L" key combination allows you to toggle ON/OFF the position/re-entry beacon light(s). In Lunar Rover, "Ctrl-L" control the thermal mirrors covers of the forward batteries pack. For all the Astronauts, these key combinations allow you to control the helmet protective visors:
- Ctrl-L control the main "gold" transparent visor.

- Shift-L control the lateral opaque visor (if it exists).

- Shift-Ctrl- L control the frontal opaque visor (if it exists).
These commands are not independent, and a logic is implemented to recreate the reality. For example, if you have all visors deployed and you simply press "Ctrl-L", you will not only retract the gold visor, but ALL visors, because both lateral and frontal visors will be retracted by the gold visor as it would be in reality.
--------------- "CTRL-NUMPAD:5" / "SHIFT-CTRL-NUMPAD:5" keys:
These key combinations allow you to activate a vessel’s relative KILL-LIN function in both the Apollo and Lunar Module vessels in order to facilitate docking operations.
This function is only available when the vessel is in LINEAR translation mode and no programs are running. Obviously both vessels must also exist. The command is also rejected if any of the 3 relative linear translation speeds between vessels are greater than 5 meters per second. A message, in the left-down corner of the screen, displays which function is active during the entire time the function operates.
- Ctrl-NumPad5: this command will produce a KILL-LIN-LATERAL which will not affect the mutual vessel’s closing speed.
- Shift-Ctrl-NumPad5: This command will produce a KILL-LIN-ALL function.
For convenience, these commands are also recognized for the Astronaut during Space EVA activities, but both commands will produce a KILL-LIN-ALL.
--------------- "TAB" keys:
This key allows you to toggle the contextual "Mini panel" in both the Apollo and LM vessels. The "Mini panel" display on the upper-left corner of the screen (in virtual cockpits only) displays a collection of useful data. The information displayed will vary according to the context of the state of the mission.

And finally, if you like a very big challenge, with AMSO you can still put full throttle on your joystick and see if you can manually put this "baby" into Earth’s parking orbit, with the correct azimuth and enough fuel remaining to continue the mission!!!

Be curious and have a look on the "life" of all parts after they have been jettisoned. AMSO simulates ALL the parts “life,” until they hit the ground. For this purpose, use the F4 key and "Select ship" option.

VIRTUAL COCKPITS

You use the standard F8 Orbiter key command to access the virtual cockpit. You can aim the camera in all directions with the mouse right button pressed continuously. Both cockpits have different camera positions, and you can obtain them with the standard Orbiter “Ctrl + Alt + arrow keys” commands. The “arrow down” command resets to the default position, while other arrows select an the other positions. In the CSM virtual cockpit, you use the “arrow up” position for visual docking. IMPORTANT!!! If with Orbiter 2006, it was possible to attempt a visual docking from the 2d cockpit too, it is NOT ANYMORE POSSIBLE with Orbiter 2010, because the 3d cockpit camera position IS NOT PRESERVED when switching from 3d to 2d cockpits.

The 3 other commands put the camera on all 3 astronauts’ seat positions. In the LM virtual cockpit, the default camera position (“arrow down”) is set for the approach and “TARGET CHANGE” feature. As soon as you are locked in this mode, you will see a blinking green dot in the center of the screen which indicates precisely the actual landing position. The blinking dot is NOT ANYMORE available in the 2d cockpit, because of the change of camera behaviors in Orbiter 2010, as described before. The “arrow up” command lets you watch through the LM docking window. The two other commands put the camera on both astronauts’ positions.
REMARK: Orbiter 2010 now PRESERVE VIRTUAL COCKPIT POSITION AND ORIENTATION. Therefore, when you quit the virtual cockpit and then bring it up again, you will recover your view exactly as you left it. BUT ATTENTION !!! This behavior is not working when you switch the focus from one vessel to another one. In this case, virtual cockpit camera will be reset to default position and orientation.

PARTICULARITIES OF PRE APOLLO 11 MISSIONS

You can find in the scenario directory "All missions lift off", which is an accurate launch scenario for Apollo 8, 9, and 10 missions.