Autopilot/ILS/GS Problems (A320n & A321 MSFS 2024)

[JayJay3692]

I’ve only been able to do a few successful flights in the new sim, my favourite planes are the airbus family, I’ve flown to a few different airports such as Melbourne Intl, Bahrain, Dubai Sydney, and all have seemed to have a similar problem, all is well during takeoff, climb, and most of the way through cruise, but the first of 2 problems is (I’m unsure if this is a simulator side bug or iniBuilds side) but the plane when following the magenta flight plan seems to start slightly waving left to right slightly and it’s also seen on the Flight Director (even in calm winds this happens), but the second and more bothersome problem is on final approach to aforementioned airports (I haven’t tried any more to see if it’s any more) but every flight so far about 100-200ft from the threshold of the landing runway the GS, LOC, and both autopilots seem to turn off the plane jerks upwards and the throttle goes to 100% this is during CAT 3 Dual ILS landings every time so far, again I’m not sure if this is a bug on the simulator side as when using cursor mode the plane seems to make weird movements and then the AI copilot is stuck on yet there’s no settings at the moment to toggle on/off AI Copilot in cursor mode so it may be that it bugs out and gets stuck on and hence why the plane seems to be slightly fighting “some other force” throughout the flight, also possibly causing the random disconnection of the automatics during final approaches I’m not sure. I just thought it may be helpful to highlight here. Because the automatics and airplane etc. worked perfectly in the 2020 simulator. 

[richboy2307]

21 hours ago, JayJay3692 said:

but the plane when following the magenta flight plan seems to start slightly waving left to right slightly and it’s also seen on the Flight Director (even in calm winds this happens),

Please follow the guidance here to disable AI Assists: 

 

Let us know if you're still experiencing the problems mentioned after. Thanks!

[JayJay3692]

I recently conducted a flight from NZAA to NZWN using the A321LR. While disabling certain assistance features significantly reduced the side-to-side swaying issues, another problem occurred during the approach. At approximately 200-300 feet above the runway threshold, the autopilot unexpectedly disconnected, the thrust advanced to TOGA, and the nose pitched up violently. This incident appeared to coincide with the autoland system transitioning from GS & LOC to LAND on the PFD.

I am uncertain whether this issue is specific to the aircraft or the simulator itself. When entering cursor mode, it seems to activate some form of AI copilot, as it begins to adjust thrust and course—similar to the behavior observed in MSFS 2020. However, to my knowledge, there is currently no option to enable or disable an AI copilot within cursor mode.

The problems initially resurfaced towards the end of the cruise phase, where the aircraft began to exhibit wobbling once again. This behavior seemed to correlate with increased usage of cursor mode, especially when interacting with ATC and preparing for descent. However, there is no visible option in the menus to disable cursor mode functionality, leaving me unclear about the root cause of these issues.

Despite these challenges, I thoroughly enjoy flying this aircraft and look forward to future updates that will hopefully resolve these bugs and enhance the overall experience.

[JayJay3692]

Any updates or information? It is still occurring regardless of time, weather, airport, I even tried changing the DA(H), tried activating the FO’s autopilot button at varying times, the PFD says CAT 3 Dual as it should, turned on all the automatics, made the weather as calm as possible to see if that was the cause, tried everything I can think of, every landing worked flawlessly in the 2020 version of the plane so I have no idea if I’m missing a “new” step to the process or what, I’m just lost at the moment

Edited December 9, 2024 by JayJay3692

[JayJay3692]

I conducted a test with the A400M at YMML airport to determine whether the autoland issues were specific to jetliners. As anticipated, approximately 200–300 feet from the runway, all avionics froze, and the aircraft began descending at a rate of 2,000 feet per minute. This issue ultimately disrupted the autoland functionality.

[JayJay3692]

Just did another test with the Airbus Beluga XL (A330-743L) and same thing happened when the PFD transitioned to LAND mode for the autoland the avionics froze and it stopped controlling the aircraft. So I’m guessing with the Airbuses it’s maybe a bug or conflict in the logic of the avionics or something I’m not sure. But I definitely can’t wait for it to get ironed out as I absolutely love the iniBuilds airbuses especially the A320N!

[Weeksy1990]

It would be great to get an update on this. Even with all assists turned off Autoland is not working. It seems to be any flight I have used the cursor (which is unavoidable as you need it for the EFB) on Xbox. 

[richboy2307]

Hi all,

Firstly apologies for delayed response. I have shared your reports with our team for further investigation.

Are you also experiencing this issue with other non-airbus aircraft when entering cursor mode? If so, I would also recommend posting the same on MS Forums as that would be something core-sim related rather than the aircraft itself in particular.

On PC, I have tried 2 flights with the Xbox controller on the A320neo, using it exclusively for flight control and cursor mode (RB + L stick) interactions. Some observations I had:

