Muffwin

@Eddie I have this error each time I load up the A350 at the gate, but it doesn't prevent me of using the airplane after. I don't know if it is linked, but as you can see on my screenshot, I also have the same issue as mentioned here But it seems to be a simulator related issues since it happens when the game is still loading

Ok so update on my previous comment: I tried yesterday the A350-900 on FS2024, fresh install + Navigraph data, short flight from LFPO to LFMN, without any issues at all. I thought everything was fixed, so i took the A350-900 again for the CTP today (LFPG - KIAD). Loaded the plane at gate, did everything from cold & dark to pushback & start, no issues, then all of the sudden I had another CTD (WTF.dll, logs below). The crash seems so random, because it happens to me 3 times: one just after departure (before 5000ft), another one at cruise FL380 after 1h25, and the last today just after engine start. So i reloaded the sim, changed from Navigraph data to default data + LIDO charts, and was able to do the whole flight from gate to gate without any crash or issue. I will try do do more flights with the default navdata, but with the crashes happening at random times (and not on all flights), it is hard to tell if navdata is the real culprit here. Anyways I hope you can find the issues of this crash and i wish you good luck 🍀 Crash report: Faulting application name: FlightSimulator2024.exe, version: 1.3.25.0, time stamp: 0x00000000 Faulting module name: WTF.dll, version: 0.0.0.0, time stamp: 0x6749d236 Exception code: 0x80000003 Fault offset: 0x00000000000023cb Faulting process id: 0x278 Faulting application start time: 0x1DBB698482B181C Faulting application path: S:\SteamLibrary\steamapps\common\Limitless\FlightSimulator2024.exe Faulting module path: S:\SteamLibrary\steamapps\common\Limitless\WTF.dll Report Id: 6822441c-a845-4638-b255-321926f01977 Faulting package full name: Faulting package-relative application ID:

Happens when loading the A350 at gate, I did a full reinstall with WASM folder deletion but i still have the problem It is not a full crash because i am still able to fly the aircraft, but maybe it causes instability and crashes like reported here Aircraft: A350-900 or -1000 Simulator: FS2024 SU1 Navdata Method: NAVIGRAPH OFP: None WASM Error: WASM: Varget of NONE in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm failed with error 0x00000004 Specs: CPU: Intel 14900k, GPU: Nvidia RTX 4080 Super, RAM: 64GB DDR5 Autosave File: None (they were created after)

Hello, I just had a crash with the A350 when trying to load it into KEWR. Steps: I just did a fresh reinstall (remove A350 from iniManager, cleared WASM folder, but kept all liveries), reinstalled the A350, rebooted PC and started MSFS 2024 via Steam. I then loaded the A350-900 into LFPG, no issues, switched to default nav data + LIDO charts instead of Navigraph. I don't know why, I thought that when removing WASM folder, I had to redo throttle calibrations, but this time it was already done. Then i went back to the main menu, planed a flight from KEWR to LFPO in simbrief, selected a new livery, choose a gate at KEWR, and then just after i clicked the button to start the flight, the sim CTD with the below error: Faulting application name: FlightSimulator2024.exe, version: 1.3.25.0, time stamp: 0x00000000 Faulting module name: WTF.dll, version: 0.0.0.0, time stamp: 0x6749d236 Exception code: 0x80000003 Fault offset: 0x00000000000023cb Faulting process id: 0x6F20 Faulting application start time: 0x1DBB5BF5699E584 Faulting application path: S:\SteamLibrary\steamapps\common\Limitless\FlightSimulator2024.exe Faulting module path: S:\SteamLibrary\steamapps\common\Limitless\WTF.dll Report Id: 120e8a2a-250a-44e2-b9e3-e8afb8dc2b33 Faulting package full name: Faulting package-relative application ID: So i am not sure if navdata is the problem here. I also had this error yesterday when trying to do GCLA - EFKH in the a350-900, CTD with WTF.dll after 1h when I was cruising at FL380: Faulting application name: FlightSimulator2024.exe, version: 1.3.25.0, time stamp: 0x00000000 Faulting module name: WTF.dll, version: 0.0.0.0, time stamp: 0x6749d236 Exception code: 0x80000003 Fault offset: 0x00000000000023cb Faulting process id: 0x6D60 Faulting application start time: 0x1DBB5141726C74F Faulting application path: S:\SteamLibrary\steamapps\common\Limitless\FlightSimulator2024.exe Faulting module path: S:\SteamLibrary\steamapps\common\Limitless\WTF.dll Report Id: b6679f12-9316-431b-a788-f55d867a6b59 Faulting package full name: Faulting package-relative application ID:

Hello @richboy2307, I just tried again to enter multiple holds and I had no issues at all this time 🥳 I tried it on this route: LFPG/08L N0485F410 ERIX6h ERIXU DCT ETAMO DCT GUERE DCT NARAK NARA8N LFBO/32L on GUERE, then ETAMO and ERIXU, changing the time / dist, editing the holds multiple times without any issue / WASM crash / Flightplan deletion. I think you can close this topic, thank you and have a nice day !

