Search results

That totally depends on the vessel you're trying to use. Orbiter has no API to modify state or failures within vessels as the way these are implemented can vary wildly (if implemented at all). I can only speak for NASSP in detail and I can tell you we do not specifically expose a stable API for...

Are you on the latest version? This was fixed recently.

The IMU error counters are used to display IMU error from the desired DAP attitude on the FDAI, that's why that's on. I haven't yet figured out what the cause of this issue is. In order to watch some memory locations while making DSKY inputs I have constructed an EMP to put a location in...

If you do this you do need to reset the REFSMMAT and DRIFT flags though, apart from that there's no side effects.

I can't think of any. In fact the simulation should be more stable due to the shorter timestep length.

It is included but it's not really easy to find the documentation if you don't know where to look as there is no user-friendly way to set it up you need to manually create a file that is then read by this module. You can find a description in Doc/Project Apollo - NASSP/VESIM.txt

Timesteps and the systems within them are synchronous. Meaning, if one part slows down, the whole simulation slows down and your FPS will drop. At very low fps (<10) there is a chance for systems to become a bit unstable but at no point will your AGC be slow compared to the rest of the simulation.

Seen these guys perform live as Sabaton's opening act. Gonna see them live next year.

I see you made 9 marks and P20 running in the background. That means they are automatically incorporated. P34 will never show you a N49 display.

If the optics mode switch is set to CMC then indeed the optics will move to where the AGC thinks it is. If you have the switch set to MANual then you can move the optics yourself and make a mark. All systems are modeled directly from drawings and handbooks and will function the same as the real...

The Excel based flightplans had procedural errors and depended on unrealistic tools like the IMFD. Nowadays NASSP features the MCC and RTCC MFD to calculate maneuvers and the Checklist MFD for the flightplan and other activities, these are the supported tools.For that reason the spreadsheets...

We've also started to maintain a little bit of a Discord presence on the Spaceflight Server where people can ask questions and talk. Invite: https://discord.gg/ceUvBbY3bQ

I was taking some marks of landmarks during my Apollo 8 flight and figured I'd try to recreate a photograph they took. Original photograph: Orbiter:

@jarmonik, if you have your hands full of D3D9Client work, would you consider distributing this addon under an open source license?

What commit is it? It can be cherry-picked from your branch and merged separately.

A bugfix has just been released for the Apollo 8 mission scenarios (that are already in orbit). Thanks @indy91. Due to updates in the RTCC these scenarios no longer knew the correct liftoff time and as a result state vectors and maneuvers were calculated approx. 12 hours into the future. If you...

For a long time NASSP had a bug that randomly triggered when rapidly switching between high level of time acceleration and realtime, for example when receiving a PAD from AGC. When this happened the state of the AGC would be corrupted causing computer restarts and other havoc to its erasable...

Probably not gonna be the same yellow boxes but something like that for the VC is on my list

With MIT this is indeed no problem but with the previous proprietary license it was. In order to use it we had to statically link XRSound's library, That would violate both XRSound's library by redistributing that library and it would violate the GPL as we would not be allowed to distribute...

Great news! Someone already made a draft PR to make NASSP work with XRSound but it was postponed due to the license conflicting with GPL. I'm gonna take another look at it to see if it can be made to work now that it's under MIT.