Search results

I've quickly tried MR-3, very impressive. Love the sound effects. I wonder, how does the periscope work using the Orbiter API? Does it just have a different FoV or also a variable view direction which is different from the main window view. I just wonder if you found a solution that can be...

In terms of orbital mechanics, if you want to go from a 51x170 orbit to a 13x60 orbit then of course the maneuver is only possible between 51 and 60 NM. If you perform the maneuver at 60NM then you will always null the radial velocity and that is the only way to achieve the 13x60 orbit. But if...

That screenshot is from before TLI. There is no separate S-IVB vessel at that point. So you need to use the name of the combined Saturn (with CSM), which should be "America". After CSM/LV separation, if you want to uplink anything to the IU, you need to use the name of the separate S-IVB which...

If you want to find out when exactly the APS lost its propellant, you can check in the scenario editor, under propellant. There are 11 tanks, tanks 10 and 11 contain up to 143 kg, those are the APS tanks. Tank 10 is the empty one, tank 11 is still at 63% in your scenario. This is actually one...

One APS module seems to have run out of propellant. That's weird, the other tank still has 63% of prop. Maybe this was caused by too much time acceleration, it can move around in the attitude deadband even during 10x. I'm usually monitoring the attitude rate and if it gets too much I go back to...

Not a typo in NASSP, the switch says LM/CSM. Must be a typo in your source. The switch affects the behavior of the SCS Auto TVC. It is set to LM/CSM for launch, at least for heavy CSMs, for the following reason given in the AOH Volume 2: "Provides reduced gain for SPS thumbwheel control of SCS...

The only way to do it right now is to edit the T-4h scenario. Find the line: MISSNTIME -14400 That is minus 4 hours of mission time. There was a delay of exactly 2:40h, so you need to change that to. MISSNTIME -24000 if my math is correct there. Sadly we can't do "in-sim" countdown holds and...

No that is LOPC-1. LOPC-2 is after rendezvous and getting rid of the LM. But targeting wise it should be very similar. "The CSM performs a second plane change on rev 61 to increase lunar surface photography coverage." What I did when flying Apollo 12, which also did a LOPC-2 for photography...

Someone from the (former) SSU team can probably answer this better, I can't really remember. I actually played around with the code for this and I might have implemented roll angle of 0 just in my local copy, but it never got to a stage where I would have called it good to be integrated into...

Ah sorry about that. A few days ago someone flying Apollo 12 tried to use mode 6 (powered descent simulation) of the Lunar Descent Planning Processor (LDPP), which is not available yet and it overwrote the time of landing with NaN, which was a bit difficult to revert without scenario editing. So...

As it turns out, this is incorrect. For Apollo 14 they added a new program to the CMC, Program 24, Rate-aided optics. In that program, and in that program only, is the CMC allowed to drive the optics in manual mode. It helps the fact that sometimes you have to command fairly large optics rates...

Yeah the optics zero switch can catch you out. After a period of having optics powered off you also need to cycle the switch from zero to off to zero so that the CMC knows that it's being zeroed. And it is possible (but unlikely) that the real position of the optics (shaft and trunnion angles)...

There is multiple things going on here. The optics system of course has limits in trunnion and shaft angles, so it's normal that you can't move it beyond a certain point. I'm starting to think this is a bad idea. I have conflicting information about what they intended to do on the actual...

A video might help yeah. But you did say you are getting a program alarm (PROG light goes on) at some point. When you check V05 N09, what is the alarm code? And at what point in the procedure do you get the alarm?

How is the state vector after insertion this time? V82 showing goods things? I am pretty sure you are doing something not quite correct after getting the 405 program alarm, because in your T+38min scenario P52 worked perfectly fine. So let's take it step by step. You are getting to the step in...

The Apollo 7 MCC has been reorganized a bit. Sadly I had to break old scenarios for that. The mission scenarios that come with NASSP have of course been fixed and if you have just launched, scenarios saved before the first state vector uplink at T+56min are also fine. Otherwise I would suggest...

As I said getting that 405 program alarm in P52 can be quite normal even if you did nothing wrong, just some bad luck with star availability at the time. Aside from the state vector being off I can't seen anything wrong in the scenario you posted. P52 works as expected. "Apollo 7 launch", do...

Ok the CMC state vector is indeed bad somehow. No idea why yet, but the uplink later would fix that. You did let it uplink the state vector at T+56min, right? That could tie into the next issue. The CMC checks if the Earth is in the way of stars or if the star is within 5° of the horizon. And...

That is probably caused by RCS firing. Time acceleration doesn't go well together with any vehicle trying to fire thrusters. When you are still attached to the S-IVB then the S-IVB will perform the attitude control. With that you can safely use 10x, but I don't think more. After getting away...

Aha! The NASSP releases do have a file that belongs in there that you for some reason don't have or don't have anymore. So just check in the last NASSP release for the 001131.elv file and put it in there. That should do it.