ben4muk

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!

NICE! This fixed it for me!

Following

Hey, Got the following flightplan and on flightplan import on INIT Page, I get a WASM Crash, on 1.0.6. CYYZ VHHH DCT IMEBA DCT YVO DCT 50N077W 60N073W 65N071W 70N070W/M085F330 DCT INGUM DCT 76N060W 80N050W 82N040W 84N020W DCT RITAK/K0919F350 T572 ANODI N611 DOSON R705 OKASA/K0898F370 R705 BRT G490 SERNA/K0876S1130 Y520 POLHO/K0878S1160 G218 TMR/K0882S1130 B458 VADKA/K0882S1190 B458 DADGA/K0896S1160 W37 GUSIV/K0906S1190 W37 PEXID/K0907S1160 W37 OMBEB/K0898S1190 R473 NNX/K0909S1160 R473 WYN W18 NLG W23 ZUH R473 SIERA DCT I wiped out all of my cached WASM files. Still happens. Benny

Fixed!!! Nice work! With the A35K, after a pushback, taxiing is behaving as expected now!

I can do another test after I finish my flight and updated iniBuilds A350 and GSX. Ofcourse, I'll wipe out the WASM folder too.

What is your realism setting in MSFS2024? Mine was set to 100% realism.

2) Did you clear the warning?

Experience the same issue. I did a test (MSFS2024). I took a plane without GSX, fired her up and tried to taxi. No problem whatsoever. I then reset the flight, this time I did a GSX pushback. I got an MSFS warning of Gear Damage. When I the try to taxi, I get the problem described... No matter how slow or how much input, nosewheel turns, but the plane is always "skidding".