Description of the issue: 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.
If applicable, which aircraft is experiencing this issue: So far I’ve experienced it in the A320 V2 and the A321LR both iniBuilds.
How often does this occur for you (Example: Just once, every time on sim load, intermittently)?: It has happened every single flight I’ve had so far.
Please list clear steps you took in order to help our test team reproduce the same issue:
Plan a flight with the A320 v2 or A321LR chose a destination airport that has ILS for example maybe YMML to YSSY.
Complete the flight as normal and then when you get to the final approach phase where you’d engage the autopilot 1 and 2 and capture the GS and LOC for the airport.
Proceed to do the final descent (and about anywhere from 100-400ft altitude using CAT III Dual mode automatics so far every time it’s disconnected all automatics, throttled to TOGA, violently pitches the nose up and starts screaming GLIDE SLOPE GLIDE SLOPE therefore ruining what up until the final 10 seconds of the flight was somewhere bearable.
What peripherals are you using, if relevant: Just a standalone Xbox Elite Wireless Controller Series 2 on an Xbox Series X
I tried the Airbus 321 and 320N and Boeing 787. EFB is broken, Autopilot doesn’t follow it even when its sent to Avionics. This game is a $150 pile of ■■■■ that I’ve now disputed with Amex. Maybe I’ll buy it again in 6 months and try again. I’m a Dad with 2 toddlers. I don’t have time for this ■■■■, it has to work and it has to have an easy mode for novices who just want to enjoy it. Its far too complicated, I was able to learn 2020 but 2024 has destroyed any quick knowledge I gained.
Regrettably, the issue persists on the Xbox Series X, which is quite disappointing as I greatly enjoy flying the Airbus aircraft. They performed flawlessly in 2020, including the autoland feature, which now seems to consistently fail on every approach, irrespective of weather conditions. I sincerely hope this matter is acknowledged and addressed. On a positive note, the recent patch has notably improved the ground textures.
Just tested another iniBuilds aircraft the A400M and as expected the avionics froze up about 200ft from the runway after the PFD had transitioned to LAND mode with a CAT 3 DUAL ILS Autoland, and it plunged to 2,000ft/s downwards for no apparent reason, it’s starting to look like the avionics of the iniBuilds aircraft can’t cope with the logic or coding in 2024 for autoland, I’m not sure, I do hope they get it fixed or at least acknowledge it.
I have the exact same issue. Tested at several airports in Europe with no luck. Again it worked fine on 2020. Definitely seems to be the AI Pilot and cursor mode as I had to turn that off in 2020. You can’t use the game without the cursor on Xbox so it’s really a game breaker for the inibuilds aircraft. I’ve taken to manual landings but even then it’s a challenge to get it to play ball!
Is there any update on this? I cant get the magenta flight path to generate on the map in any airliner. I’ve tried using sim brief, manually entering on the EFB and tried sending flight plan to avionics. All i get is a straight green line. The only thing that does seem to work is manually entering the heading and using autopilot that way.
Yeah until they add an option in the settings to disable AI Copilot in cursor mode, we’re not gonna know if that fixes the problem. But yeah keep replying to this thread to keep it fresh I guess
I think it’s mostly an Xbox issue specifically, as someone even tested it when an Xbox controller on PC, so I guess it’s just bugged at the moment on the console and the cursor mode thing. But love the A320N can’t wait for it to fully start working
Yeah of course I have, I loved flying the A20N v2 in 2020, and the autoland etc. worked awesomely, and I’m pretty sure the autopilot doesn’t even work properly at all without the FD’s switched on, I’ve posted on the iniBuilds forums and they’ve not said it was user error. Because whenever you enter cursor mode on the Xbox with the controller some sort of AI copilot takes over, yet in the settings there’s nowhere to turn it off as in 2020. And after activating cursor mode and then exiting it, the plane seems to exhibit strange “wobbling” during cruise and I feel as if it’s messing with the autopilot code or something, but won’t know if that’s the issue until there’s a toggle to turn off AI copilot in cursor mode.
I conducted some tests with the iniBuilds A320N V2 and A321LR to identify the probable cause of the ILS/Autoland failures in these aircraft. From my experience, I had suspected that using cursor mode might inadvertently activate some sort of AI Copilot, as most issues seemed to arise after engaging cursor mode—whether for replying to ATC or interacting with the cockpit. For clarification, I didn’t leave cursor mode constantly activated. The issue seems to occur after using cursor mode in flight, even if it’s deactivated afterward. The AI Copilot appears to get bugged and “stuck on,” interfering with the aircraft’s automatics, with no way to turn it off again.
For these test flights, I avoided using cursor mode entirely to see if the autoland functions would work as intended. Initially, I wasn’t optimistic, but to my surprise, both aircraft successfully completed their autoland procedures. There were no unexpected disconnections of automation at low altitudes, no random TOGA activations at 100–200 ft, and no sudden pitch-ups. This confirmed my suspicion that AI Copilot was interfering with the aircraft’s systems after cursor mode was activated.
For now, I recommend avoiding cursor mode during flight if you’re experiencing similar ILS approach issues with these aircraft. While this is a useful workaround, cursor mode is almost essential for controller users like myself, making this limitation frustrating.
To Microsoft/Asobo: Please bring back the option to toggle AI Copilot on or off in cursor mode, as it was available in the 2020 release. This would resolve many issues, particularly for the A320N V2 and A321LR. Many users don’t need or want AI Copilot interfering with their flights while using cursor mode—especially if it’s causing bugs or ruining approaches. A toggle option would be invaluable. Additionally, there is already a key bind for “delegate controls to copilot,” but it doesn’t seem to work reliably. Fixing this functionality or reintroducing the AI Copilot toggle in cursor mode would greatly enhance the user experience.
