richboy2307

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. See for more info: This improves security of the sim and portability of projects across PC/Xbox. 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. So what to do in case of WASM crash? Do not close the sim/restart flight immediately Verify the WASM error message Report the WASM error message with reproduction steps using the guide below. Verify WASM Crash in Sim Step 1. Enable Developer Mode (FS20) Options > General Options > Developers (FS24) Settings > General > Advanced Options 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. Report WASM Crash on Forum Step 5. Paste the WASM Error message and screenshot of the Console obtained in Step 4 above into a forum post WASM Crash Report. Step 6. Take note of what you pressed or things you did, just before you noticed this crash happen. Step 7. Verify if you are able to repeat the crash by following those same steps. Step 8. Please provide the following information Aircraft: A350-900 or -1000 Simulator: FS2020 or 24 Navdata Method: SIM DEFAULT or NAVIGRAPH 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 Specs: CPU, GPU and RAM of your system. Autosave File: Please include the latest ".bin" autosave file prior to your crash. Step 9. Where possible, include on your report a Screenshot / Video showing what you pressed/did just before the crash happened to give us more clues. steps on how to reproduce the crash so that we can try ourselves with debugging tools to identify the cause of crash. The Autosave File, include the latest ".bin" autosave file prior to your crash to help us reload into same scenario. FS24 Autosave Folder Paths - Steam: %APPDATA%\Microsoft Flight Simulator 2024\WASM\MSFS2024\inibuilds-aircraft-a350\work\autosaves - MS Store: %LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\inibuilds-aircraft-a350\work\autosaves FS20 Autosave Folder Paths - Steam: %APPDATA%\Microsoft Flight Simulator\Packages\inibuilds-aircraft-a350\work\autosaves - MS Store: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\inibuilds-aircraft-a350\work\autosaves These types of WASM crashes are actionable depending on your reports of the steps taken immediately before the crash happened. If reproducible on our end by following the same steps, can be debugged and resolved more efficiently.

The iniBuilds A350 Airliner simulates the MFD Controlled Backup EFIS and AFS Control panels which can be used in case of inoperational buttons/equipment. If you find yourself with your EFIS CP displays blank as above, ensure that on the MFD FCU BKUP page that EFIS CP BACKUP is disabled as follows: On the MFD Menu Dropdown select the FCU BKUP option Ensure you are on the EFIS CP page and verify that the the EFIS CP BACKUP button light is off (not green)

The iniBuilds A350 Airliner simulates the MFD Controlled Backup EFIS and AFS Control panels which can be used in case of inoperational buttons/equipment. If you find yourself with your EFIS CP displays blank as above, ensure that on the MFD FCU BKUP page that EFIS CP BACKUP is disabled as follows: On the MFD Menu Dropdown select the FCU BKUP option Ensure you are on the EFIS CP page and verify that the the EFIS CP BACKUP button light is off (not green)

Changing Weight Measurement Units (LBS / KGS) The aircraft weight measurement units (LBS / KGS) are changed on the OIS Settings Page which can be reached via FLT OPS MENU > OPTIONS > OIS SETTINGS. Select your desired unit by clicking on its respective button. (Click to enlarge image)

Changing Weight Measurement Units (LBS / KGS) The aircraft weight measurement units (LBS / KGS) are changed on the OIS Settings Page which can be reached via FLT OPS MENU > OPTIONS > OIS SETTINGS. Select your desired unit by clicking on its respective button. (Click to enlarge image)

The iniBuilds A350 Airliner simulates the realistic boot time for the On-board Information System (OIS) by default. During the boot-up the computer that powers the OIS is turning on and running through its system checks. Change OIS Boot Time You can change the OIS Boot Time via the OIS Settings page (FLT OPS MENU > OPTIONS > OIS SETTINGS) REAL: Set by default - can take up to 10 minutes. FAST: Can take up to 5 minutes INSTANT: Will boot up instantly upon availability of GPU/APU power.

The iniBuilds A350 Airliner simulates the realistic boot time for the On-board Information System (OIS) by default. During the boot-up the computer that powers the OIS is turning on and running through its system checks. Change OIS Boot Time You can change the OIS Boot Time via the OIS Settings page (FLT OPS MENU > OPTIONS > OIS SETTINGS) REAL: Set by default - can take up to 10 minutes. FAST: Can take up to 5 minutes INSTANT: Will boot up instantly upon availability of GPU/APU power.

This is not a bug. When beacon lights are turned on the Chocks & GPU are disconnected by design. Ensure you are on APU power with APU fully running before doing so. Thanks!

Hi all! Close the sim. Ensure you're on SU1 Beta (Mandatory for FS2024): Clear your WASM folder Then relaunch the sim and load directly on a runway. That will help force a clean WASM compile. Navigraph Users: On initial load, go to OIS FLT OPS MENU > OPTIONS > 3RD PARTY page and link your Navigraph account. Then ensure you have updated to the latest AIRAC cycle. After updating, restart the sim. Thanks!

