OHM BaseSyncMFD 3.3 for Orbiter 2010

[BenSisko]

I'm just noting an issue in BaseSync for Orbiter 2010 and BaseSync for Orbiter 2016. Attempting to align orbital path with Cape Canaveral (Closest passage, Direct) as target when running the DG Mk4 in orbit scenario, BaseSync indicates the alignment burn should be in Normal attitude (PLC+) but the burn should be Anti-normal (PLC-). I've been able to reproduce this with v2.8, 3.0, and 3.1. Is it a bug or am I doing something wrong?

 

[ADSWNJ]

V3.2 just released as a compatibility version for Orbiter 2010. Technical change only: this version no longer complains if you don't install the ModuleMessagingExt add-on (though please do install it, as it's needed to let this MFD talk to others - e.g. Glideslope).

 

[ADSWNJ]

V3.3 released, to fix a bug with the BurnTimeCalculator data handshake. Credit: Enjo for spotting this.