NASSP 8 Installation Guide

Max-Q

99 40
Addon Developer
Joined
Jul 5, 2021
Messages
765
Reaction score
1,183
Points
108
Location
Cislunar Space
Website
www.orbiter-forum.com
I just zipped a fresh beta r90 install, (no NASSP, D3D9, planet textures, just the way it comes from the SVN), and put it on Orbithangar. This may be of use to those who don't want to mess with the whole SVN thing.

Orbiter Beta r90

Might be a good idea to add this to the instructions as an alternate to the SVN. Now that Orbiter is open-source on GitHub, who knows how long the SVN will be up anyway!
 

jalexb88

Addon Developer
Addon Developer
Joined
Aug 11, 2008
Messages
152
Reaction score
154
Points
43
Location
Canada
I just zipped a fresh beta r90 install, (no NASSP, D3D9, planet textures, just the way it comes from the SVN), and put it on Orbithangar. This may be of use to those who don't want to mess with the whole SVN thing.

Orbiter Beta r90

Might be a good idea to add this to the instructions as an alternate to the SVN. Now that Orbiter is open-source on GitHub, who knows how long the SVN will be up anyway!
Done! thanks
 

Radar_Contact

Member
Joined
Oct 2, 2021
Messages
42
Reaction score
7
Points
8
Location
Poland
I've done everything like in the guide, but I'm getting CTD. Tbh I don't have any idea why there is a crash. From add-ons, I have only: NASSP (latest beta ver from github), D3D9 (symbolic links generated) and Orbiter sound. Here's the log (something with the D3D9?):
 

Attachments

  • log.txt
    6.7 KB · Views: 152

STS

Well-known member
Joined
Feb 1, 2009
Messages
532
Reaction score
274
Points
78
Location
Vigo
Website
orbisondas.es
I've done everything like in the guide, but I'm getting CTD. Tbh I don't have any idea why there is a crash. From add-ons, I have only: NASSP (latest beta ver from github), D3D9 (symbolic links generated) and Orbiter sound. Here's the log (something with the D3D9?):
D3D9 runtimes installed?
(From first post)
 
Joined
Mar 23, 2019
Messages
45
Reaction score
1
Points
8
had a hard drive failure and followed instructions and getting ctd's
here is the log file please advise where I should go for this

**** Orbiter.log
000000.000: Build Sep 14 2019 [v.190914]
000000.000: Timer precision: 1e-07 sec
000000.000: Found 0 joystick(s)
000000.000: Module AtlantisConfig.dll .... [Build 190914, API 190914]
000000.000: Module AtlantisConfig.dll .... [Build 190914, API 190914]
000000.000: Module AtmConfig.dll ......... [Build 190914, API 190914]
000000.000: Module DGConfigurator.dll .... [Build 190914, API 190914]
000000.000: Module DGConfigurator.dll .... [Build 190914, API 190914]
000000.000: Module ProjectApolloConfigurator.dll [Build 230506, API 190914]
000000.000: Module OrbiterSound.dll ...... [Build 200811, API 160828]
000000.000: Module OrbiterSound.dll ...... [Build 200811, API 160828]
000000.000: Module ScnEditor.dll ......... [Build 190914, API 190914]
000000.000: ---------------------------------------------------------------
000000.000: BaseDir : C:\Users\jonat\OneDrive\Desktop\Orbiter2016nassp\orbiter\
000000.000: ConfigDir : C:\Users\jonat\OneDrive\Desktop\Orbiter2016nassp\orbiter\Config\
000000.000: ConfigDir : C:\Users\jonat\OneDrive\Desktop\Orbiter2016nassp\orbiter\Config\
000000.000: MeshDir : C:\Users\jonat\OneDrive\Desktop\Orbiter2016nassp\orbiter\Meshes\
000000.000: HightexDir : C:\Users\jonat\OneDrive\Desktop\Orbiter2016nassp\orbiter\Textures2\
000000.000: HightexDir : C:\Users\jonat\OneDrive\Desktop\Orbiter2016nassp\orbiter\Textures2\
000000.000: ScenarioDir: C:\Users\jonat\OneDrive\Desktop\Orbiter2016nassp\orbiter\Scenarios\
000000.000: D3D9 DLLs : C:\Windows\SYSTEM32\d3dx9_43.dll [v 9.29.952.3111]
000000.000: ---------------------------------------------------------------
000000.000: : C:\Windows\SYSTEM32\d3d9.dll [v 10.0.19041.2788]