• Cursor Control is not exclusive all the time. It appears whilst in cursor mode, the left stick will still occasionally register flight stick control inputs instead of exclusively controlling the cursor only whilst in this mode. This in turn has the effect of AP disconnection as stick input is detected. Equally the "A" and "B" buttons sometimes also register input on the Throttles, as such leading to its movement outside of or between detents. So for the time being, be wary of this, recenter the left stick and check throttle detent visually to confirm in the appropriate mode. Also verify the rudder trims are centered (value is seen near the flaps lever). 
• Autoland issues mentioned above were not reproducible. I did not experience the issues of freeze or AP disconnection during autoland (both AP1 and AP2 connected). Tested at LPFR ILS Z 10 and LPPT ILS 02 on these 2 flights. In both instances the aircraft continued through the appropriate modes, getting into rollout and AP only disconnected after aircraft came to a complete stop on the runway.

As such, I would appreciate if you could also include a video recording of just the approach and landing phase. You may upload these clips on youtube and share a link if its too bug to upload directly to the forums.

We would like to get to the bottom of this issue as well and implement any fixes that are possible on our end to improve your flying experience.

Thanks!

[JayJay3692]

4 minutes ago, richboy2307 said:

Hi all,

Firstly apologies for delayed response. I have shared your reports with our team for further investigation.

Are you also experiencing this issue with other non-airbus aircraft when entering cursor mode? If so, I would also recommend posting the same on MS Forums as that would be something core-sim related rather than the aircraft itself in particular.

On PC, I have tried 2 flights with the Xbox controller on the A320neo, using it exclusively for flight control and cursor mode (RB + L stick) interactions. Some observations I had:

• Cursor Control is not exclusive all the time. It appears whilst in cursor mode, the left stick will still occasionally register flight stick control inputs instead of exclusively controlling the cursor only whilst in this mode. This in turn has the effect of AP disconnection as stick input is detected. Equally the "A" and "B" buttons sometimes also register input on the Throttles, as such leading to its movement outside of or between detents. So for the time being, be wary of this, recenter the left stick and check throttle detent visually to confirm in the appropriate mode. Also verify the rudder trims are centered (value is seen near the flaps lever). 
• Autoland issues mentioned above were not reproducible. I did not experience the issues of freeze or AP disconnection during autoland (both AP1 and AP2 connected). Tested at LPFR ILS Z 10 and LPPT ILS 02 on these 2 flights. In both instances the aircraft continued through the appropriate modes, getting into rollout and AP only disconnected after aircraft came to a complete stop on the runway.

As such, I would appreciate if you could also include a video recording of just the approach and landing phase. You may upload these clips on youtube and share a link if its too bug to upload directly to the forums.

We would like to get to the bottom of this issue as well and implement any fixes that are possible on our end to improve your flying experience.

Thanks!

Okay I’ll get onto making a clip of a few of the issues, and so far it’s only been the iniBuilds airbuses that have been struggling for me. Has anything been changed on the way autoland works in the new sim? Because I do the same procedures as I did in 2020 and all worked well. 

[richboy2307]

6 minutes ago, JayJay3692 said:

Has anything been changed on the way autoland works in the new sim? Because I do the same procedures as I did in 2020 and all worked well. 

No, it should work the same as far as the aircraft logic is concerned. There are differences in the flight dynamics (CFD) model between the two sims, but that should not affect autoland capabilities.

From my observation the only difference I'm seeing is the way the cursor control mode works in FS2024 vs FS2020, wherein the cursor can disappear from the screen and when that happens the control inputs become active (even though the mode wasn't exited). So there can be residual control inputs which would be particularly noticeable on the PFD.

For example in the below image you can see the "+" on the pfd (in the red box), the control input is not centered whilst in cursor control mode. Whilst moving the cursor, it appears to have detected some input on the flight control stick.

(Click to enlarge image)

Thanks!

[JayJay3692]

3 hours ago, richboy2307 said:

No, it should work the same as far as the aircraft logic is concerned. There are differences in the flight dynamics (CFD) model between the two sims, but that should not affect autoland capabilities.

From my observation the only difference I'm seeing is the way the cursor control mode works in FS2024 vs FS2020, wherein the cursor can disappear from the screen and when that happens the control inputs become active (even though the mode wasn't exited). So there can be residual control inputs which would be particularly noticeable on the PFD.

For example in the below image you can see the "+" on the pfd (in the red box), the control input is not centered whilst in cursor control mode. Whilst moving the cursor, it appears to have detected some input on the flight control stick.

(Click to enlarge image)

Thanks!

Takeoff from Runway 24L at LIRN. This video shows how when using the cursor mode in any capacity during this phase it’s like the AI Copilot is trying to retract or change the flaps and mess with the throttle as seen my the flickering on the PFD.

This is shortly after the first video I linked to you. Showing that basically without fail activating the cursor mode causes something or someone to mess with the throttle.

This is when I had just got cruise on the short test flight to capture this footage, again activating cursor mode to do anything causes the throttles to TOGA themselves without fail. So any cursor mode usage has to be quick if you don’t want to begin overspending or stalling depending on what it decides to do.

This video shows the prior setup and capture of GS and LOC and activating autopilot 2 for the DUAL ILS approach, checked to make sure the throttle was correct as you mentioned, just to make sure it hasn’t been pilot error this entire time I’m hoping it’s not lol