I have just tried a flight on 4X again and am not able to reproduce any issue (A350-900, Cathay, VHHH-RJTT, FS24, Accel Up To 4X). Please ensure the following: Ensure on SU1 Beta Ensure all assist are Disabled Use "Low" turbulence settings via Assistance Options (helps mitigate random AP disconnects due to excessive turbulence) Check control bindings and ensure no conflicting binds for trim or control inputs. In case you continue to have issues, please provide Route OFP (Attach PDF) Sim Used (FS 20 or 24) OIS Navdata Setting (SIM DEFAULT or NAVIGRAPH) Variant (A350-900 or 1000) System Specs (CPU, GPU, RAM) Sim Rate used (2x, 4x) Any other 3rd Party utilities running with sim (FSRealistic/FSUIPC etc.) Screenshots / Video recording of the crash We need the above data to try to reproduce the conditions in which you have had problems such that we can try to identify any issues. Thanks!

Thanks bug is noted.

The iniBuilds A350 Airliner for MSFS 2020 and 2024 uses Web-Assembly Module (WASM) to run its code in the simulator environment. As with all other WASM aircraft, the simulator needs to compile the necessary WASM files on first launch. However it will be much faster to load on subsequent launches. In case your sim crashes or you exit to menu during this initial WASM compile, please see the guide below to clear your WASM folder and try again:

The iniBuilds A350 Airliner for MSFS 2020 and 2024 uses Web-Assembly Module (WASM) to run its code in the simulator environment. As with all other WASM aircraft, the simulator needs to compile the necessary WASM files on first launch. However it will be much faster to load on subsequent launches. In case your sim crashes or you exit to menu during this initial WASM compile, please see the guide below to clear your WASM folder and try again:

Hi all! Close the sim. Ensure you're on SU1 Beta (Mandatory for FS2024): Clear your WASM folder Then relaunch the sim and load directly on a runway. That will help force a clean WASM compile. Navigraph Users: On initial load, go to OIS FLT OPS MENU > OPTIONS > 3RD PARTY page and link your Navigraph account. Then ensure you have updated to the latest AIRAC cycle. After updating, restart the sim.Thanks!

Thanks all. Yes SU1 Beta is mandatory for FS2024 users as it is has vital fixes required for smooth operation of the A350. Instructions on how to join/leave the Beta linked in below post: Thanks!

Hi @William Skaane If you were not charged, then please try to repurchase via webstore (https://inibuilds.com/), then download via the iniManager after. If you were charged but didn't receive the product, then share your proof of purchase/payment with Direct Support at https://inibuilds.com/pages/contact Thanks!

Hi @theChemist It works by pausing your sim anytime the AP is disconnected whilst Time Compression (2x or more) is active. It doesn't work without Time Compression set to AUTO and shown as active in green at the top of the OIS. Thanks!

Hi For those of you experiencing these issues, first of all ensure all the assistances are disabled per below: Also ensure you do not have any conflicting keybinds (keyboard or other controllers) related to RUDDER, AILERON or PITCH TRIM set in your control settings. Thanks!

Note: On the iniBuilds A350 Airliner (v1.0.0), please make sure that if you change SID/STAR/APP or RUNWAY that you have your ICAO of your airport shown on the F-PLN page with the expected runway. Example if your flight plan page shows EGLL but you have inserted a runway and STAR along with ILS then reselect them until you have EGLL27L shown on the F-PLN page, this goes for all airports. If not done the aircraft can possibly not work out the VNAV path and cause a WASM crash.

Note: On the iniBuilds A350 Airliner (v1.0.0), please make sure that if you change SID/STAR/APP or RUNWAY that you have your ICAO of your airport shown on the F-PLN page with the expected runway. Example if your flight plan page shows EGLL but you have inserted a runway and STAR along with ILS then reselect them until you have EGLL27L shown on the F-PLN page, this goes for all airports. If not done the aircraft can possibly not work out the VNAV path and cause a WASM crash.

Hi @msujim8 It will go up to 4X as suggested, meaning if the aircraft senses based on sim telemetry data that your pc will be able to handle 4X, it will scale up accordingly. If not it will sustain max possible. This is by design and unlikely to change for stability reasons. Thanks!

@eth.74English only please.

Hi @Hans-Peter Benz Close the sim. Clear your WASM folder. Then relaunch the sim and load directly on a runway. That will help force a WASM compile. At the moment it seems like your WASM is not initializing at all (sim issue). Let us know. Thanks!

Hi @drewc3350 Please follow the linked instructions to update to SU1 Beta

Hi @flor4s Should be these 2 LVARs with a value of 0 to 100%. Backlight: INI_FCU_INTEG_BRT Display: INI_FCU_DISPLAY_BRT Thanks!