000000.000: ---------------------------------------------------------------
000000.000: ---------------------------------------------------------------
000000.000: Module D3D9Client.dll ........ [Build 211009, API 160828]
000000.000: Module ApolloRTCCMFD.dll ..... [Build 230506, API 190914]
000000.000: Module ProjectApolloMFD.dll .. [Build 230506, API 190914]
000000.000:
000000.000: **** Creating simulation session
000000.000: D3D9: [DirectX 9 Initialized]
000000.000: D3D9: 3D-Adapter.............. : Intel(R) HD Graphics 3000
000000.000: D3D9: MaxTextureWidth......... : 8192
000000.000: D3D9: MaxTextureHeight........ : 8192
000000.000: D3D9: MaxTextureRepeat........ : 8192
000000.000: D3D9: VolTexAddressCaps....... : 0x3F
000000.000: D3D9: NumSimultaneousRTs...... : 4
000000.000: D3D9: VertexDeclCaps.......... : 0x37F
000000.000: D3D9: MiscCaps................ : 0x2FCCF2
000000.000: D3D9: XNA Math Support........ : Yes
000000.000: D3D9: Vertex Texture.......... : Yes
000000.000: D3D9: Separate AlphaBlend..... : Yes
000000.000: D3D9: Shadow Mapping.......... : Yes
000000.000: D3D9: D3DFMT_A16B16G16R16F.... : Yes
000000.000: D3D9: D3DFMT_A32B32G32R32F.... : Yes
000000.000: D3D9: D3DFMT_D32F_LOCKABLE.... : No
000000.000: D3D9: D3DFMT_A2R10G10B10...... : Yes
000000.000: D3D9: D3DFMT_L8............... : No
000000.000: D3D9: D3DDTCAPS_DEC3N......... : No
000000.000: D3D9: D3DDTCAPS_FLOAT16_2..... : Yes
000000.000: D3D9: D3DDTCAPS_FLOAT16_4..... : Yes
000000.000: D3D9: Runs under WINE......... : No
000000.000: D3D9: D3D9Build Date.......... : 211009
000000.000: D3D9: Available Texture Memory : 1656 MB
000000.000: D3D9: [3DDevice Initialized]
000000.000: D3D9: ERROR: C:\Software\Orbiter2016-Clean\Orbitersdk\D3D9Client\D3D9Client.cpp Line:804 Error:-2005529767 D3DXCreateTextureFromFileA(pDevice, "Textures/D3D9Noise.dds", &pNoiseTex)
000000.000: D3D9: [Loading Constellations]
000000.000: D3D9: [D3D9Client Initialized]
000000.000: Module Sun.dll ............... [Build 190914, API 190914]
000000.000: VSOP87(E) Sun: Precision 1.0e-06, Terms 554/6634
000000.000: Module Mercury.dll ........... [Build 190914, API 190914]
000000.000: VSOP87(B) Mercury: Precision 1.0e-05, Terms 167/7123
000000.000: Module Venus.dll ............. [Build 190914, API 190914]
000000.000: Module VenusAtm2006.dll ...... [Build 190914, API 190914]
000000.000: VSOP87(B) Venus: Precision 1.0e-05, Terms 79/1710
000000.000: Module Earth.dll ............. [Build 190914, API 190914]
000000.000: Module EarthAtmJ71G.dll ...... [Build 190914, API 190914]
000000.000: VSOP87(B) Earth: Precision 1.0e-08, Terms 2564/2564
000000.000: Module Moon.dll .............. [Build 190914, API 190914]
000000.000: ELP82: Precision 1.0e-05, Terms 116/829
000000.000: Module Mars.dll .............. [Build 190914, API 190914]
000000.000: Module MarsAtm2006.dll ....... [Build 190914, API 190914]
000000.000: VSOP87(B) Mars: Precision 1.0e-05, Terms 405/6400
000000.000: Module Phobos.dll ............ [Build ******, API 060425]
000000.000: Module Deimos.dll ............ [Build ******, API 060425]
000000.000: Module Galsat.dll ............ [Build 190914, API 190914]
000000.000: Module Jupiter.dll ........... [Build 190914, API 190914]
000000.000: VSOP87(B) Jupiter: Precision 1.0e-06, Terms 1624/3625
000000.000: Module Io.dll ................ [Build 190914, API 190914]
000000.000: Module Europa.dll ............ [Build 190914, API 190914]
000000.000: Module Ganymede.dll .......... [Build 190914, API 190914]
000000.000: Module Callisto.dll .......... [Build 190914, API 190914]
000000.000: Module Satsat.dll ............ [Build 190914, API 190914]
000000.000: Module Saturn.dll ............ [Build 190914, API 190914]
000000.000: VSOP87(B) Saturn: Precision 1.0e-06, Terms 2904/6365
000000.000: Module Mimas.dll ............. [Build 190914, API 190914]
000000.000: SATSAT Mimas: Terms 113
000000.000: Module Enceladus.dll ......... [Build 190914, API 190914]
000000.000: SATSAT Enceladus: Terms 33
000000.000: Module Tethys.dll ............ [Build 190914, API 190914]
000000.000: SATSAT Tethys: Terms 101
000000.000: Module Dione.dll ............. [Build 190914, API 190914]
000000.000: SATSAT Dione: Terms 59
000000.000: Module Rhea.dll .............. [Build 190914, API 190914]
000000.000: SATSAT Rhea: Terms 68
000000.000: Module Titan.dll ............. [Build 190914, API 190914]
000000.000: SATSAT Titan: Terms 100
000000.000: Module Uranus.dll ............ [Build 190914, API 190914]
000000.000: VSOP87(B) Uranus: Precision 1.0e-06, Terms 1827/5269
000000.000: Module Miranda.dll ........... [Build ******, API 060425]
000000.000: Module Ariel.dll ............. [Build ******, API 060425]
000000.000: Module Umbriel.dll ........... [Build ******, API 060425]
000000.000: Module Titania.dll ........... [Build ******, API 060425]
000000.000: Module Oberon.dll ............ [Build ******, API 060425]
000000.000: Module Neptune.dll ........... [Build 190914, API 190914]
000000.000: VSOP87(B) Neptune: Precision 1.0e-06, Terms 391/2024
000000.000: Finished initialising world
000000.000: Module Saturn5.dll ........... [Build 230506, API 190914]
000000.000: (Mission File Management) Load mission file into shared memory.
000000.000: (Mission) Loading mission Apollo 8 from file Missions\ProjectApollo\Apollo 8.cfg
000000.000: (Mission) ERROR: Can't open file.
000000.000: Module Crawler.dll ........... [Build 230506, API 190914]
000000.000: Module ML.dll ................ [Build 230506, API 190914]
000000.000: Module VAB.dll ............... [Build 230506, API 190914]
000000.000: Module MSS.dll ............... [Build 230506, API 190914]
000000.000: Module Floodlight.dll ........ [Build 230506, API 190914]
000000.000: Finished initialising status
000000.000: Finished initialising camera
000000.000: Finished setting up render state
000000.000: D3D9: [Scene Initialized]
000000.000: ---------------------------------------------------------------
000000.000: >>> WARNING: Obsolete API function used: oapiBlt
000000.000: Colour key argument not supported by graphics client
000000.000: ---------------------------------------------------------------