This video shows the final approach into LIRF 16L just after capturing the LOC and GS and descending smoothly with the CAT 3 DUAL landing, also again checked the throttle detent to make sure it was correctly positioned, as stated previously at the last moment after the PFD transitions to LAND mode it suddenly pitches up and deactivates autopilot and goes TOGA. Again not entirely sure if I’m doing something wrong, it’s a bug simulator side, or aircraft side.

I hope these videos help to maybe discerning what the issue is, I’ve posted about it in the MSFS forums also so hopefully they are somewhat aware of it, because as of now there is no way to deactivate AI flying assist when in cursor mode as there was in 2020. So I’m optimistically hoping it’s just that and nothing any deeper. Because damn the planes look incredible in the new sim when everything isn’t trying to bite my head off haha 

Also all the assists you mentioned up top of the thread have been turned off. Checked throttle detent and stuff. And if you say nothing has changed in the way you actually fly the plane then idk what’s happening because I do the same thing in 2020 and it worked incredibly. Xbox Series X using 100GB of rolling cache idk if that’s relevant.  

[JayJay3692]

Oh also I used the preset whether to calm just to make sure it wasn’t wind or weather screwing things up, but yeah not sure how the Autoland issues haven’t been reproduced. It happens to me every time after it transitions to LAND mode of the PFD on the A320N and the A321LR, with the Beluga and A400M the avionics froze up at about the same time it transitions to LAND and instead of pitching up it just plummets. But yeah absolutely can’t wait for this to get figured out. Because as I said the iniBuilds planes matched with the new sim (when the sim is working 😏) are absolutely jaw droppingly beautiful!

[Weeksy1990]

Just to say I have exactly the same issue as JayJay’s video on approach there. Also even if I disconnect the APs to try to fly manually it does the same thing. I suspect it is an Xbox issue rather than just a controller issue hence not reproducing on PC. 
 

Works perfectly in 2020 where you can turn off the AI Co-Pilot but there is no setting to turn that off in 2024. 
 

JayJay has also reported this in the MSFS forum but no response there at all.

[richboy2307]

On 12/31/2024 at 1:02 AM, JayJay3692 said:

I hope these videos help to maybe discerning what the issue is, I’ve posted about it in the MSFS forums also so hopefully they are somewhat aware of it, because as of now there is no way to deactivate AI flying assist when in cursor mode as there was in 2020. So I’m optimistically hoping it’s just that and nothing any deeper.

Yes that is what it seems like at the moment, especially for all the phases until cruise. Its possible the AI Pilot is taking over on final approach as well, but that is quite odd as I see the AP disconnect automatically. I haven't had such issues when I have tried.

Also thanks for making the post on MS forums as well for their teams. I see you also mentioned the issue on this forum bug report, may I suggest adding the above videos there as well?
https://forums.flightsimulator.com/t/ai-pilot-engages-in-cursor-mode-and-messes-up-flight/671715

  

On 12/31/2024 at 1:11 AM, JayJay3692 said:

with the Beluga and A400M the avionics froze up at about the same time it transitions to LAND and instead of pitching up it just plummets.

As for the avionics freeze, can you please also make a video for that?

Also please try to delete your StreamedPackages folder to see if you still have the issue after? Instructions here for console: https://flightsimulator.zendesk.com/hc/en-us/articles/17268168854044-Loading-issues
 

On 1/1/2025 at 9:44 PM, Weeksy1990 said:

JayJay has also reported this in the MSFS forum but no response there at all.

Well, their teams have been away for the holidays, so expect some delay in response. I'd imagine most would be back in office starting next week.

Thanks!

[JayJay3692]

10 hours ago, richboy2307 said:

Yes that is what it seems like at the moment, especially for all the phases until cruise. Its possible the AI Pilot is taking over on final approach as well, but that is quite odd as I see the AP disconnect automatically. I haven't had such issues when I have tried.

Also thanks for making the post on MS forums as well for their teams. I see you also mentioned the issue on this forum bug report, may I suggest adding the above videos there as well?
https://forums.flightsimulator.com/t/ai-pilot-engages-in-cursor-mode-and-messes-up-flight/671715

  

As for the avionics freeze, can you please also make a video for that?

Also please try to delete your StreamedPackages folder to see if you still have the issue after? Instructions here for console: https://flightsimulator.zendesk.com/hc/en-us/articles/17268168854044-Loading-issues
 

Well, their teams have been away for the holidays, so expect some delay in response. I'd imagine most would be back in office starting next week.

Thanks!

I just completed a quick test flight with the Beluga, landing at LIRF on ILS 25, and I was pleasantly surprised that the autoland worked perfectly on the first try. Unfortunately, this meant I wasn’t able to capture a video of the process. From this, it seems the avionics freeze I experienced previously with the Beluga XL and A400M is unrelated to the autoland disconnection issue I’ve noticed in the A320N and A321LR.

 

My guess is that the avionics freeze might have been caused by an out-of-memory issue triggered during the LAND sequence, rather than anything related to the AI Copilot attempting to take over controls. To confirm, I’ll try another test flight at the same airport using the A400M to see if the issue reoccurs. I’ve also gone ahead and cleared the reserved space on the Xbox Series X, as you suggested.