C. Schaffhausen

Similar issue here, haven't tested 1.1.1 but it does happen for me in 1.1.0. Will avoid flying eastbound from Japan for now. Funny thing, I had a similar path, and the WASM crash occurs when crossing around 164E from west to east for both of my flights.

Update: I've just had a wasm crash too with in-sim navdata, same issue. Happens when the aircraft is step climbing and when ALT CRZ engages. Autosave: 1752099963.bin

As titled. No input at the time of screenshot. Aircraft: A350-900 Simulator: FS2020 1.39.5.0 Navdata Method: In-sim OFP: N/A WASM Error: N/A Specs: 9800X3D, RTX 3070 8G, 64G RAM Autosave File: N/A

I've switched to in-sim navdata and I can fly for longer periods without WASM crash.

WASM crash in latest 1.1.0, screens all frozen but the sim kept running. Aircraft: A350-900 Simulator: FS2020 1.39.5.0 Navdata Method: Navigraph OFP: RJTT/16L ROVER2B INUBO Y808 NOLAX Y812 ADNAP DCT KALNA DCT 44N164E 46N171E 49N176E DCT EYWAK DCT CURVS DCT CHUUK R341 ODK DCT 58N150W 58N140W 58N130W DCT IKPAM DCT KAVDA DCT MEETO DCT DUKPO DCT IKLUG DCT 48N095W DCT KP15G DCT TVC DCT JHW J70 LVZ LENDY8 KJFK/22R WASM Error: WASM: Exception c000001d in gauge EFIS in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-1000/panel/inibuilds-A350.wasm Specs: 9800X3D, RTX 3070 8G, 64G RAM Autosave File: 1751312369.bin

Found the issue, I had connection problem with MSFS and I changed my DNS server to make the sim work again. Once I did that the FPLN data import works again.

I encountered a problem which I consistently get a sim freeze every time I import and load a simbrief FPLN. I've cleared WASM folder and tried different plans, long-haul and short-haul. All resulted in a sim freeze which I have to close forcefully. The issue was not present on 22 Jun 2025. Aircraft: A350-900 Simulator: FS2020 Stable Release Navdata Method: Navigraph OFP: Not related WASM Error: Unsure Specs: 9800X3D, RTX 3070 8G, 64G RAM Autosave File: N/A

Thank you Eddie, can you please take a look at this too? I had a video attached in the latest reply. https://forum.inibuilds.com/topic/30682-spoiler-seem-opened-while-mid-flight/#comment-73136

Agreed, bug 2 was reported since initial release, it's been a dozen versions and still not fixed.

When changing the altimeter unit between hPa and mmHg, the ISIS unit remains unchanged. The only way for ISIS to follow the altimeter unit selected is to sync all 3 altimeters in options. Aircraft: A350-900 / -1000 Version: 1.0.12 Simulator: FS2020 Navdata Method: NAVIGRAPH OFP: Not related WASM Error: Not related Specs: 9800X3D, RTX 3070 8G, 64G RAM Autosave File: Not related

Happys for sure in the A35K, saw the same behavior with the A35K boarding at LFPG

Yes, not really sure if there are any changes to the gsx profile for the 350, but now it's like this. I had no GSX program updates for the past two weeks

As titled. Aircraft: A350-900 Version: 1.0.10 Simulator: FS2020 Navdata Method: NAVIGRAPH OFP: Not related WASM Error: Not related Specs: 9800X3D, RTX 3070 8G, 64G RAM Autosave File: Not related

I haven't got a chance to record some reference, but I finally did, here is how it sounds like.

Some say a picture says a thousand words.................... happens when I board with GSX

The reverser on 1.0.10 sounded very strange in FS2020, a bit loud and sounds like wind howling in a cave; it sounds a bit more normal when the aircraft is stationary but when you land and engage the reverser it sounded out of place. Any chance for some tweaks?

Seems resolved in 1.0.9 and 1.0.10

Agreed, not fixed

@Eddie Not fixed in 1.0.10, please fix 💪

Fixed in 1.0.10

Confirmed

As titled, EGT exceeds 300 degrees for both engine, none started. Aircraft: A350-900 Simulator: FS2020 Navdata Method: In-Sim OFP: Not related WASM Error: N/A Specs: 9800X3D, RTX 3070 8G, 64G RAM

I was quite hopeful that I could complete my flight from VHHH-EGLL, no AP disconnect and LNAV worked. Until I inserted the STAR of EGLL. Apart from this, I also had high EGT with ENG1 at 300+degrees before starting, and the speedbrake working in the opposite sense when on AP. Quite disappointed, 10 versions in and still many basic issues. The new features are great, but only when the bugs are fixed. I'd rather roll back to 1.0.8. Aircraft: A350-1000 Simulator: FS2020 Navdata Method: In-Sim OFP: Not related WASM Error: WASM: Exception c0000005 in gauge MFD in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-1000/panel/inibuilds-a350.wasm Specs: 9800X3D, RTX 3070 8G, 64G RAM Autosave File: Attached, saved at 21:53 1746971587.bin

Good to hear sir! 🫡

Hello @Eddie, any news regarding this AP behaviour? I've had this issue twice on my flight from KSAN to EGLL, we really need a workaround to make sure our long-haul AP to be functioning reliably. Prevent AP disconnection - ON Navdata - Sim default WASM folder - cleared before flight