I have tried using d3d9 v 30.07 and 4.26 so 1436 and 20161

using nassp build v8.0 2048
 
Last edited:

n72.75

Move slow and try not to break too much.
Orbiter Contributor
Addon Developer
Tutorial Publisher
Donator
Joined
Mar 21, 2008
Messages
2,694
Reaction score
1,352
Points
128
Location
Saco, ME
Website
mwhume.space
Preferred Pronouns
he/him
@grummanonewire

Can you load the default Orbiter scenarios (DG at cape, Brighton beach etc.)?

It looks like you were trying to load Apollo 8, is it just that scenario or do all of them crash?

also, can you verify that "Missions\ProjectApollo\Apollo 8.cfg" actually exists in your install
 
Joined
Mar 23, 2019
Messages
45
Reaction score
1
Points
8
getting the same noise.dds error and the same oapibit error on shuttle a at the moon so its something in the d3d9 client wondering if i should delete and rebuild
 

n72.75

Move slow and try not to break too much.
Orbiter Contributor
Addon Developer
Tutorial Publisher
Donator
Joined
Mar 21, 2008
Messages
2,694
Reaction score
1,352
Points
128
Location
Saco, ME
Website
mwhume.space
Preferred Pronouns
he/him
getting the same noise.dds error and the same oapibit error on shuttle a at the moon so its something in the d3d9 client wondering if i should delete and rebuild
What do you mean by "rebuild"? Are you using OrbiterBeta R90?
 
