It is happening in more than one plane and it happens every session.
I have. The reply was unfortunately fully automatic. Given my track record with Microsoft when it comes to tickets, this will take a while.
Would you be a bit more specific, please? What do you mean by “reset the session”? Ending my flight and starting a new one yields exactly the same behavior.
Also, engaging the autopilot’s modes in a different order as well as engaging the AP first, then the modes, does not change the outcome, unfortunately.
It happens in all planes I tried (list see above) and in every session. It is perfectly reproducible.
Sorry I cannot provide any further help. They all work fine for me. Do you happen to have any controllers connected to your computer?
I appreciate the video and that it seems to be working on your system. Mine shows a different behavior unfortunately.
If you’re using controllers, try and disconnect them and see if it still happens using KB/Mouse only. Variability is the only factor you can control now.
1 Like
Everybody, thank you for your advice and help. @CasualClick pointed me in the right direction.
The problem persisted even after I reinstalled the machine and ran Steam and MSFS2024 exclusively on it, without any other software installed, save for Google Chrome.
So I started to switch out all attached devices. Turns out, the problem was induced by my CH Flight Stick Pro I’ve been using for years. In all config tools, both on the OS level as well as inside MSFS 2024, the CH was working correctly and flawlessly. However, it induced the autopilot issue somehow, no idea how.
If, and only if, I unplugged it from its USB port, and then started MSFS 2024 and initiated a flight, in my case with keyboard and mouse, the AP worked just fine. Plugging the CH into an USB port while flying on autopilot, the issues came back instantly. May worth to note, my CH Pro Pedals (same vintage as the stick) work just fine with MSFS 2024, did the same testing procedure with them, without any issues.
I just ordered a new (Thrustmaster) stick, let’s see how that works.
1 Like
Nice detective work.
We shall rename you Sherlock!
Enjoy the new stick.
2 Likes
Glad you got it sorted.
In the future and for benefit of readers who find this thread, you may have used this already - but the USB Game Controller Applet in W10/11 is a great first layer detective tool to see if a peripheral is sending uncommanded signals, usually because of potentiometer failure or other contact switch degradation. If you run it , and you see a button, toggle, axis what have you sending uncommanded inputs, that’s a good suspect pointer.
At the moment, I have a similar problem where the lateral mode of the autopilot doesn’t work, while the vertical mode works just fine. As far as I can tell, my USB hardware doesn’t send any commands that I haven’t given, and it doesn’t affect all aircraft. At the moment, it mainly affects aircraft from IndiaFoxtEcho, while I don’t experience this issue with others. Since I haven’t read anywhere else that this is a known problem with these aircraft, I’m initially ruling out that the issue is with the aircraft themselves. However, I have no other ideas either — I’ve tried everything from reinstalling drivers to testing various settings with and without AxisAndOhs. But as soon as I try to use the lateral mode, the aircraft just turns wherever it wants. Sometimes the lateral mode works at the start, but as soon as I switch the autopilot off and later turn it back on, the problem immediately reappears.
Hello.
I hade the same problem, but it is easily fixed.
To activate the NAV, you need to have bott HDG and NAV activated. Do a roll using HDG knob towards the magenta lite, when lined up, deactivate HDG and it will work fine