[BUG] Autopilot systems not functioning after MSFS update

[Teslix]

Mod Version

Latest Dev Version from Installer "built": "2020-11-24T08:08:38+00:00", "ref": "refs/heads/master", "sha": "b570de8c53cd5b52a21c81f8120bfa57d8c53830", "actor": "wpine215", "event_name": "push"

Describe the bug Multiple issues on my first flight today after downloading the FS2020 1.11.6.0 update, downloaded the latest Dev build before flying:

1. After takeoff, engaged AP but the aircraft wouldn't follow the flight plan in managed heading.
2. Set heading to manual, aircraft would not bank right to new heading (straight line).
3. Tried left heading instead, plane banked ~40 degrees to setting.

To Reproduce

1. Filed flight plan through FS2020 world map
2. Start-up, taxi, takeoff as per normal
3. Issues noticed after turning on auto pilot systems.

Expected behavior

Expected aircraft to bank right and take up the managed heading selection as per the flight plan.

Actual behavior

Aircraft maintained current heading, would not respond to a right turn in heading selection mode and banked over 40 degrees when selecting left heading instead. Flight plan indicator on the FD shows as straight line to infinity. AP will not capture.

References

N/A

Additional context

Was this working before/when did the issue start occurring? Not an issue until today's update.

Is this a problem in the vanilla unmodded game? I've repeated the same flight / flight plan without the A32NX mod, and the issue does NOT exist there.

In the first screen shot below, I've engaged the AP and the aircraft immediately banks a little to the left, when I should go right. It then maintains a straight line and immediately, the flight plan switched to a waypoint 3 down the list but doesn't track in that heading.

In the next screen shot, I've switched to heading selection mode and made a selection for a right turn, but the aircraft is not responding.

[chrisjk84]

Fellas :D This is not a flybywire issue, it is a MSFS issue for someone reason with the A320neo. I fixed the issue (not sure if a perm or not, i will try again in a couple of hours).

It has to do with your joystick/yoke - controller. There is some kind of spike the game is picking up in the control when you turn on the AP and causes the aircraft to bank right.

I deleted ALL of my joystick AXIS controls, saved and applied, then reassigned them. After doing this I was able to engage AP without the sudden roll to the right. Now I did notice after the next waypoint it started to do the same thing, just not as bad. I just rolled my joystick all the way to the left and back to the center and it was fine.

This happens in the default A320 and the Flybywire. I haven't experienced this issue with any other aircraft.

[jf96g]

I just installed the latest development version and it was working fine! Started from cold and dar, setup MCDU as usual and AP followed the heading as planned! However the swaying from left to right continued when reaching higher altitudes

[A320PHX]

I see the current version is about 23 hours old. I had downloaded that one yesterday and still noted the same behavior. I have deleted the A32NX from my community folder, reinstalled the downloader and will see if anything changes with the one I just added.

[Gamma36]

It has to do with your joystick/yoke - controller

Ahh. I have disabled all switches in my Honeycomb yoke - to fix the Saitek autopilot making strange alt changes. It sends continous USB messages for each switch to the sim, causing internal sync problems.

I've never had the heading roll of death when engaging AP, although the A/T can get into TOGA lock heading fast to overspeed.

[jf96g]

Well if its the same version from yesterday, the onlu thing I did different was before takeoff I selected on the MCDU direct to a waypoint, and then it worked perfectly, don't know if that info may help the FBW team!

[A320PHX]

Just did a test flight from SAN to LAX and can say that while I was still off course a little, like 1.0/1.5 miles off, this has been the best it has tracked a flight path since the new patch. Managed speed seemed very off though. It would speed up and retard the throttles unless I placed in selected speed. No wobble so far.

After Departure:

During Cruise:

[collinbrady]

Fellas :D This is not a flybywire issue, it is a MSFS issue for someone reason with the A320neo. I fixed the issue (not sure if a perm or not, i will try again in a couple of hours).

