I have encountered some problems with certain aircraft that use an auto-trim system, as is common in some fighter jets.

As soon as I activate the autopilot in these aircraft, only the vertical mode works, but the lateral mode does not. When I activate the lateral mode, such as HDG mode, the aircraft would spin wherever it wanted and eventually ended up in a dive.

I tried a lot of different things over time and eventually discovered that the autopilot worked perfectly as soon as I unplugged my Throttle Quadrant (X56) from the USB port, but not when it was connected. At first, I thought, "Oh no, my throttle, which was barely used so far, is defective." To confirm that, I created a test profile in MSFS24 in the control configuration and assigned the axes and buttons directly through MSFS24 instead of using AAO. And then everything worked perfectly fine. I also ruled out any double assignments of the axes, since the profile I usually use is completely free of any assignments, as I try to find a solution for everything in Axis and Ohs, which usually works well.

Has anyone else ever observed such a phenomenon in relation to auto-trim systems and AAO? For all other aircraft, AAO works perfectly, and I encounter no issues.

1 hour ago, Skydiv100 said:

Has anyone else ever observed such a phenomenon in relation to auto-trim systems and AAO?

Same with the PMDG autopilot - when you make incorrect assignments. If the problem manifests or not depends on what you assign in AAO. MSFS in general prefers the Axis Events from second selection box from the top over the Axis Variables in the first selection on the axis dialog. Some aircraft even have custom logic implemented for some axis, and you need IEs, BVars or scripts. This must be investigated for every affected aircraft.

Also, you must make sure that the same axis aren't assigned automatically to other things in MSFS. This is especially tricky in MSFS 2024.

What AAO is allowed to do over SimConnect is not the same as what the MSFS controller assignments do. Some items may have similar names, but they are not related - those are two completely different "logics", operating in parallel - and thus causing conflicts.

Edited June 7, 2025Jun 7 by Lorby_SI

Example: Axis assigned like this don't cause problems with the PMDG AP. The most common axis events are duplicated in the very first group of the event selection treelist, so you don't have to search for them

Apologies for the late reply — I had simply forgotten about this topic over time.

You were absolutely right: AxisAndOhs was not related to the issue at all. It turned out that any SimConnect connection was causing the problem, completely independent of AxisAndOhs.

Thank you again for your insight back then!