Autopilot turning off mid flight.

[Seth2413]

After update now the AP keeps disconnecting itself and I go into a steep left hand dive which have to manually try and recover from.   First it was on climb and then was on cruise.  New flight did the same again.  

Edited March 2 by Seth2413

[soliszadar]

same problem here.....

[Georgio]

Here too. I started a long haul (EDDF-KSFO) and somewhere in the middle the autopilot went off. 2nd test from EDDF to RJTT - exactly the same. Basically your long hauler airplane is not functional for long hauls... lol. (no autocompression used) How can such a fundamental error be overlooked?

Edited March 3 by Georgio

[wingview]

Do you have Turbulence setting in MSFS on low? I have no problems.

[coxman69]

Same here, wanted to do DOH-MIA for 2 straight days, one time AP disconnected 5 hours into the flight, and now after 13 hours it did it again, both flights on the -1000, never had the problem on the -900, I must say on every -900 flight I was near the sim for the whole flights, on the other hand on the -1000 flights in the first case I found it spinning in the morning and now I checked my flight on Volanta and it keeps spinning over the East Coast. No assists turned on, using Thrustmaster airbus stick with a pretty big dead zone, so I wouldnt consider there was any input that would make the AP disconnect

[vxal]

every -1000 flight ive done has ended in an autopilot disconnect and lost flight. Also Using the thrustmaster airbus stick. Supposed to be at fl 340 and obviously on the flightplan.

Edited March 3 by vxal

[richboy2307]

Hi,

The autopilot disconnects due to

• excessive roll/pitch, or
• overspeed/stall conditions, or
• continuous user input on primary flight control axis

The above conditions can be caused by

• abrupt "live" weather changes, or
• sim AI assistance options, or
• noisy axis that cause phantom inputs, or
• conflicting keybinds on trim/primary flight controls (usually keyboard) triggering unintentional input, or
• conflicting keybinds relating to AP disconnect triggering unintentional input, or
• momentary performance hiccups that lead to erroneous CFD data triggering the above conditions

Just for some context, I've done 2 this weekend, and 9 total 12hr+ flights without any such issues. Collectively amongst our testers we have over 1000+ hours of successful flighting prior to release, with many long-hauls both real-time and accelerated via time compression. Not to mention the countless other customers out there enjoying these flights as we speak.

So no, there was no fundamental issue that was overlooked or untested in that regard. There are however lot of variables to this equation (hardware, peripherals, control setups and server connectivity etc) and we are monitoring user reports of such issues. We hear your feedback and are working on a user option to inhibit the realistic AP disconnection logic in the interest of ensuring flight completion.

In the meanwhile we recommend users use "LOW" turbulence settings, ensure all AI assistance options are disabled, verify their control bindings as well as use the "AFK mode" on OIS Simulation settings page such that the sim may pause in case of AP disconnection.

Thanks!