NASSP 8 Installation Guide

[jalexb88]

This guide is intended to help users install NASSP 8.0 Beta into Orbiter 2016 Beta. If you are looking for information on installing NASSP 7.0 for Orbiter 2010, please see the wiki article here: http://nassp.sourceforge.net/wiki/Installation

Requirements:

- Latest Orbiter Beta NASSP 8.0 is not compatible with Orbiter 2010 or Orbiter 2016 and is at this time only compatible with the latest Beta release of Orbiter Beta R90 which includes a crucial fix to docked spacecraft physics which is not in the release version.

- Microsoft VS C++ 2017 Redistributable (x86) Package if it's not installed already. https://support.microsoft.com/en-ca/help/2977003/the-latest-supported-visual-c-downloads

- A recent Microsoft DirectX Runtime, for example by using the Microsoft DirectX End-User Runtime Web Installer: https://www.microsoft.com/en-us/download/details.aspx?id=35

Installation:

1. Install Orbiter Beta:

We recommend using the snapshot of Orbiter Beta R90 here: https://www.orbithangar.com/showAddon.php?id=4f300319-5ee2-4c48-a213-50995a480e06 and extract the zip to your desired install folder.

Alternatively, if you wish to use the old SVN method, follow this link http://orbit.medphys.ucl.ac.uk/betainstall.html for instructions on how to install the beta version of Orbiter.

Note: As of July 2021, Orbiter has become open source and further development has moved to GitHub. The above link is to install the last SVN snapshot which is R90, but it is unknown how long this SVN repository will be maintained.

2. Texture Installation:

-Required: Download standard orbiter textures under "Orbiter core package download" and choose the zip file: http://orbit.medphys.ucl.ac.uk/download.html and copy the Textures folder to your orbiter beta install location.

Note: Mirror's 1 and 4 appear to be the only ones working.

-Optional: Download high-resolution Earth & Moon textures under "Optional high-resolution texture download": http://orbit.medphys.ucl.ac.uk/download.html and copy to your Textures/Earth and Textures/Moon folders respectively.

Note: Mirror's 1 and 4 appear to be the only ones working.

Note: If the above links don't work for you, there are alternate links for high resolution textures here: https://www.orbiter-forum.com/resources/orbiter-2016-high-resolution-texture-packs.5676/

-Optional: Download the surface micro textures here: https://www.orbiter-forum.com/resources/d3d9-microtexture-pack.5496/ Scroll down to "MicroTexture Pack for D3D9Client" and unzip to your Orbiter directory.

-Optional: Download "Apollo Landing Sites for Orbiter 2016" by ggalfi here: http://absimp.org/orbitersim/apollolandingsites.html and unzip to your Orbiter directory.
The scenery is breathtaking but be aware there can sometimes be a mismatch between the visible terrain and the physical terrain in the Orbiter engine, so the LM can sometimes be floating above or sunken into the surface after landing. If you try and land exactly at the historical landing site, the mismatch should be minimal.

Note: The high resolution textures and micro textures are optional but really add to the visual experience

3. Install D3D9Client:

- Go to https://www.orbiter-forum.com/resources/d3d9-for-orbiter-beta.5495/ to get the latest version of the client for Orbiter Beta R90.

- Download and unzip the client file to your Orbiter installation folder.

- 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. It is recommended to use "Full Screen Window" mode.

IMPORTANT: Click "Advanced" and add a check beside "Enable absolute animation handling" to prevent animation drift happening in certain cases in the VC. You can also configure the other options in that page to your liking. We also recommend Reflection Mode "Full Scene" to get the best out of the CM's reflective texture.

4. Install XRSound 2.0: https://www.orbiter-forum.com/resources/xrsound-official.5455/

Note: OrbiterSound is not directly supported anymore.

5. Finally, download the latest build of NASSP at this link: https://github.com/orbiternassp/NASSP/releases and unzip to your Orbiter directory. Do the same with the small XRSound config zip file that can be found at the link as well. These files only have to be downloaded once. They are not part of the main NASSP build so that personalized changes can be made to the sound configuration, without being overwritten by a later NASSP build.


Configure Project Apollo:

1. Start Orbiter, go to the "Parameters" tab and make sure that at least Complex flight model, Limited fuel and Nonspherical gravity sources are enabled. Note: At this time, it is recommended to leave "Gravity-gradient torque" and "Atmospheric wind effects" disabled as in some occasions they can cause CTDs or other issues with NASSP.