Ok so i tried again today with 1.0.5 (after WASM folder was deleted before update) and still had the issue, despite the changelog mentionning "Fixed – WASM Crash EFIS_Gauge_Draw when loading ANF in NAV mode after IRS alignment on both ND at same time" It is fixed (in my case) ONLY if i load a map after another: - Using miniEFIS with both control assignment and loading ANF on both ND at same time => Crash ❌ - Using miniEFIS in Capt only control assignment, loading first the captain ANF and then the FO ANF => Ok ✅ (and after that i can use both control assignment at same time without issue) Hope this crash can be fixed in a future update, thank you

I tried again today after updating the navdata on the tablet and it crashed again with the same error code (WASM: Exception c0000005 in gauge EFIS in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900/panel/inibuilds-A350.wasm)

Aircraft: A350-900 v1.0.4 Simulator: FS2020 Navdata Method: NAVIGRAPH OFP: Not related to route (but I can provide it if needed, it was departing runway 14R, FISTO7A SID) WASM Error: WASM: Exception c0000005 in gauge EFIS in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900/panel/inibuilds-A350.wasm Specs: CPU: Intel 14900k, GPU: Nvidia RTX 4080 Super, RAM: 64GB DDR5 Description of the problem: Had a WASM crash on the ground at LFBO when trying to display the airport map Video of the crash: Crash is at 14:56 and I show the console at 15:50, but i uploaded the whole flight preparation maybe there are some other steps before leading to the crash (like the ALT blue mode flicker idk)

Hello, thank you for the update and the testing on your side ! To be honest since this WASM crash i have been afraid to enter holds in my flightplan 😅 I will try again this week and will let you know asap !

It happens to me sometimes as well (but since v1.0.0), for me it's because it opens the keyboard on the screen, you wil have to close it to restore camera view / controls. It would be nice if it could be disabled via the options Edit: you can find solutions in this thread:

Hello, as said in the title, when switching from NAV to HDG mode, the level-off indicator no longer works and is stuck below the aircraft icon on the ND. Before in NAV mode: After in HDG mode: I recorded the flight so i can send you a video if needed. Some information: Aircraft: A350-900 (v1.0.3 but had the problem since v1.0.0, cleared WASM folder before update) Simulator: FS2020 Navdata Method: NAVIGRAPH Thank you in advance and hava a nice day

I had a WASM crash when trying to insert holds into my flightplan. Steps to reproduce: Everything is on video, but to summarize: - Inserting a HOLD at REQIN - Trying to change hold config (turn, leg defining parameter) - Hold was not displayed on the ND, so i tried to enter an other HOLD at BOURI (waypoint before REQIN, without removing the HOLD at REQIN) - Trying to modify the HOLD at BOURI - Inserted HOLD into flihgtplan, flightplan diapered and the WASM crash occured I have it it on video, watch it to reproduce (first hold at 1:53, second at 3:31, no flightplan & crash at 3:50, after that i tried to resolve crash without success, showing console at 8:33) Aircraft: A350-900 Simulator: FS2020 Navdata Method: NAVIGRAPH OFP: I don't have it anymore but the route was SBGL/10 DCT TISVA UL206 KODOS DCT SEROD DCT TURUP UA302 ANITI UR975 ARDAR UA854 BRENA UA29 TRB UM986 ALR UG26 REQIN DCT ELSAG DCT ALG DCT TINTO L5 VALMA DCT LIRF/16L WASM Error: WASM: Exception c0000005 in gauge MFD in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900/panel/inibuilds-A350.wasm (i think, i didn't filter the console, but it is visible on the video) Specs: CPU: Intel 14900k, GPU: Nvidia RTX 4080 Super, RAM: 64GB DDR5

Aircraft: A350-900 Simulator: FS2020 Navdata Method: NAVIGRAPH OFP: Not related to route (but I can provide it if needed) WASM Error: WASM: Exception c000001d in gauge MFD in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900/panel/inibuilds-A350.wasm Specs: CPU: Intel 14900k, GPU: Nvidia RTX 4080 Super, RAM: 64GB DDR5 Description of the problem: I was doing a flight on Vatsim, everything went well, then I tried to display traffic on ND to adjust my speed for sequencing on unicom. I was seeing the traffic in front of me because he was just below, then i switched to nav mode to see the traffic behind me. He was higher so I pressed the "ABV" button on the TCAS section. Then when i pressed back the "ABV" button, a WASM crash occurred. Luckily I was recording the whole flight, so here is a video starting 2 minutes before the crash, with the crash occurring at 01:42 (i think) (i can provide a longer video if needed): Steps to reproduce (i think): - Have a traffic in front of you on the ND on ARC mode(without the need to press "ABV" or "BLW" buttons on the TCAS) - Have the traffic visible on the SURV tab - Have a traffic behind you (not visible in ARC mode & without "ABV" or "BLW" pressed) - Switch to NAV mode on the ND - Display the traffic with "ABV" or "BLW" - Click on it via the SURV tab - Press "ABV" or "BLW" again - Crash should occur (i think) I hope it will help you to fix this crash, thank you in advance for the support !

Hi, Same issue on my side, it is the third time i think since last week, reinstalled and it is still stuck on loading screen

Hi, Just to let you know that the problem was fixed on my side with the last update, thx ! I did a flight from Dublin to Boston without any issues, will see if the problem is fixed on other flights