Joined
Mar 23, 2019
Messages
45
Reaction score
1
Points
8
Yes I do a full SVN checkout. when Im talking about rebuild deleting my Beta Installation and restarting from scratch ...
 

dak4482

New member
Joined
Aug 12, 2014
Messages
20
Reaction score
2
Points
3
Hi all. Very very new to nassp. I'm confused about the two different versions mentioned here. Once Basic Orbiter 2016 is installed should that directory be left alone and all the next steps mentioned on page one be done to a new Orbiter nassp beta directory? Or should orbiter beta be installed ON TOP of the original orbiter 2016 install? also what is the difference between orbiter-beta.exe and orbiter-ng.exe? thx in advance.
 

n72.75

Move slow and try not to break too much.
Orbiter Contributor
Addon Developer
Tutorial Publisher
Donator
Joined
Mar 21, 2008
Messages
2,694
Reaction score
1,352
Points
128
Location
Saco, ME
Website
mwhume.space
Preferred Pronouns
he/him
Hi all. Very very new to nassp. I'm confused about the two different versions mentioned here. Once Basic Orbiter 2016 is installed should that directory be left alone and all the next steps mentioned on page one be done to a new Orbiter nassp beta directory? Or should orbiter beta be installed ON TOP of the original orbiter 2016 install? also what is the difference between orbiter-beta.exe and orbiter-ng.exe? thx in advance.
It can be a bit confusing if you're new.

Orbiter 2016 is the last official stable release of Orbiter.

OrbiterBeta is basically just Orbiter 2016 with a couple of bugs fixed that NASSP needs for proper control during docked engine burns.

A lot of us maintain two separate installs of Orbiter, one of Orbiter Beta (just for NASSP) and one of Orbiter 2016.

Because the high-res textures are on the order of 90GB if you have all of them, most people install their textures in their 2016 install, and point the textures director of their Beta install at their 2016 install's textures directory. That way you don't need two copies of huge files. What this means, however is when you install add-ons in Orbiter Beta, you have to copy files over to your 2016 install, because that's where they'll be looked for

It is of course possible to only install Orbiter Beta if the only reason your installing Orbiter is for use with NASSP, but chances are you'll get hooked and want to try other add-ons too :)

Orbiter.exe: use the old DX7 inline graphics client.

Orbiter_NG.exe: NG = "no graphics". This is what most people use these days and it lets you use the newer DX9 graphics client. The naming convention is because this version allows the graphics and core to be split into two separate software pieces, before the 2010 version there was only one version.
 

dak4482

New member
Joined
Aug 12, 2014
Messages
20
Reaction score
2
Points
3
It can be a bit confusing if you're new.

Orbiter 2016 is the last official stable release of Orbiter.

OrbiterBeta is basically just Orbiter 2016 with a couple of bugs fixed that NASSP needs for proper control during docked engine burns.

