Inibuilds A320N Autopilot Issues and A330 FMC freeze

User Support Hub Aircraft & Systems
, , , ,
1

ISSUE DESCRIPTION

Description of the issue:

Yesterday, I completed 3 flights from Lima to Cusco (SPJC - SPZO) with the A320N.

First flight: I noticed the autopilot stopped maintaining speed, causing the aircraft to go into overspeed and climb sharply until the autopilot disconnected. I tried everything to make it descend, but nothing worked.

Second flight (same setup): This time, the flight went smoothly, although I had to manually set the speed to prevent issues.

Third flight: The same issue happened again. As I approached SPZO, the autopilot randomly disconnected, and when it was working, for no reason, it started climbing despite the cruising altitude being correctly set. Even when I tried to command a descent at -3000 ft/min to force it, it refused to comply! It also went into overspeed. Frustrated, I even walked away for 10 minutes ^^. When I returned, the plane was still circling above FL500 :slight_smile:

I’ll also add that I set the altitude to FL290, but even after changing it to FL140 (after finally halting the crazy climb), the autopilot made the plane climb back to over FL500.

Regarding the A330, when trying to enter information into the aircraft, all the displays freeze! The plane can still fly, but nothing else can be done. This issue only affects the A330, not the A320N.

None of these issues happen with other aircraft. :confused:

If applicable, which aircraft is experiencing this issue:

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue? YES

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?

intermittently

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. flights from Lima to Cusco (SPJC - SPZO)
  2. Game speed: normal

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using, if relevant:

[PC Only] Are you using Developer Mode or have you made any changes to it?

NO

[PC Only] What other relevant PC specs can you share?

i5 11600k 32gb ram , 1080 gtx

MEDIA

Please add a screenshot or video of the issue occurring.

[END OF FIRST USER REPORT]

2

Hi @Ragga95 ,

Thank you for this report. We’ve moved your topic into the User Support Hub.

The Bug Reporting Hub is for posting suspected or confirmed bugs that other users are able to reproduce without duplicating an existing bug report. Using the template or providing all the relevant information about your bug and sim setup is required in order to provide valuable information, feedback, and replication steps to our test team.

If you are not sure if your issue is a bug or need further input from the community, please use the User Support Hub category. If the community can replicate your issue, first search the Bug category to see if there’s an existing topic. If it already exists, contribute to that report. Duplicate bug reports will be closed.

If you believe it is a new report and no duplicate exists, then create a new bug topic using the provided topic template.

All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.

3

BR with multiple issues for different aircraft. Moved to USH.

4

I want to clarify that I’m not deliberately causing the issue or interfering with the system — there is a real problem here. When an aircraft’s autopilot stops functioning properly after a single interaction, that clearly indicates a bug, and I’m not the only one who has noticed it.
However, if every time we report this we’re told “No, it’s not a bug” and the report gets archived without any follow-up, it becomes discouraging to even report issues.
Especially when the root cause is fairly well understood and yet no corrective action seems to be taken

it’s frustrating and disheartening for those trying to help improve things.

It’s iniBuilds that needs to fix their aircraft! Otherwise, someone needs to explain why other aircraft work just fine -_-

5

I concur. I am experiencing similar issues with the default Airbus within career mode. Today I was flying the A320neo, paused (using esc) to step away from the pc and not miss any ATC interactions, returned and unpaused, and the aircraft autopilot disconnected and the aircraft went into an uncommanded climb and the autopilot was not responsive to attempts to engage any of the lateral or vertical modes. No other inputs were made. All I did was hit esc, come back a couple minutes later, and hit esc again. Now I have an aircraft that I can only fly manually to the completion of the mission.

This is a bug, definitely a bug. Whether it is with the aircraft or the sim’s UI interaction, I don’t know. Simply hitting esc to enter the settings menus or whatever should not be causing aircraft systems to go wonky and unresponsive.

edit: I would still contend this is a bug, but after a bit of messing around I noticed the flight director was off, turned it back on followed by the autopilot and was able to re-engage the lateral and vertical modes and continue the flight as normal. Esc to the menus should not cause that so I would affirm again that this is a bug and will report it accordingly.

6

well, i’ve had this happen multiple times, but since according to the moderators it’s “not a bug” i guess i’ll just live with 25% of my longhaul flights failing after 3-4 hours. :msfs:

before he locked the bug-report thread iniBuilds’ Richboy said:

Just for some context, I’ve done 2 this weekend, and 9 total 12hr+ flights without any such issues. Collectively amongst our testers we have over 1000+ hours of successful flighting prior to release, with many long-hauls both real-time and accelerated via time compression. Not to mention the countless other customers out there enjoying these flights as we speak.

clearly we’ve all turned into LLMs overnight and hallucinated the issue. right?

he also recommends turning turbulence to low or off. this is not possible in Career, where it is locked to “realistic” (inverted commas intended).

the issue we’re reporting is NOT the fact that the autopilot drops out during turbulence or due to, say, noise on a controller. that’s understood and normal. the issue is that it drops out and then, without any ECAM warnings whatsoever, cannot be reengaged, leading to the aircraft becoming effectively uncontrollable. the issue is thoroughly descibed here: