Inibuilds A300 Master WASM Crash Thread 1.0.8 FS2024

This thread will be the new location for all WASM Crashes relating to the Inibuilds A300-600R for Microsoft Flight Simulator 2024

Below this message will be where users can upload their WASM Crashes pertaining to the current version of the A300.

NOTES: If you do not see orange expectations screens on your displays or "WASM exception in X gauge" in the developer console it is not a WASM crash. The "sim-freeze" is a separate event that is tied to something on the server side which we are investigating with Asobo.

Investigations will only be opened into WASM crashes once they have been confirmed to be reproduceable.

              All WASM Crashes existing in this thread will be removed following the release of a new update.

                    i.e. Any Crashes identified in Inibuilds A300 1.0.8 will be removed from the post following the release of 1.x.x and so forth.

Please ensure that when posting WASM crashes you post the WASM log from the in-game console alongside any media (photo/video) and a brief description of what you were doing leading up to the crash. Instructions on what to do are located in this thread - 

Thank you.

Aircraft - A300-600R Premium v1.0.8 -> A300-600F GE

Simulator: MSFS 2024 1.7.27.0

Version: 1.0.8

Navdata: Navigraph

Route - LPPR/35 N0468F330 MANI2W MANIK DCT ABRIL DCT XAMAX XAMA3B LPPT/20 (OFP attached)

Livery - Walker Air Transport Red Digital

WASM Error: WASM: Module vfs://inibuilds-aircraft-a300-600/SimObjects/Airplanes/A300-600/attachments/inibuilds/Function_Interior_Freighter/panel/inibuilds-A300.wasm is now dirty

Specs: 5800x3D / 4070ti / 64GB

Aircraft on battery and external power. IRS perfoming alignment. OFP and weights imported on EFB. INIT pages in FMS updated. Then entering the route detais. Deperture SID was entered and inserted no issue.

When entering the STAR details in the FMS the WASM occured when selecting the UPKAT transition for the STAR XAMA3B. This was repeatable twice in a row after restarting the sim for the second test and WASM -> I selected ILS 20 then XAMA3B and when selecting UPKAT transition ... WASM

Autosave File:  This does not seem to exist as per the A340 example given. There is no 'autosaves' folder in the WASM data for the A300 as per attached image.

LPPRLPPT_PDF_1778679466.pdf

Edited May 13May 13 by Woolies

Setting up STAR for a flight to EIDW when the screens went orange. V.1.0.8

• Aircraft: A300 Freighter PW

• Simulator: FS2024

• Version: SU5, iniManager

• Navdata Method: Navigraph

• Specs: 9800 X3D, 5090, 64 GB RAM

WASM: ERR_FATAL_FILE_ERROR (-239 / ffffff11)

WASM: Error -239 / ffffff11

[fsdt-msfs-bridge.wasm] fsdt-msfs-bridge: Simconnect Dispatch proc set.

WASM: Impossible to get user aircraft

[flowmodule.wasm] [FL][ERROR] Failed to get CAMERA STATE from SimVars: -1

WASM: Error during FMGS_gauge_update execution. Error code : 0xc0000005

WASM: Module vfs://inibuilds-aircraft-a300-600/SimObjects/Airplanes/A300-600/attachments/inibuilds/Function_Interior_Freighter/panel/inibuilds-A300.wasm is now dirty

EDDPEIDW_PDF_1778906271.3ea2187c.pdf

Edited May 16May 16 by LukeFF

Exact same problem as yesterday - crashing while setting up the FMS.

Not bothering with going through all the nonsense of posting what happened. It's simple enough to reproduce.

9 hours ago, LukeFF said:

Exact same problem as yesterday - crashing while setting up the FMS.

Not bothering with going through all the nonsense of posting what happened. It's simple enough to reproduce.

Have had the same issue as you several times. Now just recently after a 3,5hr flight about to enter the final airspace. Not providing any logs since I ragequit and you're having the same issue. Have been able to reproduce this issue 3-4 times in my 5 days of owning the aircraft simply by just selecting or changing a STAR.

On 5/17/2026 at 7:47 AM, Cotton_EJ said:

