jrsaez82

Hi! That worked! I followed your startup sequence exactly and now the AP behaves correctly. So in my case, the workaround is: no GPU battery ON inverter MAIN battery isolation NORMAL avionics OFF during startup generators ON after engine start avionics ON only after that no AP mode selected on the ground, only in the air Thank you very much for taking the time to write the full sequence. That solved it for me.

Hi again, Thanks for the detailed reply, I really appreciate it. That makes sense, and it also matches what I have been seeing on my side: the issue appears to be strongly tied to electrical source / bus behavior rather than to autopilot usage itself. In my testing, HDG will not latch on battery power only, it can latch with GPU power, and it drops again when GPU power is removed, so your explanation about newer electrical / amp-flow criteria in X-Plane sounds very plausible. Thanks again for confirming that this is something worth investigating. I bought the aircraft four days ago, and I’m really disappointed not to be able to fly it (unless it’s in manual mode, which is tricky for flights longer than 20 minutes). I’ll keep an eye on future announcements and I’m happy to provide any additional test details if that helps when you come back to the MU-2.

Thanks a lot, that is actually very helpful. - Yes, when I try to enable HDG, it does blink briefly and then does not stay engaged. - Also, you are correct: I incorrectly said APU, but I actually meant GPU / external power. - My test case is with the 4-bladed GNS / Garmin variant. - What I observed is this: 1.- With ther aircraft with on battery power only, HDG does not latch. 2.- With GPU connected (without batteries on) HDG can latch on the ground. And the aircraft powered up, after engine start, HDG can still remain engaged but when I remove GPU/external power, HDG drops out immediately after a couple os seconds. So the behavior really seems tied to the electrical source / bus transfer. I can keep testing and provide a more exact switch-by-switch sequence if that helps, but from my side it definitely looks like X-Plane is dropping HDG right after the command is sent. Thanks again for looking into it.

Hi everyone, I’m posting this here in case another user has already seen the same issue and found a workaround before support replies. I bought the TOGA Simulations MU-2 Marquise v2 for XP12 and I’m having a strange AFCS / HDG / autopilot problem. I want to be clear that I’m not posting this as a “quick question” without checking first. I have already: searched through forum threads read the available documentation watched videos tested different startup sequences reinstalled the aircraft checked bindings and controls and I have already opened a support ticket with X-Aviation After a lot of testing, this is what I have been able to isolate: HDG does not latch on battery power only HDG does latch when the aircraft is powered from the APU HDG can remain latched with APU on, even after both engines are started and the condition levers are advanced to takeoff but the moment I remove APU power, HDG immediately disconnects because of that, the AP becomes unreliable or unusable So at this point it looks less like a normal “how to use the autopilot” problem and more like an AFCS electrical power / bus transfer / plugin initialization issue. I also found some related threads, but none of them gives me a final answer for this exact behavior. Has anyone here seen this? Especially this exact pattern: battery only = no HDG APU on = HDG works APU off = HDG drops Any hint would be very appreciated. Thanks a lot.