All Activity

I confirm all the above problems. The aircraft in the beta version is not loaded, only the cargo version. I had to exit the beta version and the plane booted normally. Apparently version 1.0.12 is incompatible with the beta version of MSFS2024. So don't worry in vain. Troubleshooting steps will not help.

My GSX staircase has no response. I downloaded the GSX configuration file for the A380 from the forum, but when I'm on the tarmac, these stairs don't dock at the position of the cabin door. I tried reinstalling, but it didn't work

I can report the same, even with quite a good setup. NVIDIA GeForce RTX 5090, 9800X3D and 64 GB memory.

no Beta in use :)

Anything other than a PC is, in any case, the biggest disaster for flight simulation since the release of MSFS2020.

Given multi jetways is not supported at OMAA this is relatively self explanatory The external jetways in a GSX profile won't be present at this airport for GSX cause well it doesn't have multi jetways And yes, we can assume it will be added in a future update because well A380's fly in, out of Abu Dhabi to. A different setup wouldn't be required either, that one is also self explanatory.

Thanks for clarifying, iniKyle. Just to make sure I understand correctly, if OMAA doesn’t currently support the Multi-Jetways tool, is the GSX profile shown in iniManager intended for the regular GSX setup only? Also, is Multi-Jetways support for OMAA something that may be added in a future update, or is there a different setup required to use multiple jetways there?

Hello iniBuilds team, I am experiencing a serious and recurring systems issue with the iniBuilds A380 for Microsoft Flight Simulator 2024. During cruise, without any warning or apparent abnormal indication beforehand, the aircraft suddenly reports: ENG ALL ENGINES FAILURE LAND ASAP The aircraft still has sufficient fuel when this occurs, so there does not appear to be a legitimate fuel exhaustion reason for the LAND ASAP warning. The most concerning part is what happens after the failure occurs. After the ENG ALL ENGINES FAILURE / LAND ASAP event, when checking the ECAM and TCAS systems, the entire System 2 appears to be in a FAULT state. The IRS NAV 2 system also becomes inoperative after the failure. When checking the overhead panel, IRS 2 is still correctly set to NAV, but IRS NAV 2 does not function. The selector remains in the NAV position, so there is no change to the selector setting that would explain why the system stops functioning. This makes it appear that IRS 2 is correctly configured to NAV on the overhead panel, but the IRS NAV 2 system itself is no longer functioning properly. The issue therefore does not appear to be limited to the engines. It seems that the failure may also affect the aircraft's System 2, IRS/ADIRS, electrical system, or failure-management logic. The failure can occur unexpectedly during cruise without any obvious preceding event. After the failure occurs, I am able to restart the engines and attempt to recover the aircraft. However, even after successfully restarting the engines and returning to the planned flight route, the same issue occurs again and the engines eventually shut down completely once more. This means that the problem is not limited to a single temporary engine shutdown. Even after restarting the engines and recovering the aircraft back onto the planned route, the same failure can recur and result in another complete engine shutdown. Because the A380 is primarily used for long-haul operations, this issue makes it extremely difficult to operate the aircraft reliably on realistic A380 routes. The aircraft can appear to be operating normally during cruise and then suddenly enter an emergency state with ENG ALL ENGINES FAILURE and LAND ASAP, and the failure can recur even after the engines have been restarted and the aircraft has returned to its planned route. Could you please investigate the following? 1. Why can ENG ALL ENGINES FAILURE occur suddenly during cruise without an apparent preceding failure? 2. Why does LAND ASAP appear even when sufficient fuel remains? 3. Why does the entire System 2 become FAULT after this event? 4. Why does IRS NAV 2 become inoperative even though IRS 2 remains correctly set to NAV on the overhead panel? 5. Why does the same failure recur even after the engines have been restarted and the aircraft has returned to the planned flight route? 6. Is there a known issue with the A380's electrical system, System 2, IRS/ADIRS, or failure-management logic that could cause these symptoms? 7. Is there currently any recommended procedure to recover the aircraft from this state or prevent the problem from occurring? Additional Information - Aircraft version: iniBuilds A380 v1.0.1 - I have already completely uninstalled and reinstalled the aircraft. - All auxiliary functions have been disabled, except for the MSFS turbulence settings. - I have completely removed all mix ratio controls and axis assignments for all flight control devices, including the yoke, joystick/stick, and throttle. - Consequently, no mixing inputs are being sent from any connected flight control devices, so accidental mixing inputs have been ruled out as the cause of this issue. Thank you for investigating this issue.

The pitch behind the wing from the flaps is an A. There is also a very slight undertone of G sharp beneath the flaps in some clips if you listen closely like this one:link

I've noticed that there are no PAPI lights on either end of runways 9L/27R and 10R/28L. Has anyone else experienced this problem? No other KORD sceneries are enabled. Thanks,

I’m having the same issue. 1.2.6 SIAI API key is enabled. Can’t get departure ATIS. only arrival. Send an update buttons are grayed out.

