• ORBITER-FORUM will be temporarily closed at 2026-07-23 18:00 UTC while we complete some OF maintenance tasks. The amount of downtime is expected to take up to one hour, but probably less.

Search results

  1. indy91

    Apollo 12 - Experiences, Odds & Ends

    Oh that's what you mean. It's one of those things that only works in the vessel you are currently in. So if you want to have the CMC (or even IU) state vectors you need to switch to the CSM, open the RTCC MFD there and press the TLM button then. MPT on or off doesn't matter in this case.
  2. indy91

    Apollo 12 - Experiences, Odds & Ends

    Vector Comparison Display and Vector Panel Summary go hand in hand. On the vector panel summary there is a TLM button to get all the telemetry state vectors from the current vessel. That only makes a time tag appear on the page for each vector. I think in reality this was an automated process...
  3. indy91

    Apollo 12 - Experiences, Odds & Ends

    If the initial configuration in the LM MPT is "L" and not "CL" then I am out of ideas. Maybe something Apollo 12 specific. I can take a look at the scenario.
  4. indy91

    NASSP PGNCS surface landmarks for tracking

    The line I quoted would be in the Orbiter.log file, not one of the mission configs. Anything with "mission" in there? I am quite sure your mission has been using Artemis instead of Comanche from the beginning, but I have no idea why that would be. You can fairly quickly check. Just start Program...
  5. indy91

    NASSP PGNCS surface landmarks for tracking

    So if you load the scenario you posted, do you get program alarms and a restart or not? And concerning the issue with the CMC software version it seems to use, looking at your scenario I am quite convinced that it has been using Artemis instead of Comanche for all of the mission. There are a...
  6. indy91

    NASSP PGNCS surface landmarks for tracking

    When I load that scenario I am not only getting a program alarm but also a restart. And the program alarms are quite bad. I've only ever seen this behavior when loading a scenario that was using a different AGC software version than it currently uses. Are you getting that behavior, too, when you...
  7. indy91

    NASSP PGNCS surface landmarks for tracking

    Hmm, sounds like you might already have a wrong alignment. But that could only really happen if you started P11 not at liftoff (automatically) but a long time before that with V75. Does the mission time in the computer (V16 N65) align with the mission timer? If yes it must be something else. I...
  8. indy91

    Apollo 10 with NASSP 8 beta rev 1822_issues

    What kind of DV did you get for MCC-1? I think the calculation can taken longer if it is a larger DV.
  9. indy91

    New Release D3D9Client Development

    I was working on labels for Earth landmarks and noticed that the DX9 client seems to read the color of the Label.cfg file wrong. Here the comparison: Default: DX9: The RGB values for Airports are 255 255 128. That should be that yellow tone, not cyan. Is some DX9 client code using a...
  10. indy91

    Apollo 12 - Experiences, Odds & Ends

    Are you sure that is something you want to do? TIG and DV of your LOI-1 maneuver will be different if you do MCC-4 or not. So the resulting orbit of a LOI-1 maneuver that was calculated with MCC-4 taken into account will be different if the trajectory suddenly has no MCC-4 maneuver. What gets...
  11. indy91

    Apollo 12 - Experiences, Odds & Ends

    The propellant masses are probably not exactly correct. Those masses are stored in the MPT, but they are separate from the total spacecraft masses and are not taken into account for any trajectory calculation. And most importantly they are not updated automatically together with the other masses...
  12. indy91

    NASSP PGNCS surface landmarks for tracking

    I'm working on the surface markers in the new style for the Earth. Should be coming soon!
  13. indy91

    Apollo 10 with NASSP 8 beta rev 1822_issues

    The CDH maneuver is nominally 0 ft/s. And even the actual CDH maneuver won't be very large, a few ft/s at most, but in some random direction (mostly radial). So the normal technique for it is basically like residual nulling and not like a longer maneuver like CSI. That's why you wouldn't...
  14. indy91

    Apollo 10 with NASSP 8 beta rev 1822_issues

    R2 in V90 (the Ydot) is your out-of-plane velocity relative to your target. What you are trying to do is get the out-of-plane movement as small as possible without having to perform a dedicated plane change maneuver. That's why you use the CSI time and then load as DVY in N81 the negative (sign...
  15. indy91

    Apollo 12 - Experiences, Odds & Ends

    I am not sure yet, no. Changing the value from 60 to 56° in the RTCC only would give us a correct extraction roll, but separation would still be off. Changing the way our LM is actually rotated in the SLA as well would give us yet again 4° error in both sep and extraction roll.
  16. indy91

    Apollo 12 - Experiences, Odds & Ends

    Hmm, I'm not sure why it is 56°, because I am fairly sure the LM is rotated 60° in the SLA. Maybe there is a tolerance and Apollo 11 and 12 both simply had 56°? From Apollo 13 on the procedure to calculate the extraction attitude is R22 (roll for Noun 22) = 300° -R20. In the separation attitude...
  17. indy91

    Apollo 10 with NASSP 8 beta rev 1822_issues

    Ok I tried the earlier scenario where you are just entering P32 and everything worked fine. I checked the later scenario where you already have the program alarm and the TPI time (Noun 37) is actually all zeros. So it must have been an error with entering that time. With P20 and P32 running at...
  18. indy91

    Apollo 10 with NASSP 8 beta rev 1822_issues

    Moving the TPI time would be a last resort, something seems to have gone quite wrong. Can you give me the scenario before or when the program alarm has just happened? 604 alarms really shouldn't happen, there should be plenty of time between CDH and TPI. CDH usually happens an hour after CSI, so...
  19. indy91

    Apollo 10 with NASSP 8 beta rev 1822_issues

    The mission techniques document has this to say about update limits: "3.4 LM AND CSM STATE VECTOR CORRECTION LIMITS DURING RDZ NAVIGATION The LM and CSM differential state vector correction limits (RMAX and VMAX) in the LGC and CSM will be set to 2,000 feet and 2 feet per second. However, the...
  20. indy91

    Apollo 12 - Experiences, Odds & Ends

    Yeah some missions needed to do a larger plane change during TLI, especially Apollo 8 and 12, so you get a large yaw angle at cutoff. The burn time difference seems large, but the DVC error seems like a usual value. The TLI PAD in the RTCC MFD uses an outdated "simulation" of the TLI burn. The...
Back
Top