Using the latest FBW dev mod for the A320 Neo I found that the autopilot so far is working fine but just for a few minor glitches. Flying a SID works perfect and following the FLPLN is great, too, but problems do occur when executing an ILS APPR to an airport. As soon as the A/P notices that the next WPT is called USER or USR then a sharp turn to the right is executed, where it should take a left turn. Also if a turn to the right would be applicable the A/P takes a sharp turn to the left. The only way I found to circumnavigate this "glitch" is to do a DCT to the next waypoint in the APPR. Am I the only one running into this anomaly? Is there a better workaround for it then to do a DCT to the next waypoint? CLR the USR or USER WPT doesn't work unfortunately.

Thanks,
Hans

Edited December 2, 20205 yr by hvw
Accidentally wrote STAR instead of SID

No, you are not alone. I found the same workaround in the below video. Download the fixed Flybwire A320 which works much better here.

MSFS2020 A320 - Autopilot Fix - Following the Flight Plan - YouTube

Edited December 13, 20205 yr by MrFuzzy

53 minutes ago, MrFuzzy said:

No, you are not alone. I found the same workaround in the below video. Download the fixed Flybwire A320 which works much better here.

MSFS2020 A320 - Autopilot Fix - Following the Flight Plan - YouTube

Actually the "standard" dev mod one, the last one, works great. I can shoot an approach till FAF on the A/P. This morning I tried to do so with non-standard FBW A320 and again I ran into this USER/USR anomaly thingy. I then started all over and from the beginning of the approach I switched to heading mode and now I could do the approach without a problem.

I will take  look, of course, at the video in the link you mentioned.
 

Thanks,
Hans

Hans, I am just landing at EKCH and ATC gave me ILS12 approach. When entering it into the FMS then indeed the neo circles back but the reason is that USER and USR waypoints where added to the approach plan. This seems to be an MSFS issue granting ATC clearance for assigned rwy too late so approach plan starts before the actual waypoint following the initial flightplan. i.e. NEXEN in my case. So naturally the neo turned away to go back to USER and USR. So I just skipped the USER and USR waypoints and chose DCT CI12 which is the next WP after NEXEN on my way to EKCH. Will see whether that works our but looks good. Flying MP, so watch out for LH4371 currently 30nm into CI12 going to to 3000 feet 🙂

3 minutes ago, hvw said:

Actually the "standard" dev mod one, the last one, works great. I can shoot an approach till FAF on the A/P. This morning I tried to do so with non-standard FBW A320 and again I ran into this USER/USR anomaly thingy. I then started all over and from the beginning of the approach I switched to heading mode and now I could do the approach without a problem.

I will take  look, of course, at the video in the link you mentioned.
 

Thanks,
Hans

In the FBW version of the A320 the "USR" waypoints appear as well in the route, but they don't cause issues as far as I could see. There must be something else too, because even when you put the A/P in HDG mode, it doesn't follow the heading bug and flies straight.

Honestly these A/P issues are quite random and it's complicated to define a 100% working solution for everyone. There are people who solved the issues even with the Asobo A320 by cleaning the rolling cache or setting a deadzone for the controllers.

I did both: once the rolling cache trick worked even if there was no rolling cache - I don't use it - just once... And I have been keeping 10% deadzones since the release because it just feels better. But I couldn't resolve the A/P issues with the default A320, I got frustrated and downloaded the FBW mod, which (cross fingers) works fine for now.

1 minute ago, MrFuzzy said:

In the FBW version of the A320 the "USR" waypoints appear as well in the route, but they don't cause issues as far as I could see. There must be something else too, because even when you put the A/P in HDG mode, it doesn't follow the heading bug and flies straight.

Honestly these A/P issues are quite random and it's complicated to define a 100% working solution for everyone. There are people who solved the issues even with the Asobo A320 by cleaning the rolling cache or setting a deadzone for the controllers.

I did both: once the rolling cache trick worked even if there was no rolling cache - I don't use it - just once... And I have been keeping 10% deadzones since the release because it just feels better. But I couldn't resolve the A/P issues with the default A320, I got frustrated and downloaded the FBW mod, which (cross fingers) works fine for now.

You are right, it seems to be randomly this USER thing. In the "standard dev mod" FBW A320 I can easily skip the USER by performing a DCT to the waypoint after this USER waypoint, however, this didn't work in the non-standard FBW 320. It went all over the place. when I selected a DCT to the next waypoint. In the few last dev mod A320s all these DCT attempts were successfully, hence I am quite resistant to using the non-standard one. Why, I hear you ask? Well, I use to "fly" 3 hours flights and then it is pretty disappointing (understatement) to run into a malfunctioning A/P 🙂 

The USR waypoint doesn't cause a problem anymore, some time ago USR, too, caused problems, but now it is "only" the USER waypoint (discontinuity) that throws the plane off course.

I use 20% deadzones but I thought these settings only are in effect when manually flying. (landings, take-offs etc.).

 

 

I just used the custom fbw mod and landed safely at EKCH, just ILS rwy12 did not autodial but that is a known issue with some airports, hand to hand fly it down, luckily cloud layer broke early enough for visual landing

Edited December 13, 20205 yr by DAD

All this A/P "misery" started with the latest big update ASOBO issued, they repaired the A/P in such a way that every serious simmer is getting grey hairs of this "refurbished" A/P or is going bald. It's a royal PITA, but luckily most of us did find a way to circumnavigate this, let's call it, undocumented feature. 

Blue skies 🙂 

It's amazing. 

I flew the custom FBW version last night. 

Some bits need adjustment but overall it's an incredible improvement on the default aircraft. 

Switch off the autopilot and the aircraft handles beautifully.

 

14 minutes ago, gb09f said:

It's amazing. 

I flew the custom FBW version last night. 

Some bits need adjustment but overall it's an incredible improvement on the default aircraft. 

Switch off the autopilot and the aircraft handles beautifully.

 

Many times I wondered if I should leave FS2020 aside and return to my beloved PMDG 737s in Lockheed Martin's P3D and enjoy relaxing, fulfilling flights with those aircraft who seldom left me out in the dark. Only pilot error(s) could ruin my 737s flights. However, I preferred to challenge myself and see if "this time" all should go well in the A320. Only two or three times since the release of FS2020 these flights brought me joy. But I will persevere and see what the future will bring.