thermocalc
Active member
Hi there, I am sorry but I am facing a new problem for which I would ask for your kind help.
I decided to start studying and practicing Apollo 9-10-11 from scratch, until now I only managed Apollo 8 and partially Apollo 7 (still ongoing) with NASSP v7 and Orbiter2010P1, so NASSP on Orbiter2016 is new for me, so I decided to make a completely new installation of Orbiter Beta as for r90, as well as NASSP v8 beta 1537, I followed all steps described in the “NASSP 8 Installation Guide” post and for your reference here what I did:
Is that a problem to run the simulation? Is there a way to turn it green again? Do we (as end users) are supposed to run the sim independently of the status of the icon…red or green?. Do we need to “bother” about the color or not?
Now the real problems/questions come.
Q1) I started NASSP v8 loading some launch scenarios to see what happens.
During the loading time of the scenario, I saw the Earth with the BETA script and the following information: “Orbiter Space Flight Simulator – Build September 14 2019 [190914] D3D9 Client Beta 30.0 [Aug 10 2020]” -> is it normal? I mean, the information reported are coherent with the latest orbiter beta/D3D9 client status?
Q2) Upon loading the scenario I saw “dark patches near the Launch pad” as in these examples taken by the default Apollo 7, 9, 10 and 11 MCC Launch scenarios:
Apollo 7 MCC Launch scenario
Apollo 9 MCC Launch scenario
Apollo 10 MCC Launch scenario
Apollo 11 MCC Launch scenario
Q3) I try to activate the visual helpers as in the old NASSP v7 or in the normal Orbiter2016 version, for the Earth (while in Earth orbit) and Moon (while in Moon orbit):
Surface -> Config -> Earth -> I saw a lot of choices to select such as: Airport/city/Montain…. But no “Apollo Earth Landmarks”, and moreover even if I select all NOTHING (none label) was displayed on the Earth globe (while with Orbiter2016 or NASSO v7 there were there to see);
for Surface-> Config->Moon-> I saw even more choices such as: catena, crater,….vallis, but no “Apollo Moon Landmarks”, and moreover even if I select them all, NOTHING (none label) was displayed on the Moon globe (while with Orbiter2016 or NASSO v7 there were there to see);
is this normal? (I read some posts in the forum where people were saying that there were no more Apollo Moon Landmarks but they were around 2018-19 if I am not mistaken, so I thought that maybe by now developers have find out a way to recreate these visual aids in the latest betas…so maybe I did something wrong to set up the files? But I never read about similar problem happened for the Apollo Earth Landmarks….so I am still puzzled…
The Celestiial -> Config -> Apollo AGC Navigation stars are there, they are displayed , so they are fine.
Sorry for the extremely long post but hope I gave you all possible information and please let me know if this is “normal” at this stage of development, so I have really the latest status set-up correctly or instead I did something wrong, if so please give my advises.
Thank you for any help…
Paolo
I decided to start studying and practicing Apollo 9-10-11 from scratch, until now I only managed Apollo 8 and partially Apollo 7 (still ongoing) with NASSP v7 and Orbiter2010P1, so NASSP on Orbiter2016 is new for me, so I decided to make a completely new installation of Orbiter Beta as for r90, as well as NASSP v8 beta 1537, I followed all steps described in the “NASSP 8 Installation Guide” post and for your reference here what I did:
- I downloaded the latest Microsoft DirectX, I run the installer and I got this message: “DirectX setup has determined that a newer or equivalent version of DirectX has been installed already. No installation is necessary” -> so I think I am ok.
- I downloaded from Dr. Martin website the zip file of the normal Orbiter2016, and I installed it into a new directory, named “Orbiter2016” (and it worked fine with traditional Orbiter vessels)
- I created in C: a new directory named “Orbiter Beta r90” and after SVN checkout to download orbiter beta rev90 I got all “green” small icons on the bottom left corner of the folder yellow icon.
- I didn’t download the High Resolution “Orbiter 2016 planetary textures (Earth and Moon)”, as my PC is not so powerful anymore, I just copy the whole EARTH and MOON folders (containing the ***.tree files in the Archive subfolder) found inside the TEXTURE folder of the original Orbiter2016 installation I made at step 2 above, into the TEXTURE folder of the “Orbiter Beta r90” directory: as there were no preexisting Earth or Moon folders there everything went smooth.
- D3D9ClientBeta30.0-forBETA r90(r1329) -> here I got an alert message when copying cloud1.dss file, as I saw that the file from the D3D9 unzipped folder was 1 MB and the one already present in the Orbiter Beta r90 folder was only 64.1 Kb I said YES and it was automatically overwritten.
- I open “orbiter-ng.exe” and I set up everything as described in the installation post. Actually, in the “Video”->”Advance” I also click the bottom “create symbolic links” as I saw that while starting a scenario on the bottom of the screen it told to enable symbolic links.
- I unzipped the files of “Surface MicroTextures” into the main Orbiter Beta r90 folder
- I installed OrbiterSound50_20200811_setup (actually the post say the version 4.0 but I saw that the version 5.0 is available and ok for the newest orbiter beta, so I think I can use it (?)).
- I unzipped NASSP-V8.0-Beta-Orbiter2016-1537 into the main Orbiter Beta r90 folder.
- I configured Project Apollo as described in the post.
Is that a problem to run the simulation? Is there a way to turn it green again? Do we (as end users) are supposed to run the sim independently of the status of the icon…red or green?. Do we need to “bother” about the color or not?
Now the real problems/questions come.
Q1) I started NASSP v8 loading some launch scenarios to see what happens.
During the loading time of the scenario, I saw the Earth with the BETA script and the following information: “Orbiter Space Flight Simulator – Build September 14 2019 [190914] D3D9 Client Beta 30.0 [Aug 10 2020]” -> is it normal? I mean, the information reported are coherent with the latest orbiter beta/D3D9 client status?
Q2) Upon loading the scenario I saw “dark patches near the Launch pad” as in these examples taken by the default Apollo 7, 9, 10 and 11 MCC Launch scenarios:
Apollo 7 MCC Launch scenario
Apollo 9 MCC Launch scenario
Apollo 10 MCC Launch scenario
Apollo 11 MCC Launch scenario
Q3) I try to activate the visual helpers as in the old NASSP v7 or in the normal Orbiter2016 version, for the Earth (while in Earth orbit) and Moon (while in Moon orbit):
Surface -> Config -> Earth -> I saw a lot of choices to select such as: Airport/city/Montain…. But no “Apollo Earth Landmarks”, and moreover even if I select all NOTHING (none label) was displayed on the Earth globe (while with Orbiter2016 or NASSO v7 there were there to see);
for Surface-> Config->Moon-> I saw even more choices such as: catena, crater,….vallis, but no “Apollo Moon Landmarks”, and moreover even if I select them all, NOTHING (none label) was displayed on the Moon globe (while with Orbiter2016 or NASSO v7 there were there to see);
is this normal? (I read some posts in the forum where people were saying that there were no more Apollo Moon Landmarks but they were around 2018-19 if I am not mistaken, so I thought that maybe by now developers have find out a way to recreate these visual aids in the latest betas…so maybe I did something wrong to set up the files? But I never read about similar problem happened for the Apollo Earth Landmarks….so I am still puzzled…
The Celestiial -> Config -> Apollo AGC Navigation stars are there, they are displayed , so they are fine.
Sorry for the extremely long post but hope I gave you all possible information and please let me know if this is “normal” at this stage of development, so I have really the latest status set-up correctly or instead I did something wrong, if so please give my advises.
Thank you for any help…
Paolo