Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

C172 (steamer) autopilot wants to kill me

Featured Replies

Is there any reference for how this thing works? I got it to work correctly once, but if I change modes, it goes mad and rolls the trim to max up.

I am really enjoying this sim. But it has some amazing quirks.

I've used the classic 172 quite a bit but have never had it run away with the trim like that. Are you using active pause during your flights? The autopilot will continue to move the trim while the sim is paused, which causes abrupt attitude changes when resuming the flight. Are you dialing in your altitude, selecting "V/S," and keying in nose up/down with the buttons?

Edited by Hyperfocal

Same here.

Not only the Cessnas.

The trim may go 100% / AP made the aircraft bank in aerobatic style...

didn't pause...just very buggy...

1 hour ago, punder said:

Is there any reference for how this thing works? I got it to work correctly once, but if I change modes, it goes mad and rolls the trim to max up.

I am really enjoying this sim. But it has some amazing quirks.

I had that problem regularly before I figured out a few do and don'ts. As noted before don't use active pause. The AP is sensitive and any wrong move while it's engaged will throw you out of control. I have bumped the joystick by accident causing the AP to go crazy. Yesterday I accidentally tapped the right aerilon trim key while in heading and altitude hold modes and the 172 immediately dived to the right and into the ground with no way to control it. On initial climb I use FLC mode in the G1000 instead of Alt-VS which seems to help.

 

 

Edited by desbean

I've had autopilots try to kill me and then turn back to working normally after manually trying to trim some

Also engaging the autopilot with settings far off (like a completely different heading or altitude) sometimse make the autopilot try to kill you It's best to make sure the selected altitude and heading are the same, and change them after enabling the autopilot.

I've had the AP in the SR22 and the DA40 go nuts on me a me a few times, sometimes after doing well for a quite long flight. I just think the AP is a little bugged.

James

 

7 minutes ago, Phantoms said:

I just think the AP is a little bugged.

none of my AP are bugged, they all work find and specially in the C172 classic, it all has to do with conflicting keyboard and controller assignments.

Ryzen 5 5600X - Noctua U12A, 32Gb Vengence, Sapphire Pulse 5700xt, WD Black SN750 NVMe SSD

30 minutes ago, FPStewy said:

none of my AP are bugged, they all work find and specially in the C172 classic, it all has to do with conflicting keyboard and controller assignments.

This has been my experience, too. As much as I love being able to assign multiple functions to individual controls, I found myself with some very bizarre autopilot behavior that fixed itself when I undid some of my stacked control assignments.

I was seeing runaway nose-down trim behavior that I had caused by assigning flight controls to a game pad that were already assigned to my joystick. I didn't notice it until I started flying an aircraft with an autopilot.

AMD 7800X3D, RTX 4090, 42" LG C3 OLED 4K TV/Monitor

Not sure one can call it bugged but it does have a few shortcomings in the lateral nav modes. Capturing a VOR, ILS or Lnav course can take you on a Jiggy ride at times.

2 hours ago, FPStewy said:

 

none of my AP are bugged, they all work find and specially in the C172 classic, it all has to do with conflicting keyboard and controller assignments.

I believe this may be a key point.  I had the 172 (G1000) go full trim up on my first takeoff.  I had not taken time to diligently go through the setup of my flight controls.  Since doing so I have not had an additional trim issue.

Edited by fppilot

Frank Patton
Corsair 5000D Airflow Case; MSI B650 Tomahawk MOB; Ryzen 7 7800 X3D CPU; ASUS RTX 4080 Super; 
NZXT 360mm liquid cooler; Corsair Vengeance 64GB DDR5 4800 MHz RAM; RMX850X Gold PSU;; ASUS VG289 4K 27" Display; Honeycomb Alpha & Bravo, Crosswind 3's w/dampener.  
Former USAF meteorologist & ground weather school instructor. AOPA Member #07379126
                       
"I will never put my name on a product that does not have in it the best that is in me." - John Deere

When canceling IFR and switching from NAV to HDG on the autopilot that takes, but then Alt hold all of a sudden goes bonkers even though it was just working. Setting the Alt and clicking it off/on still doesn't fix it. Trying to adjust ALT to higher or lower and then setting VS (adjusted to 500) doesn't work either. This just tonight in the SR22. I've had similar in the DA40. Wondered if it might have been the fact that I usually run a map (either LNM or FSFC) and  TrackIR, but tonight I confirmed it happening without either of those running.

Edited by Phantoms

James

17 hours ago, FPStewy said:

 

none of my AP are bugged, they all work find and specially in the C172 classic, it all has to do with conflicting keyboard and controller assignments.

I would like to add that I haven't changed any of the keyboard assignments. The only assignments I have are basic flight control and camera for the joystick, throttle and pedals. The xbox controller I removed all but the camera controls and assigned the A button to toggle the drone camera. That's it, no conflicting command assignments. I use the mouse to click the buttons on screen to handle all the AP functions.

James

  • 10 months later...

I've just started having a go at the autopilot in the 172 and at the moment it's the blind leading the blind lol. I'm starting to think that ISIS had a hand in programming the AP.

1 hour ago, Sedici65 said:

I've just started having a go at the autopilot in the 172 and at the moment it's the blind leading the blind lol. I'm starting to think that ISIS had a hand in programming the AP.

Are you messing around with the AP while still on the ground?  That seemed to be part of my learning curve back in September.  I believe its OK to preset your heading, or course, but I now stay away from the HDG or NAV switches and ALT functions until I am up off the airport and established.  See if that helps.  Also, do not use the MSFS Active Pause function for more than a minute or so. 

Edited by fppilot

Frank Patton
Corsair 5000D Airflow Case; MSI B650 Tomahawk MOB; Ryzen 7 7800 X3D CPU; ASUS RTX 4080 Super; 
NZXT 360mm liquid cooler; Corsair Vengeance 64GB DDR5 4800 MHz RAM; RMX850X Gold PSU;; ASUS VG289 4K 27" Display; Honeycomb Alpha & Bravo, Crosswind 3's w/dampener.  
Former USAF meteorologist & ground weather school instructor. AOPA Member #07379126
                       
"I will never put my name on a product that does not have in it the best that is in me." - John Deere

11 hours ago, fppilot said:

Are you messing around with the AP while still on the ground?  That seemed to be part of my learning curve back in September.  I believe its OK to preset your heading, or course, but I now stay away from the HDG or NAV switches and ALT functions until I am up off the airport and established.  See if that helps.  Also, do not use the MSFS Active Pause function for more than a minute or so. 

It actually turned out to be the drift in the left thumbstick of my Xbox controller, a bit of deadzone sorted it. So turns out my AP isn't possessed after all. It seems like an obvious thing to try now with hindsight, I could've saved myself a lot of swearing.. Anyway, thanks for the reply 👍

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.