CR7

AGAIN! I had the WASM crash on v1.0.10. The WASM crashed during cruising from EGLL TO KSEA. I cleared the WASM folder before updating the A350. All crash details are on the video attached below. I'm really confused that this issue still hasn't been fixed, even after 10 updates, WHY? Simulator: MFS2020 Aircraft: A350-1000 Navdata Method: SIM DEFAULT i9-13900k RTX 3090 RAM 32GB Route: EGLL/09R CPT5J CPT L9 DIDZA N14 OKTAD DCT MEDOG DCT KRAGY DCT PEMOB DCT VATRY DCT REVNU DCT KESIX DCT SUNOT DCT 60N020W 64N030W 66N040W 67N050W 68N060W DCT CANEL DCT 68N070W 67N080W 65N090W 62N100W 60N104W 57N110W DCT YMM DCT YXC GLASR3 KSEA/16L 204372801de0542d6002e43e75f948e1.mp4

Hi there, I saw some people have this issue in 2024, but I also have it in MSFS2020! I got twice WTF.dll after taking off EGLL to KSEA. Aircraft: A350-900, A350-1000 Simulator: FS2020 Navdata Method: Navigraph i9-13900k RTX 3090 RAM 32GB

Not just the 2024! I got twice the WTF.dll crash in MSFS2020.

Sorry to hear that. 1.0.8 is broken for sure! Unfortunately, again, the A350 became unflyable before the WASM crash was solved! I also can't believe WASM crash has not been solved in 8 times of updates!

Hi there. Today, I had the first WASM crash on v1.0.8. The WASM crashed during cruising from RCTP TO KLAX. All crash details are on the video attached below. Unfortunately, the A350 became unflyable again before the WASM crash was solved! I also can't believe WASM crash has not been solved in 8 times of updates! Simulator: FS2020 Navdata Method: Navigraph i9-13900k RTX 3090 RAM 32GB Route: ROBIN1A ROBIN R583 BORDO Z29 GAKIA Y293 YULIA Y57 POROT/N0482F370 Y809 IDLAN Y812 ADNAP OTR5 KALNA DCT 42N160E 43N170E 45N180E/N0485F390 47N170W 48N160W 47N150W 44N140W 40N130W/N0476F410 DCT DACEM DCT PAINT DCT PIRAT DCT BURGL IRNMN2 0ad69f2669fec6bdb2b7fc09c6cc2d91.mp4

Thank you for your answer. Hoping for the updates.

Hi there. How can I update the ARPT MAP in the A350? The RJFF is updated to two RWYS by the developer, but it still uses the old ARPT, which is one RWY in the A350 even though I updated the latest date in OIS.

Hi, The WASM issue hasn't happened in V1.0.7 yet. I will follow those steps to report it if the issue comes up. Thank you for your follow up and hard work!😍

Hi there. This is the first WASM crashing after the update to V1.0.5. The MCP altitude, HDG, and altitude adjustment are not working after setting up the FMS. I cleared the WASM folder before updating it to V1.0.5. Aircraft: A350-900 Simulator: FS2020 Navdata Method: Navigraph i9-13900k RTX 3090 RAM 32GB 5f1fa6785b89811bf764ca42ff366eb8.mp4

Hi there, Before I prepared for descent and set the BTV, I found that the airport map was unavailable. In the settings, I discovered that the map was disconnected, and no matter what method I tried, I couldn't reconnect it. The Navigaph works fine before taking off. I have encountered this issue twice, both times after a long flight. A350 V1.0.4 FOR MSFS2020

I got the other WASM crash on the same day again!! The WASM crashes when I release the flap 3 on the final approach to KTDW by (inibuilds) 22L. I can confirm that all the WASM crashed after I cleared all the WASM files before launching the A350. It looks like the different crash type of the WASM!!!

Hello there, I had WASM crashing again. The plane is cruising, and when I move the map to select an exit for BTV, WASM crashes!!! Last time it was the A350-900, this time it's the A350-1000's turn!!

Hi there. Thank you for following up. I can confirm I did not clear my WASM folder before launching the 1.0.1 update. I will do it and run some flights for testing. However, the crashing is random. I am not sure if I can do the record when the WAM crashes. My WASM folder has more files in here than you showed. Should I delete all of them or just pick the flies that you showed?

I got the same WASM crash in V1.0 and V1.0.1 versions. The first WASM crash in V1.0 was preparing from LFBO to EDDF. I also see the almost same upon F-PLN WASM crash issues in dc.

Hi there. Do I need to update the data if I using NAVIGRAPH on the OIS?