All Activity

Go to the install location and make sure there isn't a folder there with the same name already. If there is, delete it and run the install again

The Speed window indicator alternating between "SPD" and "MACH" throughout the flight? A bug or normal?speed indicator.mp4

Managed to install after about 10 attempts

I do think this is a bug. Because the A350 doesn‘t have this problem. Whenever I spawn, the A350 will always be in cold and dark state as I set. Also, the A380 FAQ says “Your chosen state will now be applied automatically whenever the aircraft is loaded.”

So, I play with this weight: By Simbrief Calculator, it showing this: But somehow, based on OIS is having difference on the speed: With FLEX / With TOGA There's literally NO DIFFERENCES on the speed between both of them. I tried 3 of them, still the aircraft reached Vr AT THE LAST 1.000 feet. 🤭 For comparison, in another runway, almost the same weight, 4.000m of the runway, FLEX showing at 67 Degrees then I compare with TOGA. But still, both reached Vr at the last 1.000feet with EXACTLY HAVING SAME SPEED. 🤣 I think @iniKyle and team required to adjust Thrust Vector Geometry for this. Cheers! HaveASafeFlight!

Even after updating to Version 1.01 the localiser and the glideslope remains dead and inactive if game is launched from a previous save game. In that case saving a game to continue later is redundant.

I've been investigating quite a lot of scenarios after installing the 1.0.1. I made sure I delete the ThrottleData.ini file, and tested in non-VR as well. While in non-VR - everything works OK. In VR (Pimax crystal light) - after a minute or so, any movement of the throttle through binding to a hardware (tested with multiple hardware units) causes an immediate CTD. To test I created an empty Honeycomb profile and only did a bind to throttle 1 axis. Works OK out of VR but once I switch to VR and I touch the throttle - I get CTD. 100% of the times. The A380 worked great for me prior to 1.0.1. Just to add - I crossed-checked with other aircrafts and the throttle binding in VR works OK. This is something that probably related to the V1.0.1, I believe some throttle code was changed? Issue confirmed on my end - controlling the throttle with keyboard/mouse in VR works OK. Once I bind it to ANY controller and try to move it - I get an immediate CTD. Ini team, can you please please look at this? Other than that it was a GREAT plane to fly (also in V1.0.0) so please examine the new throttle binding code to resolve this.

Disregard I have figured it out, I am dumb. Thanks

I have literally tried everything under the sun from A-Z to stop all those gates from piling up on the bottom of the gauge and they just won’t spread out. New profiles, uninstall, cleared WASM, follow every procedure, usb calibration, etc, etc , etc. The plane just piles all the gates at the bottom of the range and I have no idea why.

When I zoom in to my parked aircraft I see runways but no taxiways. I also see the RWYS ONLY notice. I have a Navigraph unlimited subscription. I uninstalled/reinstalled the A220 and I reinstalled the Navigraph data via the Data menu. I have tried my third party KSEA scenery and the default KMIA scenery. I've tried different zoom levels. Thanks for any help with this. Steve

Hello, Literally just ran into the same issue tonight but in my case it was because I tried to trim my OFP page size generated by Simbrief like so : But it seems that unticking Detailed Navlog messes with a lot of plane. It messed up the import for me on the iniBuilds A340, inibuilds A350, and same for PMDG 777-300ER. I know reverted my defaults to this : and everything is fine 😁

Another way to achieve that could be an option to allow A/T without AP on

WX Radar does work, but do not think it will show something just because You see clouds. A WX radar can only see precipitation. Than 30+ testers didn´t see the issue with the Terrain map is because it only appeared after release on the Market place. If You look at al the pre-release Youtube videos from various content creator, it did work. The A380 has been released in a rather bugfree 1.0.0 state. Normally Inibuilds are quite fast to fix bugs.

I am also getting the same issues. I have done exactly the same as the users above. Intel 13900 / 4090 :(

As far as I know, spawning to a runway will be always with engine running disregarding panel states.

Hello, I have checked for all recent updates and uninstalled/reinstalled and cleared cache. Cannot get Asian liveries on a350/1000. African liveries (Ethiopian) work fine.

My apologies

Negative on 3rd party weather and tubulence is set to realistic

Hi guys ! Since the 1.0.1 update of the A380, the cabin as disappeared. I choose the “EA basic cabin” variant , I tried with also the “RR Basic cabin” but nothing happens.. (The door of the cockpit is opened, the performance mod in the EFB is not active) Thanks for your help 😁

have you tried spawn on the gate?

issue with @SebSch also happening with me, @iniKyle , see the picture below: ALL the Overhead Panel with some Knob placed incorrectly, and also with this Glareshield Panel below: This condition with ELECTRICAL ON (Either on GPU or APU), EFIS CPs (both) with CSTR, VOR1, VOR2, ARPT, TRAF and VORD actively pushed, FCU's FD ON, and Integral Light AT 100%. this is on pedestal: Differences between versions on initial loading (with good connection speed): Version 1.0.0: Exist for the first 30 seconds (sometimes less, on Downloaded Version), Version 1.0.1: Exist for the first 1-2 minutes (on Streamed Version with high bandwidth, low bandwidth may having prolonged time). BUT, since this streamed version, this is also happening during Inflight ONLY when the connection is poor, when transitioning from the external view to cockpit view, but the light resumed normal when the connection is resuming normal bandwidth. So by my experience, whenever the connection speed is drop below certain speed, this will be happening. --ADDITIONAL EDIT-- As for momentarily ALL P/B LIGHTS ON, because of sudden change from external view to Cockpit View, there's momentarily bandwidth spike happens when switching. This only happening on downloaded version, while streamed version is ONLY lost of Integral Light because of low bandwidth. I hope it helps to understand the situation. Cheers! HaveASafeFlight!

**9/26/26 I uninstalled/reinstalled MSFS 24, dumped EVERYTHING and only put what I needed back in for now. Everything appears to be working normally once again.

I don’t think deleting the WASM is the answer. It doesn’t seem to make any difference to me anyway.

I also reset(deleted) my WASM and the plane loaded back up in incredibly quick. Like within a minute. Exited the sim, then came back in and loaded the plane up and it was completely disappeared.... So I once again deleted the WASM and load the sim back up and the WASM loaded up incredibly quick once again.

This is a well known issue and being investigated by the teams. the temp fix I found is spawn to any gate. Then in the sim spawn to the gate you want. If using the A380 use in EFB GSX menu. also in the GSX settings make sure you have auto reposition selected. Multijetway requires accuracy. I think it’s all to do with a WASM file getting stuck and not regenerating each time. See if this helps