It has to do with your joystick/yoke - controller. There is some kind of spike the game is picking up in the control when you turn on the AP and causes the aircraft to bank right.

I deleted ALL of my joystick AXIS controls, saved and applied, then reassigned them. After doing this I was able to engage AP without the sudden roll to the right. Now I did notice after the next waypoint it started to do the same thing, just not as bad. I just rolled my joystick all the way to the left and back to the center and it was fine.

This happens in the default A320 and the Flybywire. I haven't experienced this issue with any other aircraft.

I think everyone's pretty aware this was introduced by the base game - that doesn't mean we all need to help see if it can be correct by the mod team or if we have to wait.

So this thing gets 100% correct by wiping my yoke and rudder bindings, saving, then rebinding them manually (not clicking the 'back to default' reset?) - what about throttle? Is anything else busted whatsoever after you do this?

[A320PHX]

Update:

The rest of the flight went fine, except for the horrible stuttering around the LAX 25R approach. The autopilot and ILS continued to remain 1.0-1.5 miles off course though. I had to take over the approach and hand fly in to correct the plane and put it on course for a visual landing.

[ajljazek16]

I have a fault in the cabin and can you excuse the error? this version https://flybywiresim.com/a32nx

[vlbreda]

Problem of not following the flight plan / localizer is also present in the stable version I found out. That's a shame. Occured in a flight after a C&D start.

[ErikNL80]

I am using the Thrustmaster TCA Officer Pack (Sidestick/Throttle Quadrant). Did some test flights and here are my results:

• Vanilla A320, works as intended (following FP, capturing LOC and G/S)
• A320nx latest dev; when starting at the runway, works as intended
• A320nx latest dev; cold and dark; aircraft banks after engaging AP

[vlbreda]

Hope there is a fix soon. For the time being, I found a working recent version of the mod, offered by a guy named easyjetsimpilot: https://www.dropbox.com/sh/4ojtcqzgq6h9xti/AACFDabQsBwlGaZ7FbQ30Czsa?dl=0

As far as I can tell, this one has none of the above issues and works fine. Can work as a substitute untill there is a solution from FBW.

[Gamma36]

@vlbreda Thanks, that version was tagged yesterday and is being studied.

[Gamma36]

@dc1ps2 You seen to be overspeed with flaps down, or am I wrong?:

That might accentuate the roll perhaps?

[Samsamtheambulanceman]

Hope there is a fix soon. For the time being, I found a working recent version of the mod, offered by a guy named easyjetsimpilot: https://www.dropbox.com/sh/4ojtcqzgq6h9xti/AACFDabQsBwlGaZ7FbQ30Czsa?dl=0

As far as I can tell, this one has none of the above issues and works fine. Can work as a substitute until there is a solution from FBW.

Tried this as a Solution, C&D Still having issues and doing the death roll. Flew from KIAD to KJFK setting up by manually inputting my Flight Plan. Second AP is put in it dives to the Right.

I have tried to use the development and AP just won't stay on course properly, almost seems like it's drunk! I did this as a direct Depart from a RWY it flew the turn from take off OK but also did the swaying once at cruise of FL200,

Didn't get round to doing a C&D Start.

[Gamma36]

I've noticed the You Tube pilots go through a methodical flight plan, SIDS, weather reports, STARS, ILS frequencies. Spawning from a gate with ground power, from cold and dark. Checklists for everything. Fuel, weight and trim are programmed in the MCDU.

With a SID the plane will follow the runway heading, remove flaps then proceed to first waypoint on similar heading a few miles away. The rest of the SID won't require steep banked turns. LNAV and VNAV will be documented and followed.

Simbrief is popular with pilots, it accepts a Navionics code to use the latest cycle, which will also be in MFSF. Then everything syncs together.

Perhaps this methodical approach keeps the sim working within its boundary?

If only we had replays - we could debug the replays and use them as test cases. But we don't, the next best is .pln and .flt files which contain a lot of "initial conditions" for the code.

