Search results

A long overlooked an missing feature, the range/rate tapemeter power/signal failure light has been added. You will see this light up as of right now under the following conditions: Tape meter loss of AC power (<85VAC) or DC power (<20VDC) PCMTEA 512KHz timing signal loss Rendezvous radar range...

Yeah this was an accidental reversion that's being fixed. https://github.com/orbiternassp/NASSP/pull/1105

These are the CLI steps for Git for Windows: https://gitforwindows.org/ 1) Install git for Windows. MAKE SURE THAT WHILE YOU ARE INSTALLING GIT, WHEN IT ASKS YOU WHAT TO DO WITH LINE ENDINGS, YOU TELL IT TO LEAVE THEM ALONE. THIS IS NOT THE DEFAULT OPTION. We are NOT a cross-platform project...

Both cases are a lot of fun! There are different rescue cases of course depending on the type of abort.

This is an orbiter limitation, you wont be able to see the LM until about 60nmi unfortunately. The octal for the LM prevents it from searching before a specified time and therefore prevents alarm codes.

@Max-Q 👆

Thanks to @Max-Q and @indy91 we have an "historical fiction" mission based on the plans for an Apollo 2 flight! "After Gus Grissom and his crew successfully took the Apollo CSM aloft for the first time on Apollo 1, the next step on the road to the Moon is a manned test of the LM. Apollo 2 will...

I just did all the tests everything was correct, my only guess is you missed something perhaps? This should be the first powerup if it is following Apollo 9's procedures.

I will need to set this Apollo 2 up before I can load that save to check, in the mean time I will check the current Apollo 9 and see if there is anything amiss.

Do you have a save around this time I can verify?

Then the numbers should be correct, I am guessing a procedural error then. I would need a save to check though

Did you use the activation from Apollo 9 when you did those checklists?

Which LM software is being run? Those numbers did change mission to mission.

I will also go on record as saying you are one of the few to fly the 13 failure mission, and also find bugs/inaccuracies! So don't sell yourself short!

Adding to this, on some transcript research, it appears missions as early as Apollo 8 also switched to MIN IMP before CM RCS firing. We don't have entry checklists for these missions so this got missed. I plan on adding that step to entry checklists and it should prevent this. Apollo 8...

I am getting the same behavior, configuration looks just fine. @indy91 could this be something to do with the CMRCS changes we made?

It also could be antivirus attacking dll's.

The way the scenario loads/saves the checklist has always been an annoying enigma. So its hard to diagnose why that went ahead without an update or editing the scenario (unless you accidently started a rendezvous checklist in the past then went back to flight plan or something. First P57 after...

Did you by chance update NASSP at all during this flight? Sometimes when checklist updates are pushed, they change the "state" and this sort of thing happens. I am getting the same behavior here in your scn so it wasn't your fault. Seems as the save thinks its in a different spot when finishing...

Was this from a fresh launch or a pre saved scenario? The pre saved ones the checklists can start in weird places a edits are made/pushed. If not, it sounds like you may have skipped something or accidently pushed it to the wrong location. I am happy to take a look/get it back on schedule.