I just wanted to let you know that the beacon/strobe sequence sync is broken again on v.1.0.5.

Timing between beacon and strobe flashes is again determined by when you turn on the respective lights.

Thanks for checking!

1. If it is being streamed, completely deactivate and then reactivate it. You can find the options for this in the bottom-right corner of the Marketplace after selecting the add-on.

2. If it is installed, please uninstall it completely; then, place the aircraft somewhere using the streamed version before downloading and installing it again.

As long as the aircraft isn't managed via the iniManager, there are no local WASM files, because they are precompiled for consoles. Consequently, you cannot delete WASM files from the usual locations. However, if you wish, you can delete the "work" folder to reset all settings, persistence data, etc.

Please check the Official2024 folder for leftover files related to the aircraft.

Don't forget to check the IniManager for updates to the LowRes textures and liveries as well.

Hi ini devs

tried for the last 4 hours to download it but keep getting this failure. streaming is fine but wont let me download, ive selected another aircraft in free flight but still no luck. any suggestions?

Ini A359 has no issues at the same stand. Jetways move as expected. So seems to be something with A380.

Help! :)

When I try to update the IniBuilds A380 on MSFS 2024 Marketplace from 1.0.3 to 1.0.4 it goes into disabled and in red says Installation failed. Even after a uninstall and reinstall it says same thing. What do I do now?

In your showcase video you present the A380 on a par with A350 performance. I have Performance mode active and FX performance enabled... it's very stuttery at landing and take-off at busy hubs. Ok, I understand it might be, but with the A350 its always very smooth... so, I don't get it, this is the only plane I have issues with. WASM cleared, shaders, scenery indexes... the lot. Issue persists but only with the A380.

My system: AMD 7800X3D, RTX5080, 64GB DDR5 RAM, I use BATC at default settings for traffic, but as I said above this only happens with the A380 with the rest I get constant 80FPS regardless of scenery (thats with FG, so 40 real frames capped).

update 1.0.4 lists this feature has been added

i cant find a way to walk around the cabin please tell me how? walkaround mode still spawns on the ground

thank you

Upon updating the a380 to 1.0.3 and following these steps:

• Uninstall the plane

• Uninstall the liveries

• Go to free flight and select any plane that isn't the A380 (no need to then go into a flight or anything, but just have selected another plane and then clicked save & back)

• Go to settings > online > set rolling cache to 1GB (results in the game prompting you that it will clear the cache)

• Once done, reset the cache to your chosen amount (I've done 64GB - no science behind that choice)

• Install the plane

• Install the liveries

I now have instant WASM orange screens when loading into the sim.

I've tried exiting the game, power-cycling the xbox (including leaving unplugged for 2+minutes) and same behaviour...

Edit: have tried uninstalling the plane/liveries and tried to stream it, same result :(

During use, all of the cockpit interaction points illuminate blue and become highlighted simultaneously. All lights are illuminated for every switch/setting. At the same time, I lose the ability to operate cockpit controls using the mouse. Moving the mouse does not restore normal interaction and I am unable to click switches, buttons, displays, or other cockpit controls. Reverting to a previously saved auto-save point temporarily removes the problem but it reappears again within 5-10 minutes of flying. I also experience a floating knob in the pilot's main window.

I have not experienced this issue when I deactivate VR, but when I reactive VR it recurs.

The problem appears to be associated specifically with VR operation and makes the aircraft effectively unusable once it occurs.

My VR headset is a Pimax Crystal Super.

I would be grateful to know:

1. Whether this is a known issue with the A380 in VR.

2. Whether other users have reported the same behaviour.

3. Whether there is a recommended workaround or change to the MSFS Cockpit Interaction System.

4. Whether there are any A380 WASM, VR, or mouse interaction settings that should be reset or changed.

I am happy to provide further system details, screenshots, video, or log files if these would assist investigation.

Many thanks.

Apologies in advance, I do not know hoe to take a screen shot in VR to illustrate the issue I am seeing.

I run the A380 in streamed Mode. Library in Marketplace Shows me 1.03. EFB shows version 1.01.

What is the Version I‘m running?

Thanks

Andreas

Why hasn't this been noticed? This issue has also occurred on other iniBuilds aircraft and it's been documented.

after the update to version 1.03 I have orange screen (WASM crashes) in every single try to start a flight in cold and dark (I tried multiple liveries at multiple airports). The plane is not usable at all right now.

It went from okay performance (1.0) to bad performance (1.01 - much more memory induced black screens then before) to no performance at all. Honestly, how is this even possible to miss such a critical issue? Did you test the version not even once on a real Xbox before pushing out the update?

This needs to be addressed and fixed ASAP.

Super excited for the a380 to come out on PS5 sometime over the coming weeks. Just a question: I can’t remember where I read it, but I read somewhere it will only release with the default IniBuilds livery and a white one. Can someone confirm this? And if true, can we expect some airline liveries to eventually become available?

Cheers

Even though neither the MSFS 2024 game optimisation nor the overlays are enabled.

If I uninstall the app, the stuttering during take-off and landing disappears.

Once reinstalled, the stuttering returns.

Tested in EDDF and OMDBV2

I’m only speaking for myself, as there shouldn’t actually be any connection. But is there a problem with the A380 and the NVIDIA app?

Anyone knows if it's possible to assign a controller device, UP / DOWN, for the "wheel" as shown in the pic ?

Thanks

the 380 is marvelous but can you please finish the stand alone installer. The marketplace loop is the most annoying thing and takes forever to fix. AARGH

Any timeline on when we can transfer the A380 to our iniMananger accounts to avoid the mess of a circus that is MSFS Market Place? Soon please!!!

NOTE: when only moving a throttle during a scan to the FLX position, a full signal is registered. Moving to TOGA reduces signal strength back to 50%

I currently stream the A380, but tbh, the original download at release was to my PC and the defect appeared then. Uninstall and re-install has zero effect.

For reference, every single other aircraft I use with the Winctrl throttle behaves correctly. Fenix, Ini A350, etc, and has done since Fenix release and Ini A350 release. Nil change to my set up.

Please ingest the situation here....If I am missing a basic setting change, I would love to understand that.