Regarding stability, the latest release has tuned ai.cfg. I merged the PID (Proportional, Integral, Differential) params into the mod. The plane is smooth at cruise using today's dev (26th) and updated ai.cfg

[dc1ps2]

@dc1ps2 You seen to be overspeed with flaps down, or am I wrong?:

That might accentuate the roll perhaps?

This is also a phenomenon I explained. In the Type A test case, the climb and speed increase are very stable, but the speed increase when it comes to Type B has become more dramatic. I am not sure if this factor causes the inclination angle to be too large.

[dc1ps2]

It seems that this Youtuber is also experiencing the same problem, but her troubles are more serious, and she keeps turning sharply to the right. What happened to Microsoft's update this time?

https://youtu.be/6rJcRsa7NKE?t=1340

[A320PHX]

Well, it turns out that my good flight was just luck... I loaded up a longer flight from Kelowna to Denver and it put me in a steep left turn and then leveled off and would not climb past my first altitude. Wow, Asobo really messed up this time!

[modzin79]

As some other users, the plane hard bank on the left when I activate AP. The FD is on the extrem left, either AP is turned off. I tried to desactivated and réactivite the FD and AP but that do not resolve that issue.

[Benjozork]

Please react with the thumbs up message on the main post if you are experiencing the exact same issue, to avoid commenting and cluttering the discussion and potentially making information harder for us to find.

[arby36]

I've noticed the You Tube pilots go through a methodical flight plan, SIDS, weather reports, STARS, ILS frequencies. Spawning from a gate with ground power, from cold and dark. Checklists for everything. Fuel, weight and trim are programmed in the MCDU.

With a SID the plane will follow the runway heading, remove flaps then proceed to first waypoint on similar heading a few miles away. The rest of the SID won't require steep banked turns. LNAV and VNAV will be documented and followed.

Simbrief is popular with pilots, it accepts a Navionics code to use the latest cycle, which will also be in MFSF. Then everything syncs together.

Perhaps this methodical approach keeps the sim working within its boundary?

If only we had replays - we could debug the replays and use them as test cases. But we don't, the next best is .pln and .flt files which contain a lot of "initial conditions" for the code.

Regarding stability, the latest release has tuned ai.cfg. I merged the PID (Proportional, Integral, Differential) params into the mod. The plane is smooth at cruise using today's dev (26th) and updated ai.cfg

I haven’t used the 32NX since I attempted a flight last Tuesday immediately after the update (stable version), but during that flight I used Simbrief and went through a slightly abridged version of the NPs, but still extensive, from cold and dark to climb out, like you are saying. I only didn’t use a SID because the airport I was flying from doesn’t have any, but from the runway heading, I didn’t require any great banking to get to the track to the first WPT.

The AP still had the same issue of a slight rightward bank off course and selected heading mode not functioning. So I don’t think working anymore methodically or by the checklists would help. 🙂

[Gamma36]

avoid commenting and cluttering

Roger on the clutter.

I'm struggling to reproduce the problem (Honeycomb yoke, Saitek throttle, Logitech .290 driver, all switches deactivated)

There is a known bug that USB switches confuse the sim, Honeycomb support said Asobo is working on a fix.

Info on yokes/sticks would be useful, we might see a pattern emerge.

[Samsamtheambulanceman]

avoid commenting and cluttering

Roger on the clutter.

I'm struggling to reproduce the problem (Honeycomb yoke, Saitek throttle, Logitech .290 driver, all switches deactivated)

There is a known bug that USB switches confuse the sim, Honeycomb support said Asobo is working on a fix.

Info on yokes/sticks would be useful, we might see a pattern emerge.

I tried deleting my profile on my TCA Stick. Seemingly no effect.

[DevWish]

I'm having the same problems as others have stated. But, in my case, I have issues with the stock A320 as well as the A32NX mod. I'm very sad these past few mornings as I only have a small window in the wee morning hours to fly before the house becomes an asylum run by my kids.

