ben4muk

Was preparing for the arrival into VHHH. Went to update the POS to the runway I was expecting, VHHH07C. 1753215956.binEGCCVHHH_PDF_1753177785.pdf

Just stopped following the route after waypoint MAKMU. WSSSKJFK_PDF_1751426712.pdf 1751451392.bin

Just landed at RKSI and started to clean up the airplane. Noticed that Flaps and Speed break were still up. 1750828919.bin KSLCRKSI_PDF_1750785707.pdf

I did read it. It was literally in the last few minutes. It's fixed.

Yup! Using the default sim data works fine. This is probably a Navigraph issue.

Hey guys, I don't know if I am the first to report this, but with the latest airac from Navigraph, the A350 is freezing. The freeze happens for me, either when installing / updating the airac, or when trying to import a flightplan from the INIT page. Are we aware of this? Is this being looked into? I can confirm, this is happening with Navigraph airac 2506 for me. Things I have done to try and remedy the situation: uninstall and reinstall of the Inibuilds A350 - no change deleted wasm of all navigraph folders - no change deleted wasm of all inibuilds a350 folders - no change Let me know if you need anything else here. Benny

Partially fixed. Still missing the building section that extend from the main corridor at Terminal 3 Gates...

Yeah, well... It looks like I spoke to soon...

A350-900 MSFS2024 Navigraph 13900K 4090 64GB RAM While vacating the runway, I was trying to clear up the airplane. Turned down the lights to Taxi, Initiated the APU. When I tried to retract flaps and speed breaks, I noticed nothing happening. LTFMKSFO_PDF_1748835431.pdf 1748890068.bin

Negative! SU2!

Same thing happened to me, usually happens within the first hour or two into a flight. I am on 1.0.11. Doesn't seem to matter how many times I wipe my WASM folder for the A350.

Or, perhaps, there might be something happening in the early stages of flight that triggers it. And then once you reload the flight after, and skip the early stages, you are "safe" from a wasm crash?

I too am suffering from WASM Crashes. It got MUCH WORSE since 1.0.11. Every flight is WASM Crashing. Is there something unique about the Time Compression? What I am doing is, WASM Crashing, then I load an Autosave, and apply the time compression, and I am able to complete the flight.

Didn't help...

I just did another flight, and no Terminal 3 Piers. Issue still persists. I checked my sceneryindexes folder and found the following file: I am deleting this file and trying again. I have no other EGLL files in my sceneryindexes folder. Hopefully this will resolve the issue. Will report back!