Search results

NASSP 8.0 LM VC work-in-progress: Panels 1-4 are almost done.

"Further VC work, including working gauges is slated for NASSP 9.0." Well that was a lie :lol: https://www.orbiter-forum.com/showthread.php?p=606185&postcount=7688

Work-In-Progress: NASSP LM virtual cockpit with working gauges and switches :)

The LM VC has had a bit of an update, with the goal of making it easier to fly the lunar landing from the VC in NASSP 8.0. No gauges are functional yet but panels 1-4 are now displayed (static). LGC altitude and descent rate information as well as guidance modes & remaining fuel are displayed in...

That is only the case when you are in CMC mode (SC CONT - CMC). If you are in SCS mode then setting the wide deadband will ensure that thrusters dont fire if any rates develop during time accel. If you are in CMC mode then the only thing to worry about is CMC mode to free.

That is normal. Its better not to use time acceleration with any DAP modes active, set CMC MODE - FREE & SCS in wide dead-band during time acceleration, same goes with the LM.

That option should always be ticked for best performance, it is not on by default but it really should be and there should be an update for that soon. How much time acceleration can be safely used really depends on how fast your system is, on mine I use 30x in cislunar space or 10x in low earth...

So the issue is that the 4:3 bitmap is being selected, rather then the 16:9 one which it definitely should do. The Project Apollo Configurator has code which detects the user's aspect ratio and should automatically select the proper bitmap, but it seems this has failed in your case. Are you...

To better understand the issue, can you post a screenshot of it?

Are you re-using a texture directory from another Orbiter installation? If so you must copy the "Textures/ProjectApollo" folder over to the actual Texture directory that is being used by your Orbiter Beta/NASSP installation. This is outlined in the NASSP 8 Installation Guide thread.

You 1st want to find the bias, since the AGS is started many hours into the mission, the starting point is biased. Usually this is the previous 10 hour mark from power-up, so if you start it at 95:00:00 then you will use 90 hour bias, if you start it at 102:00:00, then 100 hour bias. You enter...

Ok sounds good. I'll take a look at the mesh, could very well be a few issues with it as it hasn't been updated in probably 15 years or so. Thanks for the help!

Well, I would say quite a ways :lol:

Maybe you are forgetting the + before entering the angles? (+000.00)

That would be R 001.00 P 204.00 Y 358.00

Here you go. As soon as I zoom out past 80m or so the shimmering goes away, in the screenshot its hard to see but there is still a bit of shimmering. As I also said in my edit, just turning the rover to a different heading seems to fix the issue completely, also the issue only appears on the LM...

Today I was driving the lunar rover in NASSP 8.0 Beta on Apollo 17, when I switched views back to my EVA astronaut, I suddenly got some strange "shimmer" showing on him. I then switched to the LM and the same thing: I tried re-installing D3D9 client but the issue persists, also if I turn off...

If you want to play around with P20 and Artemis072/Luminary210, the Apollo 17 - Before PDI scenario has been updated in "WIP Scenarios\Apollo - Mission Scenarios\Apollo 17" You can also push in the landing radar CB, run P63 and enjoy the descent into Taurus-Littrow :)

Are you running the D3D9 client found here: http://users.kymp.net/~p501474a/D3D9Client/ ? NASSP 8 Beta is only compatible with Orbiter Beta and the corresponding beta version D3D9 client as described in the installation instructions thread. By dx11 client, are you talking of this thread...

Hmm that is a weird one. Are you sure you are set to Full Screen Window, and not True Full screen?