when i turn CMD A off and try to engage it again, nothing happens. if i really need auto pilot i should turn CMD B

 

 

why?

Are you moving the disengage bar back up to its normal position? Click once to disengage, then once again to move it back up.

Describe precisely how you are desengaging the autopilot. Certain things, like moving the flight controls with the A/P on, can cause a failure in the system, leading to permanent A/P disengagement (won't let you reengage).

Are you moving the disengage bar back up to its normal position? Click once to disengage, then once again to move it back up.

 

Describe precisely how you are desengaging the autopilot. Certain things, like moving the flight controls with the A/P on, can cause a failure in the system, leading to permanent A/P disengagement (won't let you reengage).

 

i made e little pressure on the joystick, it was enough to desengage. so a failure occured...

 

 

but cmd b is the same as a?

 

 

ps: not always i do stupid things like this lol

By moving the stick you aren't disengaging the AP. You are forcing it into cws mode and it depends on which way you move the stick. If you pull or push it you will force it into cws pitch mode. Turn the stick and will force it into cws roll. The autopilot will remain engaged. If you truly want to disengage the ap just push the button on the yoke. Hot key it to your controller to make it more realistic.

 

Sent from my Galaxy Nexus using Tapatalk

And if you move the yoke to hard, you break some connections from the AP accuators to the yoke. The AP channel (CMD A or CMD B) won't work anymore until maintaince (in the NGX, the CDU) fixes the system.

And if you move the yoke to hard, you break some connections from the AP accuators to the yoke. The AP channel (CMD A or CMD B) won't work anymore until maintaince (in the NGX, the CDU) fixes the system.

 

even if i restart the flight simulator i need to fix?

even if i restart the flight simulator i need to fix?

Yes- you need to repair it in the failures menu.