ben4muk

I literally just cleared the WASM Folder, started the sim, downloaded the latest AIRAC and started prepping the flight. FP Attached! 1.1.6 MSFS2024 NAVIGRAPH 14900K, 4090, 64GB No AUTOSAVE as I had just wiped the WASM Folder to resolve earlier WASM crashes. Talk about bad luck! WSSSOTHH01.fpl

Did an approach this morning. Terminal 3 buildings were there and complete! Thank you!

Now this comes into the discussion... https://simpleflying.com/qantas-1st-airbus-a350-1000ulr-assembly-line-toulouse/ So, back to the original question. Will we get the A35K ULR from Inibuilds?

I had a wasm crash. Restarted the sim, and the issue came back again. I can only assume this is something that started with the latest update of the A350.

I have bad numbers showing in multiple displays.

Yes, that's the folder that needs to be deleted. Honestly, a horrible experience. I really regret buying the A340 via the Marketplace!

There's an MSFS thread for this, and I have voted for it. Maybe MSFS / Asobo can ask Inibuilds to do what we want 🙂 https://forums.flightsimulator.com/t/premium-a330/742160

I have seriously lost my patience with Inbuilds and Asobo Marketplace. Having the aircraft exclusively on the Marketplace is a horrible decision. I am not able to install the update!

100% agree!

Not buying until this is buyable from the IniBuilds Store!

I have a follow up question... Will IniBuilds be releasing a Premium A330 with improved updates?

+1

Glad I could help 😉

Is there anyway to make the devmode changes stick when we start the sim again? Right now, I need to go into dev mode and enable active lod's. Is there anyway to make these changes stick till this is fixed?

What's your Shader Cache set to in the NVidia Control Panel? I increased mine to 100GB in non VR and it sorted my stutters.

Worked like a charm! Thank you! Was growing frustrated with this.

Nothing. Not even a confirmation that this is being looked into.

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

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!

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.