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.
I'm playing about with apollo 7 at the moment, quick question a pad comes through for a re-entry at 08:17. I assume this is an abort PAD if needed. How would I act on it, would i use one of the checklists in the MFD from the index as I left the oven on and have to return home.
I also have a question about the PAD at 14:20 for a phasing man at 15:42
I didnt get either a null PAD or a "Second Phasing Maneuver not necessary."
I'm now in the Phasing Maneuver with no pad should i just abort it?
i dont remember seeing one but it's possible i kept a razor eye a good time before and after the pad was due.I'll answer both your questions here.
Yeah Apollo 7 prepared for an early deorbit maneuver, with P30 uplink, deorbit REFSMMAT and Maneuver PAD. I think this is kind of training for the deorbit burn, kind of like Apollo 11 practiced lunar ascent procedures just after landing on the Moon. But it is also for the case they actually had to abort the mission early. It was the first Block II CSM flight and many things could have happened that would cut the mission short. So this was just in preparation for not receiving the GO to continue with the mission. You could fly this of course. If you use the abort option in the CAPCOM menu then it will disable the normal on-orbit updates. It doesn't give you an Entry PAD though, so you have to do without that. You can use the word checklists and the deorbit preparations stuff in the Checklist MFD.
Hmm, that is strange. Can you post a scenario just after the MCC calculation for the second phasing burn should have happened? Maybe it is failing somehow. Did you get a "Thread started" message without a "Thread done" message?
i dont remember seeing one but it's possible i kept a razor eye a good time before and after the pad was due.
thanks indy perfect i now know what the debug menu is for. 1 ft/s between friends is nothing i'm just about to hit ncc1 so will carry on.I think the calculation has already happened (at exactly 14:16h GET) and it concluded that no maneuver is necessary. Maybe you missed the message or for some reason it didn't show up. Actually if I let it do the calculation again (CAPCOM menu button 9 for the debug menu and then 8 for Reset State) it results in a second phasing maneuver of 1.0 ft/s, which is exactly the threshold for deciding if the maneuver is necessary or not. If you want to be on the safe side, just let the MCC redo the calculation like that and perform that 1 ft/s maneuver.
I don´t think I understand properly your question, but may be something related to Orbiter 2016. Markers dissapear under some conditions...stupid question I cant see the other ship in the SCT but can in the magnified SXT in planetarium mode is there a range setting somewhere in orbiter that's stopping this
although i'm now 40 minutes from impact it's a busy little period that last hour. Great fun and helped a lot by STS with his live A7 stream WITH ACTUAL COLD/FLU just like the real crew now thats what I call attention to detail.
el diablo está en el detiail
This is defined (somewhat indirectly) in the vessel's DLL using "VESSEL4::SetSize(double size)". This is also the function that controls how close the camera can get in external view. I don't know the relation between size and how far the marker is visible, but setting "size" to a large enough number could make the S-IVB visible from Mars!That sounds like an orbiter limitation to me, I don't think you can adjust this range without editing orbiter.
ive been doing the same luck and faith but wondered where it's hard codedFor knowing where the S-IVB is when using COAS, I took a note of what stars are around the S-IVB (On the optics) so I know moreless where to look at when using COAS. Then, if I zoom In and Out (Z and X keys or mousewheel on VC), and having luck and faith, the S-IVB marker appears.
(Some luck and a lot of faith )
Ah ok I wondered and I do agree that making it more real stops too much cheating and brings in a little chance. It also is a bit of a treassure hunt so that's good.This is defined (somewhat indirectly) in the vessel's DLL using "VESSEL4::SetSize(double size)". This is also the function that controls how close the camera can get in external view. I don't know the relation between size and how far the marker is visible, but setting "size" to a large enough number could make the S-IVB visible from Mars!