A lot of us maintain two separate installs of Orbiter, one of Orbiter Beta (just for NASSP) and one of Orbiter 2016.

Because the high-res textures are on the order of 90GB if you have all of them, most people install their textures in their 2016 install, and point the textures director of their Beta install at their 2016 install's textures directory. That way you don't need two copies of huge files. What this means, however is when you install add-ons in Orbiter Beta, you have to copy files over to your 2016 install, because that's where they'll be looked for

It is of course possible to only install Orbiter Beta if the only reason your installing Orbiter is for use with NASSP, but chances are you'll get hooked and want to try other add-ons too :)

Orbiter.exe: use the old DX7 inline graphics client.

Orbiter_NG.exe: NG = "no graphics". This is what most people use these days and it lets you use the newer DX9 graphics client. The naming convention is because this version allows the graphics and core to be split into two separate software pieces, before the 2010 version there was only one version.
thanks.

I found this in my log:

-------------------------- WARNING: --------------------------
>> Texture not found: ProjectApollo\VC\CueCards\T_AND_D_CONTINUED.dds
Skipping.
>> [TextureManager::AcquireTexture | ..\Texture.cpp | 1040]
---------------------------------------------------------------
000000.000: ---------------------------------------------------------------
000000.000: >>> ERROR: DDraw error DDERR_INVALIDPARAMS
000000.000: >>> [ReadDDSSurface | ..\Texture.cpp | 292]
000000.000: ---------------------------------------------------------------
000000.000: ============================ ERROR: ===========================
000000.000: ReadDDSSurface failed (code: -2147024809)
000000.000: [TextureManager::LoadTexture | ..\Texture.cpp | 1227]
000000.000: ===============================================================

Looks like the cue card stuff didnt get installed and thats why I'm not seeing them. Any ideas??????
 

n72.75

Move slow and try not to break too much.
Orbiter Contributor
Addon Developer
Tutorial Publisher
Donator
Joined
Mar 21, 2008
Messages
2,694
Reaction score
1,352
Points
128
Location
Saco, ME
Website
mwhume.space
Preferred Pronouns
he/him
thanks.

I found this in my log:

-------------------------- WARNING: --------------------------

Skipping.

---------------------------------------------------------------
000000.000: ---------------------------------------------------------------
000000.000: >>> ERROR: DDraw error DDERR_INVALIDPARAMS
000000.000: >>> [ReadDDSSurface | ..\Texture.cpp | 292]
000000.000: ---------------------------------------------------------------
000000.000: ============================ ERROR: ===========================
000000.000: ReadDDSSurface failed (code: -2147024809)
000000.000: [TextureManager::LoadTexture | ..\Texture.cpp | 1227]
000000.000: ===============================================================

Looks like the cue card stuff didnt get installed and thats why I'm not seeing them. Any ideas??????
It looks to me like you may have forgotten to copy over your Textures\ProjectApollo folder into your Orbiter 2016 install.
 

dak4482

New member
Joined
Aug 12, 2014
Messages
20
Reaction score
2
Points
3
It looks to me like you may have forgotten to copy over your Textures\ProjectApollo folder into your Orbiter 2016 install.

NEVER MIND!!!!! I guess I'm half blind. I missed the words "virtual cockpit" in the original post announcing the cue cards. Sorry for the confusion. haha. By the way that orb1 install is so much easier and incorporates almost everything in the official install instructions. It really sped up the install. Only thing left to do was the hi-res earth and moon textures.
 
Last edited:

Max-Q

99 40
Addon Developer
Joined
Jul 5, 2021
Messages
765
Reaction score
1,183
Points
108
Location
Cislunar Space
Website
www.orbiter-forum.com
@dak4482 Do not use orb!
That is not an authorized place NASSP is uploaded, the guy who maintains that is a bad character.
He loves to take credit for others' work, and when we asked him to stop redistributing NASSP, he refused and started trolling us.
@rcflyinghokie can tell you more.
 
Last edited:
Top