All Activity

Update: clean reinstall did NOT fix it. To rule out a corrupted download, I fully uninstalled the A380 from My Library, reinstalled it fresh (2.38 GB), fully quit MSFS 2024 on Xbox (not just dashboarded), and restarted. The WASM crash still happens on every load — identical error, inibuilds-A380.wasm, Gauge: DU, all displays orange before I can touch anything. Tested both a runway spawn and a cold & dark start at a gate. So this is not a bad file on my end. It looks like a v1.0.3 regression on Xbox specifically — it went from ~0.3% of loads to 100% right after the update. Happy to test anything you suggest.

Cancel that, I found the switch you referred to. Boris

It's been a while, but I just came across the same issue in v1.08. Rudder Controls Tiller set to NO Tiller deflection with full rudder: Nose wheel deflection with full rudder: Same deflection with full tiller input. Is it supposed to be this way? Boris

Hi team, reporting a WASM crash on the A380 that has gone from rare to every single load. Aircraft: iniBuilds A380 (v1.0.3) Simulator: MSFS 2024 on Xbox (console) Navdata: default Xbox (EFB navdata source not verified) WASM error: "The WASM module has encountered a fatal error and stopped responding." Package: inibuilds-aircraft-a380, Module: inibuilds-A380.wasm, Gauge: DU. All display units go solid orange with the "WASM module crashed" message. On one occasion the new v1.0.3 crash diaog appeared instead. Automatic reporting was DISABLED and no manifest ID was recorded, so nothing was sent automatically. Reproduction (100% — happens on every load): Load the iniBuilds A380 at any airport — either a runway spawn or a cold & dark start at a gate/heavy parking. The displays are already solid orange with the WASM crashed message before I can touch anything. Even on a cold & dark start with every power switch in the OFF position, the screens still show orange with the WASM message. Frequency: this used to happen on roughly 0.3% of loads. Since around Oct 8 (after the v1.0.3 update installed) it is 100% — every load, both runway and gate starts. Notes: I am on Xbox so I cannot provide dev-console output, INI_CRASH LVARs, or the.bin autosave file — none of the PC verification steps apply on console. Happy to test any steps you suggest.

Could be that they’re at an expo so are tied up. Also I’ve heard anecdotally that apparently if you enrol in the SU7 beta that the issue isn’t present, which feels as though it could have been an Asobo issue rather than inibuilds, but they may not have enough info to say that out loud. Obviously that’s just me speculating

Agree about this issue on the A350! But hadn't bothered reporting as was focussing on more systems stuff. Hopefully fixed with v2!

Hello iniBuilds team! ❤️✈️ I play MSFS 2024 on PS5 and absolutely love your airliners! I’m really looking forward to the A340, A350 and A380. I heard rumours about their release a while ago, and I’m ready to buy them as soon as they arrive. Could you please share an estimated release timeline for these aircraft on PS5, even if it’s only an approximate timeframe? It would mean a lot to us console pilots. Thank you! ❤️

Hi, I had the same issue with Beacon and strobe and 100% they were on since start.

Have you tried this:

I apologize if this seems a bit out of place, but isn't the entire point of having a support-forum to get support for bugs or other issues regarding a product instead of having a forum and being referenced to another platform?

I thought I would test out the Jump to waypoint feature and I think I may have found a bug. Not sure if this has been reported. Did a search and could not find the exact issue. After using the feature, I noticed that my FLT time show was now showing a lot less than what it was before the jump. I had the chrono going as well and you can see the difference in the screenshot. Because I started the chrono at the start of the takeoff roll, the two were about a minutes apart all through the flight till I did the jump.

WASM module has encountered a fatal error and stopped responding.

@iniKyle

Well, I believe they will get back to us. Be patient. They have a very good Customer Service track record.

Hey Inibuilds Team? Any update, reaction, answer whatsoever? Why are you completely silent? Not only in this thread but also to other users commentating the same issue. This is a dealbraking issue that needs to be addressed.

Unfortunately I can confirm that this is no solution (at least on Xbox): I tried uninstalling and reinstalling with the same effect of orange screens. Why is Inibuilds silent on this? This is not a small bug, annoying but bearable. This is a critical problem preventing us customers of using the product which we payed 80 Euros. The least they could do now is address the issue in the first place.

Ok forget it. On my present flight I gained 9 tons of fuel in 5 hours flight time. This is ridiculous! I tested it with v1.0.1. Unfortunately there's is nothing about this issue in the last 1.0.3 update. Kyle? Any news on that?

Hi inikyle, one more thing about the additional improvements to the fuel simulation in case this one is planned to be implemented. It is not just the fuel FOHE being clogged, but also the fuel filter. This introduces unique challenges to long haul ETOPS flight Caption: Since the FOHE is clogged, the engine behavior might get affected resulting in increased oil temperature with OIL TEMP HI and FUEL FILTER CLOGGED alerts. Since center tank not usable, it might be nose heavy. The logic should be applicable to the a380 but with a different procedure. And one more thing, its weird that the current a350 has no triggers related to EGT exceedance. Because according to FCOM, more than 900C EGT should trigger the respective ECAM alert: Then finally, since you guys have implemented the dynamic vibration, try to add a chance of fan blade and cowling loss similar to the Air france 066 a380 incident in order to add consequences for mishandling the failure. Caption: Mishandling the engine failure whether oil, FOHE, EGT, engine fire, or engine vibration must have serious consequences. If this is not allowed to be modeled externally due to legal reasons, then maybe a vibrating cockpit and cabin due to the aerodynamic changes of a cowling loss will suffice due to this. And a low oil pressure/leak should give symptoms to the engine like abnormal high EGT, vibration, FADEC altn, GENERATOR faults before finally giving out to an engine seizure. Hope it helps!

yes

Can someone from iniBuilds please officially acknowledge the Xbox WASM crashes introduced with A380 v1.0.3? Multiple Xbox users are reporting the same issue, and the aircraft is currently unusable for us. Has this been logged with the development team, and is a hotfix being investigated? Even a brief update would be appreciated so we know this issue is being taken seriously.

I have the same issue

Same issue here, but it resolved after running the update on the EFB and restarting the sim. The new cycle showed up as ready to update.

thanks for the help :) @iniKyle

There’s any estimate timeline?

Apparently, this is the solution. I haven't tested it myself yet. I can't remember where I got it from. Somebody posted on another post here, "The MSFS Marketplace is a nightmare. The update functions don't work properly. There are two ways to update the A380 without issues, depending on whether you have it installed or are streaming it: 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. Don't forget to check the IniManager for updates to the LowRes textures and liveries as well."