Search results

Thanks! I will try and give it a test once I get a build environment going for Orbiter.

Thanks for checking this! Yeah I suspected it would be hard to figure out a work-around to make it work in r90, but if its easily fixable in the development version of Orbiter this is already very good news! :)

Since a few months now NASSP has variable CG in the CSM+LM accomplished with ShiftCG(). We are now noticing issues with VC click-spot positions getting messed up only scenarios with both LM + CSM loaded in the session and only when the session is loaded already in the VC. The issue seems to be...

NASSP 8.0 Beta - A few pics of Eagle

A few visuals updates for the CSM & LM: Some new D3D9 configuration files have been defined for the SM & LM. These now use "metalness PBR" which increase the realism for metallic surfaces and things such as foil. For the effects to be visible, you mush have D3D9ClientBeta30.7-forBETA r90(r1436)...

CM Virtual Cockpit: The command module virtual cockpit has been part of NASSP for more then 10 years, the meshes/textures originally created by Swatch, another NASSP developer. Up until recently however, the VC was completely static and dark so I turned on the lights and started work on...

@ggalfi I guess if we are following the timeline we can expect some nice Descartes terrain this coming April? ?

NASSP 8.0 Beta Playing around with some metallic effects on the LM. Merry Christmas!

Done! thanks

Yep, nothing you can do about that, NASSP 7.0 is not compatible with Orbiter 2016/Orbiter Beta, so there is no fix in your case for that issue other then installing NASSP 8.0 in Orbiter Beta. Please follow the instructions at the top of this post step by step... If you want to continue using...

Sometimes this happens for me if I have Orbiter running along with a 2nd instance running in the background from a previous session or whatever. On rare occasions Orbiter doesn't terminate properly I think, you can check the Task Manager. The PGNS switch is under "MODE CONTROL", right above the...

Yes, you have to manually sequence the yellow steps with PRO or FAIL buttons By the AGS steps I mean all the items before the (PDI -5) step can be skipped if you want, just keep clicking FAIL until you get to (PDI -5).

I would recommend using the "Apollo 11 - 12 - Before PDI T+102h28min" scenario found in the "Apollo - Mission Scenarios" folder. It has everything set up for PDI minus 10 minute mark. Just follow the checklist MFD from there, If you want the LM to land automatically just leave the PGNS switch on...

Yep, there is a Quickstart mode: https://www.acsoft.ch/AMSO/amso.html :LOL: In all seriousness though, the old "Quickstart" mode in NASSP was removed since in was a big mess in the code and was interfering with the main goal of having as much realism as possible. The simplicity of having only...

Are you following the instructions at the top of this post, or at http://nassp.sourceforge.net? The latter is quite outdated and only for NASSP 7.0 and Orbiter 2010 as stated above. The instructions at the top of this post is what should be used as they are the most recent and for NASSP 8.0 and...

Are you using ParkingBrakeMFD by any chance?

Panel 227 is not added yet in the CM VC, will come eventually. The needle disappearing sounds like you haven't yet added a check on "Enable Absolute Animation Handling", in the D3D9 client advanced settings, you can try that to see if it fixes the issue.

It is still right click to operate the covers in the VC, just try to aim for the perimeter of the switch to operate it, if you aim for the center of the switch, the right click is then controlling the downward motion of the switch and not the cover state.

Like n7275 said above, adding that check should fix the VC animations "drift", I have also added this to the installation guide. As for the sound issue, I think I might know what is happening there, can you tell me what your FPS is in the VC? At very high FPS (over 90 or so) there is a bug that...

Its because you have your MANUAL ATTITUDE switches set to ACCEL CMD, set them to RATE CMD and that should fix your issue. TEI-31 is I believe the PAD you would burn on the next revolution if you missed the nominal TEI (TEI-30) .