Have had the same issue as you several times. Now just recently after a 3,5hr flight about to enter the final airspace. Not providing any logs since I ragequit and you're having the same issue. Have been able to reproduce this issue 3-4 times in my 5 days of owning the aircraft simply by just selecting or changing a STAR.

Hi, it would be appreciated if next time you can provide the route you did so and whether it was sim data or Navigraph and which variant of the aircraft. You are correct that in some instances this is happening more often than not, but sometimes this can be on a route per route basis or even between Departure and Arrival airports, one or the other and vise versa. If I go into the sim and load a flight there is a chance I won't get a WASM crash and then the viability of the testing and reproducing is already lost whereas if you tell us which route you were on when you had the crash, which is visible in the image above, then if I go in and try this route 5 times and get a crash even once or twice; it now gives us more to look at and investigate into. Thank you

47 minutes ago, IniJamir said:

Hi, it would be appreciated if next time you can provide the route you did so and whether it was sim data or Navigraph and which variant of the aircraft. You are correct that in some instances this is happening more often than not, but sometimes this can be on a route per route basis or even between Departure and Arrival airports, one or the other and vise versa. If I go into the sim and load a flight there is a chance I won't get a WASM crash and then the viability of the testing and reproducing is already lost whereas if you tell us which route you were on when you had the crash, which is visible in the image above, then if I go in and try this route 5 times and get a crash even once or twice; it now gives us more to look at and investigate into. Thank you

Hi Jamir, thanks for your response. As I mentioned I closed the game in disappointment when I got the WASM crash, this was a longer Vatsim event I had planned for for a few days so I didn't remember to get the WASM logs. However I should be able to add more information regardless:

To Reproduce:
Loading a STAR is the only thing that's caused a WASM crash for me so far. The plane is awesome otherwise.

First crash was into EDDP: initial STAR loaded fine but switching to another one crashed it. Latest time, no pre-loaded STAR in FMS; selected one near arrival and it crashed. Other flights, choosing or swapping STARs worked fine. Hit and miss.

Aircraft: A300-600 Freighter PW (Premium)

Simulator: FS2024

Version: 1.0.8 IniManager

Navdata Method: NAVIGRAPH

OFP: Include a PDF of your Operational Flightplan (OFP) if related to FMS/Route Procedures crashes

WASM Error: Not provided

Specs: CPU: AMD Ryzen 9 9950x, GPU: AMD Radeon RX 7900 and RAM: Kingston FURY Beast DDR5 6000 MHz CL36 64 Gt

Autosave File:  No Autosave folder or BIN file?

EHAMOJAI_PDF_1779005610.2b914fd1.pdf

To Reproduce:
Video (unlisted) is time stamped with moment. WASM crash occurred when inserting the approach data for runway, then STAR, when pressing "Insert" to flightplan:
https://www.youtube.com/live/MpOLidphPJA?si=cUIdGiFJrb0lKD2Z&t=5340

Aircraft - A300-600R Premium (Passenger)

Simulator: MSFS 2024 1.7.27.0 (latest SU5)

Version: 1.1.9 MSFS2024 Marketplace (Installed not Streamed)

Navdata: Navigraph

Route - EDDF/25C N0446F350 ANEK3F ANEKI Y163 HERBI Y164 MOPAN DCT LUTIX DCT BENOT DCT NEMOS DCT NINTU DCT MEBAK DCT REPSI DCT LERGA DCT MINSO DCT NARAK DCT AGN DCT PIPOR L866 PPN/N0442F370 N976 NEA L14 ADINO DCT ELVAR DCT ALAGU DCT USALU USAL9C LPFR/10

EDDFLPFR_PDF_1779642878.9e825734.pdf

Livery - Lufthansa (retro) D-AIAN

WASM Error: Unable to retrieve. When I returned to the simulator to retrieve it, it looks like it was already purged.

Specs: AMD Ryzen 7 9800X3D / RTX5080 / 64GB

Autosave File:  Not available for this aircraft.

Edited 3 hours ago3 hr by theglideslope

Out of curiosity, we're exploring some possible culprits - but the next time you load your sim could you check your console and search "it will use" and send us the screenshot of any console entries? Like this?

Also can you specify if you frequently get crashes/freezes or not?