Problem AMSO docking playback

[Bodrius]

Hi all...

I was trying to make a video showing the Apollo CSM/LM docking and extraction with AMSO, so I made the docking and recorded it. But when I play it back the CSM does not undock from the SIV and the full stack turns around and follows my previous movements, as if it was the CSM...

Any idea what's going on or how can I fix this?

 

[Lucy]

You mean the staging doesn't happen? Odd, but it might have something to do with how AMSO's autopilots work. Not entirely sure.

If you record a launch from pad - orbit and play it back, does it stage properly then?

 

[Nemoricus]

It sounds like AMSO doesn't support extraction in replays. If that's the case, then there's not a whole lot that can be done about it. Make one replay up to TD&E and another from after extraction to splashdown.

Send the AMSO team a note as well so that they will know about this.

 

[tblaxland]

I was trying to make a video showing the Apollo CSM/LM docking and extraction with AMSO, so I made the docking and recorded it. But when I play it back the CSM does not undock from the SIV and the full stack turns around and follows my previous movements, as if it was the CSM...

The CSM is not docked to the S-IVB. Up until the moment of separation, the whole stack is one vessel, as far as Orbiter is concerned. When you separate using AMSO's commands, AMSO uses its internal code to spawn separate a S-IVB vessel (and SLA panel vessels too) and those bits of mesh are removed from the CSM vessel. Unfortunately, this separation event is not recorded in the playback file and so when you play it back, Orbiter just plays the movements of the CSM as the movement of the whole stack, since they are the same vessel as far as it knows.

As to how to fix it, this is something that can only be resolved by the addon developer, I think, using the VESSEL2::RecordEvent and VESSEL2::clbkPlaybackEvent functions.

 

[Tommy]

AFAIK, the flight recorder only records flight data for vessels in exist at the moment you hit the record button, so even if a vessel used the playback to record the spawning, the new vessel wouldn't have any .atc or .att info, and would just drift. You'll experience a similar problem with EVA also, most likely.

By the same token, only vessels listed in the scenario file, and that have info in the flights folder, will "playback", any vessel without flight data is available for normal flight. Someone used this loophole to do a "race this DG around Canaveral" scenario.

Incidently, deleting vessels is also not recorded, the vessel will remain in the playback and just drift. DGIV cargos and UMMU have some weaknesses because of this when it comes to recording, as will the new UCGO I suspect.

 

[the.punk]

I know this isn't exactly what you've asked for but I wouldn't use the flight recorder for making videos. Maybe a program like fraps.

 

[Lucy]

Personally I record a scenario with the flight recorder and then playback with Fraps so that I can concentrate on the flying and camera work separately.