All Activity

Nice, are we getting an update today?

Yo thanks m8. I noticed the tail was from performance mode, you’re right. Thanks for the heads up about the cockpit pop ins.

In my case, the crash happened very early during pre-flight, so it doesn't seem to match the arrival/runway-change scenario you described. I had started the aircraft and GSX. GSX integration was disabled in the A380, and I started GSX separately through the Asobo tablet. I also had my usual external programs running, including FSLTL, FS-ATC-Chatter and CABBY. I had imported the flight plan and completed the basic departure setup, including the FMC performance data, but I hadn't made any subsequent changes to the flight plan. I was simply waiting for GSX passenger boarding to finish when the WASM crash occurred. I did not use the SEC F-PLAN at any point. So unfortunately I can't identify a specific button press or F-PLAN modification that triggered it. In my case it appeared to happen spontaneously during the pre-flight/boarding stage.

Hello. I don't know if I'm posting this in the right place but here goes. I am aware that Air Calin are taking delivery of a A350-900. I was wondering if any kind and talented painter out there would consider doing this beautiful livery for the Inibuilds A350-900 for msfs2024. Many thanks in advance.

Hope there will be fix available soon...

Ok, I believe that may be the issue. If you can, uninstall the aircraft and stream it. That should solve the issue. Thanks!

I encountered an issue where the refueling option completely went rogue. I requested 60 tonnes of fuel, and selected the realistic refueling option. Now the refueling will not stop and has even exceeded the maximum fuel capacity of the A359.

I’ve recorded a short video showing the issue. It shows the transition from the cockpit to the external view and then back to the cockpit. When returning to the cockpit, all the lights illuminate simultaneously for a few seconds, as if the annunciator light test had been activated, before returning to normal. I can reproduce the same behaviour in both VR and 2D. Video: https://drive.google.com/file/d/1TF8h-q12ZMcS3QW46GFeok2qbgkoMCFM/view?usp=sharing

Hi, This issue has already been logged and fixed by the team. Thanks!

I’ve just had another WASM crash last night when I got an arrival runway change and modified it accordingly in the F-PLAN. Can I ask you , when you encountered the crash, what specific action did you take that led to it? Also, did you use the SEC F-PLAN by any chance? Asking these questions because these crashes seem to have the same triggers as the A350.

From cockpit movies I've seen so far I can at least confirm that the derated takeoff option is available on Lufthansa, Air France, Qantas, Etihad, HiFly/Singapore Airlines and Malaysian Airlines A380's. The only example I could find so far where the derated takeoff option was missing, was an Emirates A380 with EA engines.

When flying at higher levels, the airplane obviously switches to Mach speed. When trying to Pre-Select a manual Mach speed, the digits appear but are frozen to the managed speed value. For example, when flying managed Mach .84 and going up 4 ticks, the digits stay at Mach .84 but as soon as you pull the speed knob, mach .88 appears.

Something must be wrong. The jetway tool does work for me at all - neither OMDB v2 nor EGLL v1.1.0. I have tried uninstalling GSX - tool does still not work through the EFB, so reinstalled GSX. I have uninstalled an reinstalled OMDB v2, EGLL v1.1.0 and the jetway tool - still no change All installs are located in the Community folder. Windows 11 version 25H2, build 26200.9457 MSFS2024 version 1.8.16.0 rgds Søren

That worked thanks alot

The same as in the A350. This is not supposed to be like this...

Multi jetway not compatible with GSX,for now you'll just have to use gsx for pushback

Just adding another WASM crash report here. Rather ironically, about 10 minutes earlier I had just told my friends that after 2–3 flights in the A380 I hadn't experienced a single WASM crash and that the aircraft had been very stable for me so far. Then I loaded another flight and got this almost immediately. 🙂 This happened shortly after loading the A380 at Warsaw (EPWA, Drzewiecki Design) in MSFS 2024. I was still on the ground and had barely started setting up the aircraft when the A380 WASM module crashed and all displays showed the red WASM crash message. Unfortunately I closed the simulator before checking the Developer Console and INI_CRASH variables, so I don't have the complete diagnostic information for this occurrence. I have attached the screenshot showing the actual crash. I was also running several external applications at the time, including FSLTL traffic, Cabby, FS-ATC-Chatter, Landing Rate Monitor and its traffic component, so I can't say whether any of these contributed to it. I had completed my previous A380 flights without a WASM crash. If it happens again, I won't close the simulator and I'll collect the Console error, INI_CRASH variables and the other information requested in the WASM reporting guide.

I love the current engine start-up and shut down sound of the A380 , its really music to the ears , please do not reduce the sound of this , if its too loud , perhaps a slider to control the booming bass of start-up and engine shut down that pulsates but that should be all , don't reduce the sound or it will be ruined.

Hi team, I’m encountering a problem when trying to bind hardware buttons to several of the new A380 input events using FSUIPC. The bindings do trigger, but the associated cockpit buttons remain latched in the pressed state and never return to the released position — even when sending a parameter value of 0. Events affectedCode AIRLINER_THROTTLE_ATHR_DISC_1 AIRLINER_THROTTLE_ATHR_DISC_2 AIRLINER_SIDE_STICK_DISCO_CPT AIRLINER_SIDE_STICK_DISCO_FO AIRLINER_CPT_TILLER_DISCO AIRLINER_FO_TILLER_DISCO Hardware usedThrustmaster Airbus Joystick (Sidestick) Thrustmaster Airbus TCA Quadrant What happensWhen binding any of the above events through FSUIPC the event is received by the aircraft and the corresponding button in the cockpit visually presses, but: It stays visually pressed permanently Sending parameter 0 does not release it

I also have had similar experiences. Microstutters everywhere at a variety of airports(base game and add-ons). Cockpit textures load in and out when I move my view around the cockpit. Have had many “memory resources low” issues, on initial load of the flight to the gate and also after 5 minutes of beginning prep. Even restarting my sim and Xbox has not stopped this so far I have only managed two flights but they were very stutter heavy. All using performance modes. For such an expensive add-on I hope an improvement comes quickly

Great you like to buy from the MS Store, good for you! I and many others don't also our choice. By saying someone who chooses not to you "don’t believe in the sincerity", you imply that those we are likely to be engaging in some illicit act, without any proof at all, which I find offensive. Every peice of software on my computer has been legitimately bought and paid for. I'm in the fortunate position of having spare funds to allow me to engage in this and many other hobbies. So maybe you should think before making such scurrilous comments.

If I move my joystick, the autopilot disconnects, but I don't hear the usual Airbus autopilot disconnect warning sound.

You need to first select the runway close to the green triangle near the runway then you can select the exit to vacate

The A380 is telling me there's limitations to consider, but the status page is not telling me what is causing this limitation. Anyone knowing where else I can find the root cause of the limitation?

I'd like to add, that if you activate the ARPT Button too many Airports are shown in the ND. Usually only bigger airports are and, forgive me the language, every cornfield airport around. Or am I wrong? Is it a setting? Besides that and the other things mentioned it is a great plane worth the money! Great work!