I came across this issue lately with Cessna 172 on MSFS2020. 

Both elevator and aileron axis are functional before the engine starts. But once I switched on the engine the the Ailerons stop functioning. I then changed the aircraft type to Cessna 172 G1000 where I can see both axis fully functional. I've already calibrated my Honeycomb yoke in WIndows 11. Also I reverted all the control back to default settings in MSFS2020. Unfortunately, the issue is still persists. 

Please refer to the following clip. You can hear AP engaging sound around 0:15 mark then yoke starts turning to right without any input. 

 

 

Thanks

13 hours ago, Aviationkid2020 said:

I came across this issue lately with Cessna 172 on MSFS2020. 

Both elevator and aileron axis are functional before the engine starts. But once I switched on the engine the the Ailerons stop functioning. I then changed the aircraft type to Cessna 172 G1000 where I can see both axis fully functional. I've already calibrated my Honeycomb yoke in WIndows 11. Also I reverted all the control back to default settings in MSFS2020. Unfortunately, the issue is still persists. 

Please refer to the following clip. You can hear AP engaging sound around 0:15 mark then yoke starts turning to right without any input. 

Thanks

There is a binding conflict that activates the AP; please check the keyboard and any connected peripherals.

 

There are no other bindings associating AP. I've cleared them all. Only Alpha flight control has a binding for AP. 

If it is a binding conflict , why does it only affect default Cessna 172? It doesn't make any conflict with Cessna 172 G1000 though under the same control profile. 😕

 

Screenshot

https://ibb.co/WWV5cDRr