All Activity

Thank you for the update, Jamir.

It seems the 1.0.9 Updates has broken the A300 .. Unclear status at loading Many clickspots not working at the overhead, buttons off Radio / Tuning Panel not working Startup impossible..... Guys, who has made QA for this update..... Reinstalled, cleared WASM etc... no changes ...

This is a known issue regarding the A300 and A310 in SU5. We have not received any additional information regarding the action plan for this issue at this time. This is an Asobo-acknowledged sim bug since SU5 Beta that has inadvertently broken the way specific types of clickspot interaction points are rendered dependent on zoom levels and resolutions. This will affect any aircraft coded with this specific type of interaction required for protruding 3D objects that move outwards on interaction. You can test it yourselves by enabling Developer Mode > Tools > Behaviours > Debug > Interactions. You'll note it works perfectly as intended in dev mode, but breaks without it. We don't have any viable workaround so cannot address it our end alone unfortunately in any way that will still make the switches behave as they ought to.

Please correct cockpit interactions with VR controllers. Right now it is not usable.

I've logged this for the team, thank you :)

Logged for the team :)

Hi, this has already been logged for the team however it appears I never responded indicating as such. That said the forums are not for show and just because one of us doesn't respond immediately doesn't mean that it hasn't been seen and actioned on. Thank you :)

Hi, this is because of two reasons; the first is due to how the team worked around some funky terrain to make the runway at EGLC appear authentic to it real world counter-part and the other being that the MSFS Failures don't exactly interact to well with both 3rd Party Aircraft and scenery and can sometimes trigger the "Crash Event" for said in game failures. It is recommended to disable all of the MSFS Failures that can be found in the Game Assistances menus. Let me know if this helps.

Have you installed any 3rd party liveries or mods specifically for the A350-1000? If so it's possible that this could be causing the crash on loading for one but not the other

Just wondering. Has this even been picked up by the devs, or is this forum just for shows? It's been over a month since I posted this but the silence is deafening.

Hello all 👋🏼 I recently brought the 350 series from inibuilds and i was wondering if anyone knows why my sim crashes to desktop loading into a flight with the A350-900 but the A350-1000 works completely fine I’ve tried deleting my wasm folder, uninstalled and installed but no no avail

I just flew the A300F yesterday for the first time in a while and I had these click spot issues as well on console. I was going to make a topic about this but it looks like that has already been done so here I am just throwing my hat in to the ring letting people know that I to have this exact issue.

Just got a marketing email that included v1.0.8 of the TriStar having been submitted to the Marketplace, and I figured I'd ask one question: when will the flight model be among the fixes? I've been waiting for certain aspects of the flight model to be made more realistic for a couple of months. I've seen posts saying that, among other things, it shouldn't be able to climb at 1,500fpm above FL300 and the deck angle on approach is several degrees too low, and those things now greatly annoy me every time I try to fly it, to the point where the only times I've flown the aircraft have been to test it after an update. So with every update since probably v1.0.3, I've been hoping to see those aspects of the flight model be modified based on that feedback, and I've been sorely disappointed each time so far. I still hold out hope that v1.0.9 will include this, but I'm starting to really wonder. To be clear, I think I speak for everyone when I say I very much appreciate all of the systems fixes that have been done so far, but I just really hope the team doesn't neglect other important areas such as this.

I have the crash while loading the "flight" obviously

This is "Parking 255" in the list of parking spaces.

When spawning into cargo ramp 8 with the A300, the plane is badly misaligned with the apron markings.

As mentioned above, we have been trying but don't have any viable workaround at the moment for what appears to be a platform-level bug with how its rendering the clickspots. Should we find one that works, it will be pushed via an update but barring that it remains an issue that needs addressing sim-side. Thanks!

A known issue since SU5 Beta, please see:

Now you can. Try on v1.0.9. If you do happen to get a crash, please follow this guide to report the CRASH variables as well.