[HubertGer]

Problem solved by me after deleting Asobo A320 and A320NX_vers0.41 deleted und new installed both. After start manually, then AP HDG RWY direction, then NAV. Start ist working and later also capturing the ILS and follow it correctly. Started with engine running.

[Watsi01]

Problem solved by me after deleting Asobo A320 and A320NX_vers0.41 deleted und new installed both. After start manually, then AP HDG RWY direction, then NAV. Start ist working and later also capturing the ILS and follow it correctly.

@HubertGer Did you start from the runway or cold&dark?

[DevWish]

C&D. I've deleted the mod, and tried to fly the stock. It is just borked. AP immediately banks hard right into the ground. I downloaded the version of A32NX from youtuber simpilot, and that didn't work either. I reset all my controls, too. Which is a larger pain in the butt than it should be.

[Watsi01]

Which is a larger pain in the butt than it should be.

Yeah!!! Did that too. No effect.

[DevWish]

FWIW: I'm flying the 747 right now, and AP is working as it should.

[yardpanz]

I'ts working for me. Delete ASOBO A320 and MOD, then re-install both. working from runway & cold/dark. all it's working here with the developer version. thank you HubertGer

[DevWish]

@yardpanz I did, bud. I deleted the mod, tried the stock; same problem. I've reinstalled the mod, same problem. I've started c&d and on the runway - AP freaks out and crashes the plane.

edit: I should mention that I reset my HOTAS prefs, too - which is a MASSIVE pain in the rear.

[yardpanz]

here it's ok, all perfect. I've done what written from HubertGer, very strange

[HubertGer]

Problem solved by me after deleting Asobo A320 and A320NX_vers0.41 deleted und new installed both. After start manually, then AP HDG RWY direction, then NAV. Start ist working and later also capturing the ILS and follow it correctly.

@HubertGer Did you start from the runway or cold&dark?

start with engines running

[Watsi01]

@HubertGer Yeah, the problems mostly occur when you start your flight at the gate (C&D). Many users report no problems with starting on the rwy.

I tried it anyway. Removed the mod and removed the Asobo A320 (restarted sim after every step). Downloaded vanilla again, then installed the latest A32nx dev again. Started form C&D (without saving and reloading the flight). Problem still exists. No NAV or HDG following. No left bank. Next I try the save and reload workaround.

EDIT: with this testflight, the right side PFD kept beeing off during the whole test. Dim switch didn't do anything. Have to check if this was just random.

[DevWish]

I tried both starting on the runway (engines running) and cold and dark. That didn't change the AP behavior.

[Brathwa]

If everyone who complains here were to complain about this problem in the forum of Microssoft I believe that Asobo would have already made a correction for this. The problem is that the group of NX programmers are only making improvements to the aircraft by implementing things that the two companies did not do, so they have no obligation to fix the errors that occur with each update in FS, who has an obligation to fix these "crap" "is Asobo. I'm sorry, because I got tired of seeing it, as soon as they release an update and ruin everything, they run over here to complain about it. I myself have posted several complaints on the Microsoft forum, but the vast majority of idiots do not understand aviation and are only praising each update that is released just worrying about FPS and graphics. So I would like to ask everyone who is complaining here to make a complaint in the Microssoft forum reporting all that happens with each update, and understand once and for all the FlyByWire team was not created to fix bugs in the game, they created this team simply to make the A320 functional, things that were not implemented in the A320, now the manufacturer has the obligation to make all aircraft perfectly functional for flights. Including Asobo, who already got used to doing "shit" and the people at FlyByWire are fixing the crap they do and this needs to end.

[Samsamtheambulanceman]

