Failures and Installation: Difference between pages

From Project Apollo - NASSP
(Difference between pages)
Jump to navigation Jump to search
No edit summary
 
(Replace NASSP 8 installation guide with a link to the Orbiter Forum guide for the time being.)
 
Line 1: Line 1:
'''NASSP''' simulates various failures for the CSM, LM and Saturn rockets. To enable them select "Damage and Failure Simulation" under Realism in the Parameters tab of the Orbiter launchpad. Failures can be scheduled or randomized. Aside from specific failures in the simulation, generic switch failures are supported where systems see the state of a switch in a failed switch position, different from the actual position. The specific failures can be scheduled or randomized in the Project Apollo MFD, switch failures are currently only available through editing scenarios.
{{Infobox | caption=Latest Downloads | text={{Latest_Downloads Extended}} }}


=Specific Failures=
Project Apollo - NASSP is an ongoing project, many developers are working on lots of new features and enhancements. If you are interested in this development you can now test the current version of Project Apollo.


For failures to occur they have to be "armed" and a failure condition has to be added to them. These conditions are currently all time based. For both CSM and LM the mission time since launch (failure condition 0) can be used as well as the simulation time (failure condition 1) since the start of the simulation. Only the CSM currently supports more failure conditions.
Since Project Apollo is an open source project and all developers are working for free in their spare time we don't have project plans, schedules, or things like this. We coordinate the development by using our [https://www.orbiter-forum.com/forums/project-apollo-nassp.40/ forums]. So if you read the latest news you hopefully get all the necessary information you need to use Project Apollo. Of course every developer is happy to get feedback regarding his work to fix bugs and make improvements, so please do not hesitate to post in the forum if you discover something noteworthy.


==CSM Failures==
= NASSP 8.0 Beta =


===Failure Types===
The guide shown on this wiki is outdated. For the time being, please refer to THIS guide on the Orbiter Forums, which is the most up-to-date guide on installing the newest version of NASSP: https://www.orbiter-forum.com/threads/nassp-8-installation-guide.36801/


The list of available failures that are simulation can be viewed directly in the PAMFD page for failures. The majority of them are still launch or reentry related.


====Launch Failures====
= NASSP 7.0 (Deprecated) =
The center engine on the SIb, SIC and SII stages may randomly shut down early. This may or may not require a launch abort or a different mission profile depending on when in the launch it occurs: with a Saturn 1b this may not leave enough fuel to reach orbit, and with a Saturn V it may not leave enough fuel to reach the Moon.


The LET auto jettison may fail, requiring you to jettison the tower manually. The LET jettison motor may fail, requiring you to jettison the tower manually with the abort motor. Automatic separation of the SII stage from the SIC may fail, requiring you to separate manually.
This version of NASSP is several years old, having released in 2017. It is no longer actively maintained, but should remain perfectly usable if you desire a "stable" version of NASSP that will not change, at the cost of missing out on more recent improvements to simulation accuracy, etc. If you wish to upgrade from NASSP 7.0 to 8.0, it is highly recommended to perform a complete reinstall from scratch, following the instructions provided in the earlier "NASSP 8.0" section.


====Display Failures====
This section tries to provide step-by-step instructions to set up the Orbiter environment for Project Apollo. You need to do the following steps only once. If you want to update your installation read the "How do I update?" section below.
Random lights on the Caution and Warning System will fail.


====Switch Failures====
== Install Orbiter ==
Any of the TWR JETT and SM JETT switches may fail, though only one of each type will fail at any time as having both fail would be fatal. If one of the two redundant switches doesn't function, use the other.


====Landing Failures====
If you have installed the latest Orbiter 2010 version already, you can use this installation for Project Apollo, of course. Otherwise you need to install Orbiter. This includes the following steps at the moment:<br><br>'''Orbiter 2010-P1 Edition'''
The apex cover deploy, drogue deploy and main chute deploy may fail randomly. You will have to deploy them manually.
* Orbiter100830.zip/msi as explained here: http://www.orbiter-forum.com/download.php<br><br>Optional:
* Earth091124_11_14.zip
* Moon090730_L11.zip


===Failure Conditions===
'''OrbiterSound 4.0'''
* http://orbiter.dansteph.com/forum/index.php?page=download