2. Go to "Visual effects" tab and configure to your liking. Make sure to have a check on surface elevation, using LINEAR interpolation in order to not have the landed LM seem sunken into/floating over the lunar terrain. You should also check "Particle streams" to see the various particle/dust effects in NASSP and "Local light sources" for the night-time launch pad lighting.

3. Go to the "Modules" tab and activate the "ExtMFD", XRSound", "ProjectApolloMFD" and "ApolloRTCCMFD" modules. Do not use the DX9MFD as it is known to cause crashes.

4. Go to the Vessel Configuration->Project Apollo Configuration on the "Extra" tab. If you have a joystick, this is where you can configure your joystick for use in NASSP. Do not use the normal Orbiter controls page to configure your joystick, there it should be <Disabled>. In the "Miscellaneous" tab, make sure "Multi-Threading in time acceleration" is checked. It is also recommended to set a limit for time acceleration, NASSP runs best at 50x or less depending on the hardware you are using.

And that is it! Enjoy

How to update NASSP:

Download the latest build of NASSP at this link: https://github.com/orbiternassp/NASSP/releases and unzip to your Orbiter directory. (Click yes to overwrite files)

Please note, timestamped saves (i.e. those within the "Apollo Mission Scenarios" folder) do not have the latest systems updates. Because of this, they may have alarms and other quirks when loading them. We encourage starting with a fresh launch.

We hope this guide helps, if you need assistance or troubleshooting please visit our discord channel! Have fun!

 

[CuriousMarc]

Trying to get Orbiter beta from the SVN repo, but when I try to download from the SVN repo as instructed from the link in your post:
http://orbit.medphys.ucl.ac.uk/betainstall.html
the TortoiseSVN complains that it does not get an answer from the repo server at:
svn://orbiter-forum.com/orbiter

Is this the wrong link? Is the server actually down?

Marc

 

[Mambo]

Trying to get Orbiter beta from the SVN repo, but when I try to download from the SVN repo as instructed from the link in your post:
http://orbit.medphys.ucl.ac.uk/betainstall.html
the TortoiseSVN complains that it does not get an answer from the repo server at:
svn://orbiter-forum.com/orbiter

Is this the wrong link? Is the server actually down?

Marc

Hi,try this: svn://svn.orbiter-forum.com/orbiter

 

[pappy2]

Hello "jalexb88"

I have a problem displaying textures
I may not have properly installed all the folders

Can you confirm the folders to install in Orbiter2016Beta






Do we need to install both folders together ?



what is the version of D3D9 that corresponds to the last update I installed: NASSP-V8.0-Beta-Orbiter2016-1476



I have the same problem with and without D3D9

thank you in advance

 

[indy91]

Do we need to install both folders together ?

No, you should only have to install the first zip file, not the source code.

what is the version of D3D9 that corresponds to the last update I installed: NASSP-V8.0-Beta-Orbiter2016-1476

You need to use the DX9 Client version that corresponds to the Orbiter Beta version you are running, that's independant from the NASSP version.

But I don't really know what is causing the texture issue. Maybe jalexb88 can help with that.

 

[pappy2]

Very good thanks for the answer "indi91",
but where to find the name of the Orbiter version?

I can not find a name corresponding to the version of D3D9

 

[DaveS]

Use D3D9ClientBeta28.8, it's the latest version for the beta version of Orbiter.

 

[pappy2]

Thank you for your reply "DaveS"

So the important thing is to have the latest version of D3D9Beta for Orbiter 2016 Beta.

Regarding my problem Textures I found where the problem comes from:

As mentioned here http://orbit.medphys.ucl.ac.uk/betainstall.html
to avoid downloading HD HD for Orbiter, I created the lines in the Orbiter_NG.cfg file.



But when I use this method I have the textures of the Earth and the Moon in HD but more textures of Apollo or LM.



Without these lines I have the textures of Apollo and the LM but not the textures of the Earth or the Moon





Any ideas ?

 

[jalexb88]

Thank you for your reply "DaveS"

So the important thing is to have the latest version of D3D9Beta for Orbiter 2016 Beta.

Regarding my problem Textures I found where the problem comes from:

As mentioned here http://orbit.medphys.ucl.ac.uk/betainstall.html
to avoid downloading HD HD for Orbiter, I created the lines in the Orbiter_NG.cfg file.

But when I use this method I have the textures of the Earth and the Moon in HD but more textures of Apollo or LM.

Without these lines I have the textures of Apollo and the LM but not the textures of the Earth or the Moon