If everyone who complains here were to complain about this problem in the forum of Microssoft I believe that Asobo would have already made a correction for this. The problem is that the group of NX programmers are only making improvements to the aircraft by implementing things that the two companies did not do, so they have no obligation to fix the errors that occur with each update in FS, who has an obligation to fix these "crap" "is Asobo. I'm sorry, because I got tired of seeing it, as soon as they release an update and ruin everything, they run over here to complain about it. I myself have posted several complaints on the Microsoft forum, but the vast majority of idiots do not understand aviation and are only praising each update that is released just worrying about FPS and graphics. So I would like to ask everyone who is complaining here to make a complaint in the Microssoft forum reporting all that happens with each update, and understand once and for all the FlyByWire team was not created to fix bugs in the game, they created this team simply to make the A320 functional, things that were not implemented in the A320, now the manufacturer has the obligation to make all aircraft perfectly functional for flights. Including Asobo, who already got used to doing "shit" and the people at FlyByWire are fixing the crap they do and this needs to end.

3/4 of the problem is the seeming lack of liason between MS/Ashbo with 3rd Party development. They say pre patch beta will come but not before we go through this every 8 weeks or so when they hack in major "fixes"

It seems the lack of beta testing with both Vanilla stuff and modded stuff is one of the biggest issues for playability with the title.

[HubertGer]

I think, that was misunderstanding. The problem for me was, to empty the communtity folder before the update. That was my fault. Now, and after deleting the ASOBO A320 und new installing both aircraft all goes fine. PS: Thanks for the great work for the developer in your free time by github Sorry, my english is not my native language

[PatriotBY]

I installed a stable build through the installer and everything works fine

[ErikNL80]

Guys, in the assistence settings there is an option for 'Autorudder'. I had it on all the time but switched it off a few days ago. Today installed the latest dev and enabled this option, and was able to do a flight from LYNI to LOWG without issues (except the small F/P offset). I have to test further, but it might be a clue?!

[yardpanz]

Here I have autorudder OFF and all is OK. I don't think this is the problem, but my opinion.

[dc1ps2]

Today, after updating the Attempts to fix AP issue (#2107) of the A32NX Dev Version, after the dark cabin is activated, the problem of excessive inclination turning in AP mode has been resolved. Thanks to FlyByWire for its efforts, it is worthy of recognition, but It will still not be aligned with the flight path during cruise. Before the update, it will be parallel to the flight path to the left, but now it is parallel to the right. I hope that with this correction, it will be perfect.

now

{ "built": "2020-11-27T09:16:34+00:00", "ref": "", "sha": "", "actor": "DerL30N leon.beeser@yahoo.de", "event_name": "manual" }

[MStallen]

Uninstalled MOD and Vanilla. Reinstalled Vanilla ans latest dev. Everything works now. (from cold and dark)???? Like @HubertGer said.

[felixalmont09]

How do you uninstall the a320?

On Fri, Nov 27, 2020 at 09:46 MStallen notifications@github.com wrote:

Uninstalled MOD and Vanilla. Reinstalled Vanilla ans latest dev. Everything works now. (from cold and dark)???? Like @HubertGer https://github.com/HubertGer said.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/flybywiresim/a32nx/issues/2089#issuecomment-734868990, or unsubscribe https://github.com/notifications/unsubscribe-auth/AR44RHAJJFEZA6SEY6ZV3ZDSR63UZANCNFSM4UBHUQTQ .

[MStallen]

Via the content-manager in MSFS 2020

[PatriotBY]

just delete from my d:\packages\Official\Steam\

[PM3Delta]

Uninstalled MOD and Vanilla. Reinstalled Vanilla ans latest dev. Everything works now. (from cold and dark)???? Like @HubertGer said.

No that does not solve it when starting from cold&dark. Did the delete and the reinstall of the A320neo via the Content Manager - still same problem (FD pointing and AP banking to the left into a death spiral), when starting from Cold&Dark in the vanilla (w/o 320nx) installed.

[MStallen]

Strange, but I reinstalled the latest dev also....maybe that did it?

[felixalmont09]

Strange, but I reinstalled the latest dev also....maybe that did it?

i reinstalled the a320 and downloaded the latest dev, im going to test it now.