So I was able to complete a 12 hour long haul flight - this was the first time I successfully completed an end to end long haul on the A380. I want to run a few more flights to build confidence before I declare the issue is solved - but there are a handful of things that I did. I'm not sure which one of these steps (if not the combination of multiple) prevented access violation and memory errors leading to a MSFS CTD when using the A380. Fresh-Installed and updated Nvidia drivers to latest (617.14) The previous driver was what I was using when the CTDs occured. Increased Windows Memory Page File Size, and added an additional page file on the SSD that MSFS is installed on. Downgraded DLSS Swapper FG Preset from v310.9.1 to 310.7. Going to try 310.8 next. Cleared A380 WASM folder, disabled addon in library, deleted residual files from "streamed packages" and did a complete clean install of the A380. Disabled Navigraph Charts. Disabled FSLTL Injector (During Cruise, turned it back on during approach and had it on during takeoff) Turned off the EFB on both sides after takeoff, kept it off the entire cruise, and turned it back on after landing. Downloaded the "A380 reduced texture pack"

Might be a different problem for them since in my case AOC FLT INIT was still working, but not INIT REQUEST. Still thought I'd chip in with my edge case however.

As a current workaround, even though the aircraft doesn't let you change the ZFW when you're airborne, you can update the fuel. Increase the fuel to an amount that will give you a proper GW for current part of flight. I up the fuel from the OIS loadsheet page until the landing weight resembles the expected landing weight from simbrief. You can check the aircraft expected landing weight on the fuel&load page. As you can see it gives me way more fuel than I need but at least the aircraft gross weight is now correct, giving you accurate performance for the remainder of the flight and an accurate gross weight and estimated landing weight. (I know i'm 5.0t out here but you get the idea)

Hola. Porque no soy capaz de hacer girar la rueda de morro?. Tampoco consigo que el avión se mueva cuando doy gas despues del pushback. Me salen 2 avisos en pantalla de mal funcionamiento de las ruedas y mal estado de las ruedas

Hm. I’ll check it again tomorrow but didnt see it on reinstall this morning. Actually looks like I may have the wrong version. I think mine says it was last updated in like 2022 or so. Tx Kyle.

Hello, same problems here with different hardware. Using Inibuilds A380 V 1.0.1. Hardware and configurationThrottle quadrant: Thrustmaster TCA Airbus (2 hardware axis) Reversers on axis: On Input Axis Count: 4 Keybind: Throttle 1 and 2 Axis: Axis X Throttle 3 and 4 Axis: Axis Y Issue description‘Input Axis Count 4’ and ‘Reverse Axis ON’ were already preset following the installation of Inibuild A380 V1.0.1. Therefore, I did not restart the sim and began the calibration straight away. Once the calibration was complete, I restarted the sim and the Xbox. The throttle stages are correctly mapped in the EFB. Full Reverse and Idle Reverse work in the calibration window in the EFB. Unfortunately, however, Thrust Reverse does not work in the A380 itself. The thrust levers map all positive settings (IDLE, CLB, FLEX/MCT, TOGA) correctly. This makes the A380 very easy to fly. However, the reverse functions do not respond to either Full Reverse or Idle Reverse. They remain in IDLE mode. Additional informationThe thrust reversers work with the same hardware on every other aircraft in my MSFS2024, particularly on all in-built aircraft (A300, A320, A321, A330, A340, A350, A400). QuestionsAre my settings correct? What can I do to make my reverse functions work properly?

HI, Thank you for this beautiful aircarft. Everything about the operation of the A380 works just fine, but I seem to be having some issues with GSX passengers and cargo loading. There are no seated passengers after loading and loading and unloading 480 passengers only takes a couple minutes (weird). During Cargo and luggage loading and unloading, the iniA380 doors open as expecetd, but there are no GSX ramp agents or GSE. This works fine with all other aircarfts so I am not sure how to fix this. What I tried so far was run GSX config, uncheck and recheck ini A380. *Update: After carefully looking at GSX config, I just noticed that there is NO iniA380. Was there supposed to be? Any idea how to fix this?

Just a tiny detail but I noticed that after updating to V1.0.1 , "No Mobile" cabin sign no longer illuminates when the sign is switched on.

Morning. Still loving the A340, holding back on opening the already purchased A380 till Christmas. Any change one could modify the default passenger seat screens to either a world map, or other more realistic view rather than the inibuilds sign. the world map is common to most airlines, or even a screen showing all the Tv/movie selections, something that is common to all airlines. Thank alot you have brought it to a new level Really hoping for the 747-400. As for scenery hoping for Bangkok, Kuala Lumpur, Maldives, Tahiti, Haneda, oh there are so many more.

Hello Kyle, is there a public bug tracking tool to check before posting here ? ( just to avoid duplicates ;) )

Hello, After the v1.0.10 update all my PFD displays remain black after power up. For a fraction of a second on the pilots right PFD I see the Synaptic Simulations in the white box flash and disappear. I've tried deleting contents from the community and WASM folders, ensuring the marketplace version is disabled, and reinstalling through the ini manager. I'm running a RTX 5080 with latest drivers. I suspect a WASM crash?

Hi Kyle, as mentioned I've already tried changing the refresh rate either via MSFS or the EFB but it did't help it. It doesn't always stutte but sometimes during a flight. It seem to be happening randomly. Regards, Leif

There you go.

Xbox Series X