Any ideas ?

I believe the problem is that your "ProjectApollo" folder in the texture directory of Orbiter Beta, where your NASSP installation is, is not being read because you have configured Orbiter to read texture files elsewhere (to be able to get the HD planet textures).

What you can do is copy the "Orbiter Beta/Textures/ProjectApollo" folder and paste it in the Textures directory that you are linking in the Orbiter Config file, "ORBITER 2016 THD/Textures" in your case. I will have to update the installation instructions to reflect this.

 

[pappy2]

Hello "jalexb88"
indeed you have found the problem.









It is a good idea to specify this in the installation instructions.
and also specify the correct address for the extraction in TortoiseSVN,

Hi,try this: svn://svn.orbiter-forum.com/orbiter

Because the address indicated on the site of Orbiter is no longer correct

Thanks again and good flights !!!

 

[jalexb88]

Glad to hear! I have updated the instructions for the texture directory and I will now also add the corrected link for TortoiseSVN.

 

[CuriousMarc]

Glad to hear! I have updated the instructions for the texture directory and I will now also add the corrected link for TortoiseSVN.

Thanks, that worked!

 

[gryper]

God, I can't even get past the installation. Probably not my cup of tea. Awesome product though. Wish I was smart enough to use it.

 

[gryper]

I believe the problem is that your "ProjectApollo" folder in the texture directory of Orbiter Beta, where your NASSP installation is, is not being read because you have configured Orbiter to read texture files elsewhere (to be able to get the HD planet textures).

What you can do is copy the "Orbiter Beta/Textures/ProjectApollo" folder and paste it in the Textures directory that you are linking in the Orbiter Config file, "ORBITER 2016 THD/Textures" in your case. I will have to update the installation instructions to reflect this.

I'm having the same graphics display problem. But if I look at the Orbiter config file, I see this:

; === ORBITER Master Configuration File ===
EchoAllParams = FALSE
LPadRect = 0 0 550 574

; === Physics engine ===
NonsphericalGravitySources = TRUE

; === Device settings ===
DeviceIndex = 4
ModeIndex = 4

; === Window positions ===
LpadScnListWidth = 139
LpadModListWidth = 213
LpadExtListWidth = 213

; === Active plugin list ===
ACTIVE_MODULES
ProjectApolloMFD
ApolloRTCCMFD
OrbiterSound
END_MODULES

Where does it indicate which Texture directory I am supposedly linking to incorrectly?

I am not very C++ knowledgeable, at all. But I have dealt with Microsoft Flight Sim for years. And do understand how the file system works, there. (I think).

But I see no indication in this config file showing any kind of link to a texture directory.

Thanks,

Andrew

 

[gryper]

I guess my question was so stupid, no one wants to even answer it. Haa ok, ok... I'll go now. Thanks anyway. But thanks for making such a great product for free on your own time, guys. Maybe I will just try to figure this out on my own. I thought I would ask here, but I understand.

 

[indy91]

Ah sorry, I must have missed your posts a few days ago.

I think you need to add the line in the Orbiter config file, as by default it just uses the texture folder where the install and config file are as well. It gets explained in the Orbiter Beta installation instructions: http://orbit.medphys.ucl.ac.uk/betainstall.html

So, probably anywhere in the config file (Orbiter_NG.cfg if you are using the DX9 Client, which I assume you do), like this:

TextureDir = D:\Orbiter2016\Textures\

for example. Luckily no C++ involved.

 

[palmski]

I think I have everything setup correct but for some reason I have no keyboard control in the game. any suggestions?

 

[ADT187]

Hi! Quick request for installation help if I may...

Have set up a clean install of Orbiter 2016 + beta and all required additions.

All runs ok until I try to switch to the LM virtual cockpit when it CTD. Log file seems to suggest it's trying and failing to load texture files. Have attached copy of file.

Thank you all for efforts in producing such an excellent sim!

Cheers,

Alex

 

[jalexb88]

Hi! Quick request for installation help if I may...

Have set up a clean install of Orbiter 2016 + beta and all required additions.

All runs ok until I try to switch to the LM virtual cockpit when it CTD. Log file seems to suggest it's trying and failing to load texture files. Have attached copy of file.

Thank you all for efforts in producing such an excellent sim!

Cheers,

Alex

Sounds like you are missing some NASSP textures. If you check the outside view, does the CSM/LM have textures, or does it look all white/grey?

 

[ADT187]

Yes the CSM/LM both have textures.

Cheers,

Alex