C. Schaffhausen

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

Thanks Eddie, much appreciated 🙏🏻

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

I have a similar issue, although not as severe as the one in the OP. Edit: I also tried it under conditions without wind, same issue. The sim is MSFS 2020 stable build (not SU16 beta).

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

Tried 1.0.11 today in FS2020, de-rotate system does not work and nosewheel hammers the ground.

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

Agreed, very dark screens in msfs 2020. Also the lower MFD (I hope I got that right) is brighter than the rest of the display.

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.

One issue on my side, when boarding the FA seems to be going............up

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

No longer an issue in 1.0.10, thank you!

Same issues as OP has, inaccurate arrival time and fuel predictions.

We are the beta team lol

Agreed, not fixed

@Eddie Not fixed in 1.0.10, please fix 💪

Fixed in 1.0.10

Confirmed