3 hours ago, Bobsk8 said:

have never turned on  AP prior to takeoff and in the real world, I don't know any pilot that would do that.

 

2 hours ago, Bobsk8 said:

Even with an Airliner, they can't engage the AP until they are over 600 Feet AGL> 

When I worked around with the AP and NAV, VS, and FLC was early on in MSFS when I was studying airraft and systems while sitting in a parked aircraft.  The times I lost control when airborne and I engaged the AP were in those cases.  I learned and then after studying began returning the home screen and starting fresh before flying.  No more occurances.

2 minutes ago, fppilot said:

The times I lost control when airborne and I engaged the AP were in those cases. 

Which would support the notion that the AP code is still flakey in MSFS..

WT to the rescue?? 😉

19 minutes ago, Bert Pieke said:

I am still not quite there... if that is what was happening, the autopilot should disconnect. 

What I encounter, is the AP staying connected, but flying me into a spiral dive.

When this happened to you, did the AP disconnect?

A good question - it did not disconnect. So for example I would look at left wingview (NUM4) and now with hindsight I recall that each time I used one of the hotkey cockpit cam numpad hotkeys it would induce a dive. I know that now but didnt make the connection until I saw what @TacomaSailor said.

To recover from the dive I had to turn the  AP off (SHIFT+ALT+Z)

I guess I cant really explain it but the fix worked, after deleting the mapping to the primary control surfaces I can use the numpad view keys as much as I want to enjoy wingviews and the AP works as smooth as butter. In fact I made sure of this by droning around for 2 hours before posting on here!

Edited June 4, 20215 yr by ThrottleUp

59 minutes ago, ThrottleUp said:

if that is what was happening, the autopilot should disconnect

 

1 hour ago, Bert Pieke said:

Which would support the notion that the AP code is still flakey in MSFS

👍

3 hours ago, ThrottleUp said:

A good question - it did not disconnect.

The last systems update mentioned that attempted autopilot override would be compensated by the autopilot, up to the disconnect point.

Edit:

Just tried the C172, and the Bonanza, and they actually disconnected when forced... so this may be working now..

 

Edited June 4, 20215 yr by Bert Pieke

It also helps to turn off the autopilot in any Just Flight aircraft before logging them out as if you quit out of something like the Piper Arrow with the AP turned on the JF feature which remembers the last state seems to really mess with the AP the next time you jump in that plane .

Edited June 4, 20215 yr by Glenn Fitzpatrick

37 minutes ago, Glenn Fitzpatrick said:

It also helps to turn off the autopilot in any Just Flight aircraft before logging them out as if you quit out of something like the Piper Arrow with the AP turned on the JF feature which remembers the last state seems to really mess with the AP the next time you jump in that plane .

This may have something to do with my experience as well.. Since SU4, the C172, and Bonanza actually seem much improved, so it may just be some fine tuning that is missing 🙂