Since the release of World Update 3 (UK) my airbus A320 Neo (default) drops out of the sky for no reason whatsoever on autopilot despite everything being set correctly. It literally vertical nose dives into the ground and cannot be recovered - HELP !!!
Had a similar experience with the CJ4 today. After an hour’s straight and level flight in AP at 0.71 mach FL430 the aircraft dived left and spiralled down. Despite all attempts at control with and without AP nothing would work so I ended the flight session. Rerunning the flight I experienced no problems. It would be helpful if anyone could explain this phenomenon.
I don’t know why the co-pilot would want to nose-dive into the ground, but maybe check that he/she has not been accidentally given control of the aircraft.
Also, a check of your bindings, to make sure that there is nothing in there that might mess up. For example, even aircraft without a fuel mixture control can get a bit upset if your mixture lever is set to zero. The start of the flight might be OK, until you either touch the lever or Esc and resume, as that will set the virtual control/axis to zero if that’s where your control lever is.
Thanks for your response. I use a Honeycomb Bravo TQ. My CJ4 setup only uses a Speed Brake & 2 throttle levers, so no mixture control. The aircraft fell out of the sky in autopilot…George didn’t have any control at any stage in the flight and I made no ESC and resume activities. It remains a mystery.
This may be totally unrelated, but there does seem to be a “Ghost in the machine” / Asobo Autopilot system.
Its almost as if the gyros topple and cannot recover (even with damage set to OFF).
Then any time you turn on the AP, the plane will either/both dive or turn sharply (normally to the right) … – in all access, visible trim was set neutral.
The only way around this (I have found) is to reload the plane in the Dev Mode Menu.
You can do this while the plane is still flying with AP off, and then when the AP is turned back on again, all is fine.
I can imagine all sorts of way this could easily happen with buggy AP code, but since that is all “under the hood”, it will be up to Asobo to find and fix this issue.
In the meanwhile (at least for the simpler GA prop planes) a work around is to reload the aircraft – not really such a big deal --once you accept the issue, and that YOU have a way around it.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.