System 60 HDG button: cockpit click behaves differently than AP_PANEL_HEADING_HOLD
-
Hi,
While mapping the Commander 114 System 60 autopilot to external hardware, I found what appears to be an inconsistency between the cockpit interaction and the documented simulator event.
Reproduction
Load the aircraft.
Battery ON.
Avionics ON.
Pitch Trim ON.
Engage the autopilot.
Trigger AP_PANEL_HEADING_HOLD from an external controller.Nothing happens.
However, if I click the HDG button once in the virtual cockpit, the exact same external command immediately starts working.
If I disengage the autopilot and engage it again, the external command no longer works until I click the cockpit HDG button once more.
The issue is therefore fully reproducible.
Investigation
Using the MSFS Behavior Debugger, the HDG button executes:
(A:CIRCUIT ON:54, bool)
(L:var_AutopilotTest, bool) ! and if{
(A:AUTOPILOT MASTER, bool) ! if{
(>K:AP_MASTER)
}
(>K:AP_PANEL_HEADING_HOLD)
}
1 (>O:buttonHeld)During testing I verified that:
CIRCUIT ON:54 is already 1 before clicking the button.
L:var_AP_Heading_EM_readonly is read-only and only reflects the state.
Sending K:AP_PANEL_HEADING_HOLD externally does not reproduce the cockpit behavior.
The first mouse click on the HDG button appears to initialize something internally. After that, external commands work normally until the autopilot is disengaged again.
QuestionIs there any additional initialization performed by the cockpit interaction (for example in the System 60 logic or WASM code) that is not triggered by K:AP_PANEL_HEADING_HOLD?
Or should the simulator event be sufficient to fully reproduce the cockpit button action?
Thanks!