Muffwin

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

Hi ! I have the same issue (currently cruising at FL340), i followed the checklists in MSFS. I also have the same issue as mentioned by pdp above.