For the last several days, I have been encountering lots of auto pilot/auto throttle problems with the model, whether using the Development or Experimental version. At times, the autopilot refuses to activate and sometimes when it does, it will not follow the programmed flight plan on the MCDU. The auto throttle also seems to be having intermittent problems and on some flights, I can’t get the power to climb. Am I the only one having these issues?
I have not seen that recently on my flights. I had a flight today Down Under and everything went off without a hitch. I’m on the latest Development release as of this morning. A/P won’t engage if the plane determines in unable or unsafe to do so. Are things like your speed/pitch/flight controls all normal when trying to activate?
I haven’t noticed any problems. I just flew the A320NX last night. To answer your question, it would seem that it’s just you.
This might be an obvious question, but have you checked your Assistance settings and make sure everything is set to True to Life with all the sub-options set to Hard?
I have the Hard settings. Pretty much have tried everything, except removing the mod completely from the game and then reloading it. Will try that now.
If you see the issue again, take a screenshot of the cockpit displays when it happens. Maybe that will give people some clues.
Check your settings/throttle calibration/dead zones as well. SU8 reset many different settings so I needed to go back through.
Do you have any mods in the community folder?
It could be a conflict.
As well, do you use Navigraph, or the default navdata?
Deleting and reloading the mod from scratch seems to have worked. Am now flying the Experimental version and all the newest features seem to be working. Perhaps the original mod was corrupted.
2 Likes
Same here; I did a couple of flights since SU8 with latest dev version; everything good
glad to know you sorted this one out 
Fingers crossed. Really enjoy the Experimental version, given all the new features.
1 Like
Been having similar problems to the OP, latest DEV version, autopilot won’t engage then autothrottle malfunctions and I get overspeed warnings and of course I bust my altitude clearance too. I suspected, as suggested abive, that the aircraft wasn’t in a “safe” configuration but couldn’t see where. This has happened at several airports so I’m discounting addons in the C/F.
Continue the flight manually until on course etc. reset autothrottle, make sure I’m in CLB on the throttle and the AP engages with no further problems.
Are these issues happening right after takeoff and during climb-out?
A key thing I learned recently is A/T will not engage on takeoff if you do not select the right throttle detent. If you enter a Flex take off temperature in the MCDU, you must take off in the MCT/FLX detent. If you do not enter a Flex take off temperature, you must take off in the TO/GA detent. If you do not, A/T will not engage when you pull back to the CLB detent.
This drove me crazy for several take-offs and I didn’t realize that it depended on Flex temp matching throttle detent for take off.
1 Like
yes that’s Airbus 101
I can only get the FBW A320 Stable version to follow my LNM flight plans. I only use the AP on the upper section of the cockpit. I plan on learning the FMS this summer.
The Development version indicates it’s locked on the Flt plan but doesn’t follow it. Maybe I’m doing something wrong that’s ok with the Stable version but not the Development version?
My plans use some waypoints I create if this means anything between the two versions.
Development version is working fine. It’s probably your procedure. I suggest watching a few of the plentiful YouTube videos showing how to plan, program and fly the FBW A320. Be patient and watch them completely. Do not skip any parts.
I figured that, that’s why I never post with my hair on fire…lol.
But could I be doing something wrong with the Development version that it doesn’t like and follow the same process with the Stable version it finds ok.
Again, I’m using Little NavMap with some waypoints I create and only use AP on both versions.
Very helpful comments from all. Although my last flight in the Experimental version went off perfectly, will keep suggestions in mind.
1 Like
Just finished an IFR from EGNT to EGGP, really just to test out the aircraft once again. This time got airborne with all the correct selections, wheels/flaps up, throttle to CLB from Flex, and the AP took straight away, following the SID perfectly. Until we got to the first assigned altitude when whilst we were attending to other things the overspeed warning went off and we headed for the stars!
Pulled the throttle, hand flew it back down to assigned altitude (apologies Manchester Radar!) when we got the the AP engaged - strangely we hadn’t actually reset the throttle to CLB until after the AP clicked in but the flight then proceeded by the book including a perfect STAR and Approach. (Shame the autoland then failed and we crashed into the runway - need to investigate that one but I don’t think Cat3 is available at EGGP.)
I really don’t know if it’s me, the sim or a C/F item that’s causing this but I’ll persevere!