Hi everyone, unfortunately with v1.0.9 a lot of buttons, especially in the overhead (haven't tested every single one yet) have their clickspots greatly reduced in size. It's only about the size of the red square in the following screenshot: It's basically impossible to properly push these without being close up. This is the same across all variants. Can you please check? This makes the plane kind of hard to control once airborne. Cheers!

Hi everyone, thanks for the latest update. Unfortunately, a little artifact sneaked into the latest release. There's a black thing floating above the innermost spoiler hinge on the right wing: Maybe something to quickly remove for the soon to come second update? Cheers!

Hello dear Inibuild team, I have got an issue when landing at London City, whatever the plane : I get the "tire malfunction warning" from MSFS just before touchdown and the plane stops on the runway and is completely stuck, there is no way to get it to move again (moving brakes, TOGA...) I had this issue with both Just Flight Avro RJ and Fenix A320. This problem only appears with this airport. Scenery version V1.0.1 Thank you, Your sincerely Ecdis

I would love for Inibuilds to do their own KLAS. The Fly Tampa KLAS has never performed well for me whether it was in 2020 or 2024. I feel like if Ini did this, it would be a huge success.

What is WASM?The WebAssembly Module (WASM) is a container for running programmes written in other langauges (eg C/C++) that is then converted to native code ahead of time (as DLLs) during first launch (WASM Compilation). This helps improve performance for subsequent uses but causes longer load times on first launch. his also improves security of the sim and portability of projects across PC / Consoles. In case of issues, only the WASM crashes instead of the rest of the sim along side with it. This is why the sim and some functions may continue to work, however other systems and displays that use WASM on the aircraft become unresponsive or "freeze" in place with a red warning screen. So what to do in case of WASM crash?Do not close the sim/restart flight immediately Verify the WASM error message & crash LVARs Report the WASM error message & crash LVARs with reproduction steps using the guide below. Verify WASM Crash in SimStep 1. Enable Developer Mode FS24 Settings > General > Advanced Options FS20 Options > General Options > Developers Step 2. Enable the Console by pressing "~" key on your keyboard or using the Dev Toolbar at the top of the screen Step 3. Filter the Console by ❌Error messages only by clicking on ⚠️Warning and ℹ️Messages to disable them (remove blue box border around them). Step 4. Type 'WASM' in the search box. Find the WASM Error and Copy the message. Also take a screenshot of this console window for making a report. Step 5. Check the new CRASH LVARs via the Behaviours Menu. Also take a screenshot of this for making a report. Accessing Behaviours Menu FS24 Via the DevMode toolbar at the top, select Tools > Behaviours and navigate to the Variables tab. Uncheck "Only Show Variables get/set....". Type 'CRASH' in the search box and expand their name to display the values. Report WASM Crash on ForumStep 6. Paste the WASM Error message, screenshot of the Console and INI_CRASH LVARs obtained in Step 4 and Step 5 above into a forum post/discord message/ support ticket WASM Crash Report. Step 7. Take note of what you pressed or things you did, just before you noticed this crash happen. Step 8. Verify if you are able to repeat the crash by following those same steps. Step 9. Please provide the following information Aircraft: A300 PW Freighter Simulator: FS2024 Navdata Method: SIM DEFAULT or NAVIGRAPH BASE OFP: Include a PDF of your Operational Flightplan (OFP) if related to FMS/Route Procedures crashes WASM Error: The error you copied in Step 4 above Crash Variables: The variables you screenshotted in Step 5 above Specs: CPU, GPU and RAM of your system. Step 10. Include on your report a Screenshot / Video showing what you pressed/did just before the crash happened to give us more clues. Screenshot of the Crash Variables Steps on how to reproduce the crash so that we can try ourselves with debugging tools to identify the cause of crash. These types of WASM crashes are heavily dependent on the actions taken just before the issue occurs. Detailed reports of the exact steps leading up to the crash are extremely helpful, as if we’re able to reproduce the issue internally using the same sequence, our team can investigate, debug, and resolve it much more effectively.

I had this WASM crash when I clicked the insert flight plan key on the left MCDU To reproduce Load at gate Power on aircraft (Battery, GPU) Click on insert flight plan on the left MCDU Systems freeze Information Aircraft: A340-300 Simulator: FS24 Navdata Method: NAVIGRAPH OFP: Not required, happens on any route Specs: Ryzen 9800X3D, RTX 4090, 64GB RAM Autosave: N/A WASM: Error during XPDR_gauge_update execution. Error code : 0xc0000005 WASM: Module vfs://inibuilds-aircraft-a340/SimObjects/Airplanes/inibuilds-a340/attachments/inibuilds/Function_A343_Interior/panel/inibuilds-A340.wasm is now dirty EDDFLEPA_PDF_1782494650.3681dcea.pdf