Default A320neo altitude error in autopilot

It’s not. That would be not feasible technically, if for no other reason than because of network latency.

1 Like

I delete And reinstall a320 content but problem still remain. Is the avionics of a320 is in a specific folder or have a name that I can investigate or delete and reinstall (like other Garmin avionics in the SIM)?

Exactly. The QNH you’ve set is irrelevant; if you set the AP to 7000 it should fly at 7000 on the altimeter.

Clearly, there’s something wrong with the OP’s setup somewhere.

Just gotta find it.

Strange because I use fbw a320 and is good. Setting is the same clearly the fbw is more detailed system but taking off, activate ap and flying at specific level is the same. Seems something in a320 asobo is broken but I can figure out what

Ok, the problem is in the flt CTL. If I turn off elac1 sec1 fac1 the autopilot descend to correct altitude and I can engage again elac sec and fac. Now if I change altitude the airplane follow correct altitude. Someone can tell me why this append?

I investigate a lot in this day and I found that some old bug and malfunction in the past is resolved whit the workaround of turn off sec 1… Seems default 320 (and aircraft with def 320 shared avionics) is randomly bugged in the autopilot section and the solution is always turn off sec1 or reinstall the whole SIM. A question for developer, is there a cfg file or something like that i can edit or redownload for solve the problem? Please let me know or explain how a320 avionics sistem works in term of files and where is located

unfortunatly bug persist randomly… sometimes autopilot work, sometimes need to stop flc button. so. no one can help me?

Hi dementedcorn327, in this section there’s no useful help or information about my issue and is very frustrating… Can you please move in bug session or where developers is active? Thank you

Until not having other users being able to reproduce the issue or specific steps that allow to reproduce it, even if moved back to the bug forum does not automatically means devs will look at it, they need a way to reproduce it. So if you could provide more information like: start on the runway or cold & dark, specific route/airport, live or custom weather condition, aircraft setup, even aircraft livery you are using when it is happening please provide them and hopefully some users will be able to reproduce.

I did 3 intents following your steps “Simpli insert altitude in autopilot and apply” to try reproducing it and was not able to, always leveling off at the target altitude:



I’ll do more intents and if other users could do so it would be very helpful to get their feedback.

The situation is present in every scenario every airport every livery every weather (real or not) with or without addon installed and in safe mode. In past day Sometimes randomly run correctly but now no one flight I made work as expected. Cold and dark, on runway or start in flight. What can workaround the problem is to stop the flc computers (elac FAC sec) but this produce a violent dive before a320 start to climb again and reach finally correct altitude, after that I turn on again flc computers and now autopilot work correctly. So for now I start my flight with flc computer off, then when I reach altitude I activate FAC sec and elac, but with this method auto trim e other fbw function is off… I don’t know if any addon I install can modify system file so deeply but seems a config file or something like that is corrupted… But delete and reinstall a320 doesn’t resolve the issue so I don’t really know what I can do… (I don’t want to reinstall entire SIM and, if something is broken, save actual official and community folder on a disk and move later for save download time, must be useless)

I reading some post in other forums about various bug in the past affecting default a320 autopilot , and the FLC turn off and on or keep elac FAC and sec off is the workaround for 99% of autopilot issues I see…

The real big problem is that shared avionics add-on like latinvfr a320/321/330 also shared the issue and some of my fleet is unusable. A320 fbw work Well but on my old pc is a stutter fest… For what I want, default a320 was ok and see stop working well randomly with no changes like this made me crazy

Thanks for the additional information. Have you tried to uninstall latinvfr addons ?
I did another flight with many level changes and not able to reproduce.

Yes, but problem persist

problem is still here… please help me

I am also having this issue, and I can only use Asobo’s because the other planes the autopilot doesn’t automatically follow the flightplan, they just start acting up going any weird way and I always have to change the heading

unfortunatly i can resolve the issues and i use the ini v2, but the fps is massive and for easy fly i prefer the default a320… noone can help