I have been flight simulating for over 20 years and have used many different autopilots. I have this problem with both msfs 2020  (su16) and 2024 (beta).

The only autopilot that works now is the garmin g1000 all the other autopilots when I make my flight plan and take off and turn on the any other autopilot ( garmin 530 or 430  or any other one except the g1000) the plane turns right and dives

down to the ground. I have uninstalled both sim's and reinstalled both. Emptied community folder and it still does the same thing. Hopefully someone can help me with this out of idea's. 

thank you 

You have tried to fly in safe mode and see if it behaves in the same way or what is the same you could manually rename the community folder.

1 hour ago, thauser said:

I have been flight simulating for over 20 years and have used many different autopilots. I have this problem with both msfs 2020  (su16) and 2024 (beta).

The only autopilot that works now is the garmin g1000 all the other autopilots when I make my flight plan and take off and turn on the any other autopilot ( garmin 530 or 430  or any other one except the g1000) the plane turns right and dives

down to the ground. I have uninstalled both sim's and reinstalled both. Emptied community folder and it still does the same thing. Hopefully someone can help me with this out of idea's. 

thank you 

What type of controllers are you using? Suggest checking for binding conflicts. As a quick experiment, once up in the air and flying level, if you unplug your controller(s) USB connection(s) and just fly using the mouse and the keyboard, does the same problem happen when you turn on the AP?
Would also not use any addon third party liveries until you figure out what is going on.
I would also check that any unwanted Assistance Settings have not been turned on somehow, e.g., AI AUTO-TRIM, AUTO-RUDDER, etc.

Al

 

Edited October 12, 2025Oct 12 by ark

Was going to type the same thing as the comment above. Do that - most people find it’s a peripheral issue when it’s weird stuff like this. 

thanks for the suggestions . I will try some of those and report back. Again thx

Yeah I'd say a controller axis etc.  I find MSFS to be more sensitive to AP disengagements vs prior sims.  But I guess irl you can override the AP as well fairly easily.

thx everyone i tried all the suggestions and it didn't help. the thing odd about this the garmin g1000 works perfect. Maybe I am not activating a certain button. here is what I do.

- set my altitude

- set my vs

- go to nav. mode

- make sure FD is active

- make sure I am in GPS or FMS mode

Is there something I am missing to do. Same thing I do with the g1000 and it works. Right now if I want to do a long flight I can only fly a plane with g1000 autopilot in it.

still stumped thx

4 minutes ago, thauser said:

make sure I am in GPS or FMS mode

Make sure your GPS is up to date.

Al

All ok here:
C172
MSFS2020

I use FSUIPC7.

 

Edited October 12, 2025Oct 12 by vonmar

12 hours ago, thauser said:

I have been flight simulating for over 20 years and have used many different autopilots. I have this problem with both msfs 2020  (su16) and 2024 (beta).

The only autopilot that works now is the garmin g1000 all the other autopilots when I make my flight plan and take off and turn on the any other autopilot ( garmin 530 or 430  or any other one except the g1000) the plane turns right and dives

down to the ground. I have uninstalled both sim's and reinstalled both. Emptied community folder and it still does the same thing. Hopefully someone can help me with this out of idea's. 

thank you 

I hate to point it out, but NONE of those are autopilots. The G1000, 530 and 430 have no autopilot functionality whatsoever.

4 hours ago, somiller said:

I hate to point it out, but NONE of those are autopilots. The G1000, 530 and 430 have no autopilot functionality whatsoever.

While the different GPS/FMS units are not autopilots, they may make use of (communicate with) different autopilot implementations. For example (based on my admittedly limited understanding) the sim's current GNS530 GPS makes use of a "managed mode" AP developed by Working Title. In this case basic AP K_event commands (e.g., AP_NAV1_HOLD) get intercepted by a management layer of software that decides on how best to respond to that command.  On the other hand, the current version of the TDS GTNs communicate directly with the standard (not managed) Asobo autopilot (although TDS is developing a new "managed mode" AP). Whether or not these different AP implementations have anything to do with the OPs AP problem I don't know. I would expect however that since the current G1000 and GNS530 are both WT developments they would make use of similar APs. 

Al

Edited October 12, 2025Oct 12 by ark

On 10/12/2025 at 1:27 PM, somiller said:

The G1000, 530 and 430 have no autopilot functionality whatsoever.

That's strange, I was flying a C172 G1000 IRL just yesterday afternoon, and the G1000 most definitely had an autopilot built into it.

I take your point that they are GPS units but the fact that the G1000 has an AP built in it in the sim and the others don't, may well be at the heart of the OPs problem.

Edited October 13, 2025Oct 13 by JYW

On 10/11/2025 at 11:44 PM, thauser said:

thx everyone i tried all the suggestions and it didn't help. the thing odd about this the garmin g1000 works perfect. Maybe I am not activating a certain button. here is what I do.

- set my altitude

- set my vs

- go to nav. mode

- make sure FD is active

- make sure I am in GPS or FMS mode

Is there something I am missing to do. Same thing I do with the g1000 and it works. Right now if I want to do a long flight I can only fly a plane with g1000 autopilot in it.

still stumped thx

You actually engaged the AP master though?  Can you give an example of what plane this is happening on?