Recent content by mnurick

Been reflecting on the insane Steel Battalion mech controller and wondered if anyone here has thought about or investigated what it would take to fully recreate a physical Apollo Command Module console and plug it into Orbiter? Sounds crazy, but I feel like this group is also crazy enough to...

Thanks Indy! Noob mistake on the RTCC. Thanks for the fix and glad you found the bug.

Hello again Indy! For the RTCC MFD, I navigated to the PAD menu, selected Lunar Ascent PAD, selected Columbia as the target, and hit calculate. Also, here is the MCC snippet of the save file, where you can see the zero'd out GET and dV data MCC:ProjectApollo\MCC STATUS Landed Earth POS...

I'm on the latest Orbiter Beta and NASSP 8.0 release. Regardless of save file including stock Apollo 11 scenarios, when on the moon preparing for liftoff, MCC pad data is coming with blank liftoff times. I then turned to the RTCCMFD to calculate the burn data manually, and liftoff time also...

Hi Indy. Thanks again for the detailed reply and context. Really helpful! And to your question on the build of Orbiter I'm running... I'm running Build 28 v.160828 Let me know if you'd recommend running an alternate build. The S-IVB issue is strange. Definitely never touched the save file...

Indy, to the rescue again! Thanks! I tried copying a healthy Columbia DSKY and AGC section from the stock scenario included with NASSP closest to my stage of the mission (rendezvous prep), updated the clock and state vectors and will update alignment as well, but it fixed the error. So there is...

TL;DR Uplinks don't work, when they do, they result in opr err, and P00 causes the comp acty light to stay on. AGC seem to be a bit messed up in my CM. LM appears unaffected. MCC uplink initially works, but then I get an opr err during uplink. I tried a P00, but then the comp acty light came on...

Likely human error then. I started at T-4hrs to launch, and have used time acceleration up to 20x. I really thought I nailed the mark on the LGC clock initialization in the LM, but possible my mouse pointer keystrokes were a bit off at 1am. Serves me right for skipping rest periods. Thanks again!

Strange. I didn't touch the save file code. I'm running Orbiter 2016 and NASSP 8, whatever were the latest builds as of a month ago. Huh! Off relative to what? Is that human error on my part? Or is the virtualaAGC pegged to Orbiter time? And huge thanks again for helping me troubleshoot...

Landing radar is definitely powered. But let me run the procedure again and check to see if its actually doing anything. Will report back after I get home from work tonight eastern time. But I do recall the Range Alt indicating an altitude of ~45,000 ft when I begin PDI. But I'm starting to...

Thanks for your reply. I'm seeing that 6.7 nm stat in the stock Orbiter MFD (which also states my pre-burn orbit at roughly circular 60 nm). I never use this view, but since I find myself crashing on the moon during PDI before I even reach pitchover, I'm digging for answers!

Hello! I’m performing a DOI burn from ~60 nm orbit following the values on the MCC P30 pad changing my velocity ~70 FPS. Which all seems accurate. And yet after the burn and nulling all residuals my periapsis is 6.7 nm. Far too low for PDI. What do you think is happening? Thanks for your help!

Thanks!

I’ll also try the rtcc method you mentioned next time. Thanks again! Loving this experience!

Turns out it was a time acceleration error throwing off the altitudes. A fresh scenario and patience fixed the issue! Thanks for the offer to help.