ISSUE DESCRIPTION
The ATR suffers from what I call the “Fisherprice - my first autopilot” logic. Same applies to most if not all default aircraft.
With autopilot engaged, especially on the ATR, it is physically impossible to steer through the autopilot. Either you are flying or the autopilot is flying, not both at the same time. The autopilot will sense the force applied to the controls and disconnect if a threshold is reached (only on the pitch and yaw axis on ATR, not on the roll axis).
When applying manual control inputs with the autopilot engaged on this creation:
You and the autopilot are fighting each other, the flight control surfaces follow your inputs, overruling the autopilot. But the yoke follows the autopilot command. This has not made any sense since FS2020 initial release. That this logic is still present is simply unbelievable.
In this screenshot, the aircraft is flying straight and level, the control surfaces follow your inputs but the autopilot rolls the yoke, as if the two are somehow disconnected:
The solution is so simple: IGNORE ALL MANUAL INPUT WHEN AP IS ENGAGED. When applying input above a certain threshold (lets say 50% travel), the autopilot should disengage (for the ATR only applies to pitch and yaw axis, not roll).
This problem is most apparent when you are using the keyboard (like me now away from home), because there is no way of knowing whether the controls are centered. So any input applied while engaging the autopilot will overrule it (yes there are key bindings for centering).
FREQUENCY OF ISSUE
Since FS2020 initial release.
REPRODUCTION STEPS
Engage autopilot, apply manual inputs.
YOUR SETTINGS
Not relevant.
MEDIA
See above.