The additional failure conditions for the CSM are:
Optional: '''High resolution surface tiles for the Kennedy Space Center'''
* [http://sourceforge.net/projects/nassp/files/Orbiter/KSC_HiRes_Tiles.zip/download KSC_HiRes_Tiles.zip]


*2 = time since S-I/S-II (or S-IVB) staging
== Installation Prerequisites ==
*3 = time since S-II/S-IVB staging
*4 = time since Earth Orbit Insertion
*5 = time since TLI preparations start (Timebase 6)
*6 = time since TLI cutoff


==LM Failures==
Install the '''[https://www.microsoft.com/en-us/download/details.aspx?id=48145 Microsoft VS C++ 2015 Redistributable (x86) Package]''' if it's not installed already.


No specific failures are currently supported for the LM, but switch failures can be scheduled on mission or simulation time.


=Switch Failures=
== Install Project Apollo - NASSP ==


Switch malfunctions have to be added to scenarios. For this, a failure section in the scenario has to be added that starts with line FAILURES_BEGIN and ends with FAILURES_END. In between, the following format is used.
Follow the '''Modules Pack''' link at the top of this page download and unzip the first .zip file to your Orbiter installation folder. Make sure that the directory structure of the archive is retained, usually there's a "Use Folders" option box or similar, which should be ticked/checked.


SWITCHMALFUNCTION GNComputerMnACircuitBraker 0 0 100.0
Optionally, you can download and unzip the '''Source Code.zip''' the same way if you wish to have the source code that corresponds to the binary release.


1st parameter: name of failed panel element
== Optional, but recommended: Install the DirectX 9 client ==
2nd parameter: failure state of panel element
3rd parameter: The condition type for the failure. See above.
4th parameter: The time value associated with the condition type.


There is no list of switches, but the names can be derived from the saturnpanel.cpp and lempanel.com files where the names are used in the Register function for each switch.
The built-in (aka "inline") Orbiter graphics client is based on DirectX 7. Especially with Windows 7 computers and/or recent graphics adapter this client isn't working very well or in some cases isn't working at all. Fortunately there's an DirectX 9 client by [http://www.orbiter-forum.com/member.php?u=408 jarmonik] meanwhile, which is working great with Project Apollo. So it is strongly suggested to give it a try. You can get it from [http://www.orbiter-forum.com/showthread.php?t=18431&highlight=d3d9client this thread] in the Orbiter main forum or by following these instructions:
 
*  Install a recent Microsoft DirectX Runtime, for example by using the [http://www.microsoft.com/en-us/download/details.aspx?id=35 Microsoft DirectX End-User Runtime Web Installer].
 
* Download and unzip the [http://d3d9client.codeplex.com/ client] file to your Orbiter installation folder the same way as the Project Apollo files above.
 
* Start '''Orbiter_ng.exe''' (NOT Orbiter.exe) from your Orbiter installation folder.
 
* Go to the "Modules" tab and activate the "D3D9Client" module.
 
* The "Video" tab appears, configure the video settings as you like, they are quite similar to the usual Orbiter video settings. Do not change any settings you don't know/understand.
 
* Launch a build-in scenario in order to check if the client is running fine before you continue with the instructions below.
 
 
== Configure Project Apollo ==
 
* Start Orbiter ('''Orbiter_ng.exe''' in case you're using the DirectX 9 client), go to the "Parameters" tab and make sure that at least '''Complex flight model''', '''Limited fuel''', '''Gravity-gradient torque''' and '''Nonspherical gravity sources''' are enabled.
 
* Go to the "Modules" tab and activate the '''[[ProjectApolloMFD]]''' module.
 
* Optionally you can change some options with the '''[[Launchpad Configuration Options]]''' on the "Extra" tab.
 
* That's all, now you can try if Project Apollo is working properly. You'll find the proper scenarios in the '''"Project Apollo - NASSP" scenario folder'''. Please note that the scenarions in the "Broken Scenarios" subfolder are, well, broken.
 
 
== How do I update? ==
 
To update your Project Apollo installation you can repeat the steps above in [[Installation#Install_Project_Apollo_-_NASSP|Install Project Apollo - NASSP]].
 
== How can I track the development source and/or participate in development? ==
 
Please see the [http://www.ibiblio.org/mscorbit/mscforum/index.php?board=34.0 development area of the forums], specifically the [http://www.ibiblio.org/mscorbit/mscforum/index.php?topic=2864.0 git instructions thread].
 
==See Also==
 
* [[:Category:Scenario configuration|Configuration]]

Latest revision as of 19:37, 26 August 2024

Latest Downloads
Latest NASSP 8.0 beta

https://github.com/orbiternassp/NASSP/releases

The link opens the GitHub download page.
NASSP 7.0.1 modules (legacy, last updated May 13th, 2021)

Project-Apollo-NASSP-V7.0.1.zip

Project Apollo - NASSP is an ongoing project, many developers are working on lots of new features and enhancements. If you are interested in this development you can now test the current version of Project Apollo.

Since Project Apollo is an open source project and all developers are working for free in their spare time we don't have project plans, schedules, or things like this. We coordinate the development by using our forums. So if you read the latest news you hopefully get all the necessary information you need to use Project Apollo. Of course every developer is happy to get feedback regarding his work to fix bugs and make improvements, so please do not hesitate to post in the forum if you discover something noteworthy.

NASSP 8.0 Beta

The guide shown on this wiki is outdated. For the time being, please refer to THIS guide on the Orbiter Forums, which is the most up-to-date guide on installing the newest version of NASSP: https://www.orbiter-forum.com/threads/nassp-8-installation-guide.36801/


NASSP 7.0 (Deprecated)

This version of NASSP is several years old, having released in 2017. It is no longer actively maintained, but should remain perfectly usable if you desire a "stable" version of NASSP that will not change, at the cost of missing out on more recent improvements to simulation accuracy, etc. If you wish to upgrade from NASSP 7.0 to 8.0, it is highly recommended to perform a complete reinstall from scratch, following the instructions provided in the earlier "NASSP 8.0" section.

This section tries to provide step-by-step instructions to set up the Orbiter environment for Project Apollo. You need to do the following steps only once. If you want to update your installation read the "How do I update?" section below.

Install Orbiter

If you have installed the latest Orbiter 2010 version already, you can use this installation for Project Apollo, of course. Otherwise you need to install Orbiter. This includes the following steps at the moment:

Orbiter 2010-P1 Edition

OrbiterSound 4.0

Optional: High resolution surface tiles for the Kennedy Space Center

Installation Prerequisites

Install the Microsoft VS C++ 2015 Redistributable (x86) Package if it's not installed already.


Install Project Apollo - NASSP

Follow the Modules Pack link at the top of this page download and unzip the first .zip file to your Orbiter installation folder. Make sure that the directory structure of the archive is retained, usually there's a "Use Folders" option box or similar, which should be ticked/checked.

Optionally, you can download and unzip the Source Code.zip the same way if you wish to have the source code that corresponds to the binary release.

Optional, but recommended: Install the DirectX 9 client

The built-in (aka "inline") Orbiter graphics client is based on DirectX 7. Especially with Windows 7 computers and/or recent graphics adapter this client isn't working very well or in some cases isn't working at all. Fortunately there's an DirectX 9 client by jarmonik meanwhile, which is working great with Project Apollo. So it is strongly suggested to give it a try. You can get it from this thread in the Orbiter main forum or by following these instructions:

  • Download and unzip the client file to your Orbiter installation folder the same way as the Project Apollo files above.
  • Start Orbiter_ng.exe (NOT Orbiter.exe) from your Orbiter installation folder.
  • Go to the "Modules" tab and activate the "D3D9Client" module.
  • The "Video" tab appears, configure the video settings as you like, they are quite similar to the usual Orbiter video settings. Do not change any settings you don't know/understand.
  • Launch a build-in scenario in order to check if the client is running fine before you continue with the instructions below.


Configure Project Apollo

  • Start Orbiter (Orbiter_ng.exe in case you're using the DirectX 9 client), go to the "Parameters" tab and make sure that at least Complex flight model, Limited fuel, Gravity-gradient torque and Nonspherical gravity sources are enabled.
  • That's all, now you can try if Project Apollo is working properly. You'll find the proper scenarios in the "Project Apollo - NASSP" scenario folder. Please note that the scenarions in the "Broken Scenarios" subfolder are, well, broken.


How do I update?

To update your Project Apollo installation you can repeat the steps above in Install Project Apollo - NASSP.

How can I track the development source and/or participate in development?

Please see the development area of the forums, specifically the git instructions thread.

See Also

Retrieved from "http://nassp.space/index.php?title=Failures&oldid=2383"