Search results

Yes I do a full SVN checkout. when Im talking about rebuild deleting my Beta Installation and restarting from scratch ...

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

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...

the O2 Cryo pressure issue .. These are on new scenarios I was running into some issues after doing updates and I decided to purge my entire install and start from scratch I find that this is probably the easiest fix for me with NASSP So there is no Saved scenarios etc and no warnings...

I am reinstalling NASSP after a bit of a hiatus in play and was looking at getting the most updated version And I was having issues with O2 cryo pressure reading zero but quantity 100% Anyways Ive got everything set up I load Appollo 9 launch scenario and I get LC 39 but no LUT or...

Interesting note now that I am now working off a fresh install I would try any file from Scenarios\Project Apollo - NASSP\Apollo - Mission Scenarios\Apollo 11 and I would get program alarms etc and brushed it off as a bad scn file. Given the Beta status of this project and knowing its been...

using the latest update /scenarios/project apollo nassp/ apollo 11 launch I tried to update nassp and broke it so I reloaded everything and retried the scenario and it was popping the alarms you indicated so I am going to assume somewhere in my adventures of playing NASSP i messed up a save...

No program alarms or restart indications and cfg file has comanche and lgc is luminary no timestamps are indicated in any of the misson.cfg files

No Ive been working off the same scenario for about 3 weeks so I know I am not using the latest version but this is off the default apollo 11 launch scenario not in the Apollo Mission Scenarios folder

heres the scenario file

Using the default apollo 11 scenario CMC time matches Mission Timer according to AOH A16V02 checklist page 4-518 if you enter V21 you can reject CMC star selection and enter one that may be in view but it keeps giving me V09N45 404 alarm even if I can center the crosshairs on it before...

Trying to do the first P52 in Apollo 11 and the computer is giving me stars outside of the view field or traverse range of the sextant... and entering V21 at V01N70 an d entering a star that is clearly in the view field on the first sighting is causing V09N45 404 alarm did I mess anything up...

Hello I am wondering at one time I was using NASSP on orbiter and not Beta before I got wise to that I have since switched to Beta and transferred all the earth texture files over and moon texture files similarly as i needed to for FDAI textures One thing that I am curious about is how to...

Yeah figured that out thanks its probably some line of code on the NASSP side that has not been changed

Update : I was able to resolve this I just copied and pasted the Project Apollo textures folder into both the main and the beta installation texture folder. I am wondering if there isnt something in the NASSP coding for this but it seems resolved as so far

Thats what I have done is I updated the textures to the main directory path to the main C:\Users\Jon\Documents\OrbiterMain\Textures my beta NG config file ; === Subdirectory locations TextureDir = C:\Users\Jon\Documents\OrbiterMain\Textures\ Deep dove the main textures and FDAI .dds files...

I got out of NASSP for a while and just have decided to get back into it. I have everything up and running so far however I am having an issue and I do not know if this is a direction change in the builds or a legitmate issue I come from the FS community FS2004 and FSX and bought several...

I now have the simulation re running but on the 2 d panel the FDAI 1+2 are just a solid white which I think is missing textures. Is this part of the new updates that these do not work or a bug do the FDAI's work in VC mode Since NASSP is primarily procedural I usually fly missions from the...

Ok so I use Orbiter for NASSP and had walked away for it from a bit and removed and re installed a new installation for Beta couple of issues I am having 1 OrbiterNG cfg is not saving with the texture folder re route copied and pasted to module/server as well 2 I have no planetary textures...

Ok so I am re installing orbiter and NASSP I got Beta installed but cannot get graphics to work with D3D9 client for most current SVN update and Current D3D9 client release dated april 2021 I have the config file with texturedir= ( non beta install ) and still get a ctd I have not put in...