Hello everyone, has anybody else noticed ultra long times from when "Start flight" is pressed until either the "Ready to fly" button is available, or the walkaround mode is loaded (in case the RTF button is disabled)? I've been facing these issues mostly since Christmas. Right now I've been spending over 10 minutes trying to load the A350 at default KJFK, without success. I've tried disabling my frame rate lock, killing MSFS2024 and restarting, abort the loading (by pressing ESC), reduce TLOD/OLOD to 10 and try again, changing the aircraft, but still no success: the camera is still panning around the selected gate from way above. It's happening to me almost every flight. I've been spending the last hour trying to start a flight, unsuccessfully. Any other way to fix this?

My idea was to take off and leave my plane in cruise while I go to a medical appointment nearby, but with this MSFS behavior, I guess the flight is canceled. Frustrating 😭

PS: I had purchased the A350 during Black Friday, and flown it several times since, so it's not an unknown plane to my sim. Also, both MSFS2020 and 2024 are installed in the same dedicated SATAIII SSD.

I only get extended times to load, after pressing the "Start Flight" button, when flying complex airliners, like the PMDG 737, PMDG77 and the INI A300 Premium.    My normal load time from pressing 'Start flight' is GA aircraft is almost instant.  In the aircraft listed above, it's upto 2 minutes.   Never longer than that.

Interestingly I don't get the delay in the Fenix A320, which loads instantly.

On sporadic occassions where the flight just won't load after I hit 'Start Flight', it's always been because of an incompatible scenery addon.    EG. I download a new scenery from FS.TO, go to load a flight but it just hangs on the position where the camera is floating above the scenery, and does not load.  You can 'ESC' out when this happens.   I remove the scenery (which is usually an old MS2020 scenery) and everything loads fine again.

Edited January 7Jan 7 by JYW

2 hours ago, JYW said:

On sporadic occassions where the flight just won't load after I hit 'Start Flight', it's always been because of an incompatible scenery addon

Thanks for your reply. Would this also happen with default Gaya sceneries, such as KJFK or EGLL?

After the SU4 update I did get the opposite.
Game loading times up to the main menu have almost tripled (I need to sit through the intro video almost 3 times now) but hitting the start button for a flight is not slower than before.

12 hours ago, Luis Hernandez said:

Right now I've been spending over 10 minutes trying to load the A350 at default KJFK, without success

Initial WASM compilation especially for the ini 350 takes exessively long times here, too, I need to let it sit well beyond 10 (if not 20) min until the plane ultimately loads. however, that only happens once you load the ini 350 after an update of that plane (or even MSFS, cannot remember). Once done, every succesive loading is almost instantaneously. So if you updated the ini recently and did not let it sit reaaally long, grab a coffee or beer and then come back, then you may just be too impatient. However, if that happens on every flight/loading after it even loaded once fully then there must be another reason and all I can propose to the delete the WASM folder for the 350, restart 2024 and start again a new flight with the 350 but then wait reeeally long.

That WASM folder should be here, add your Win username for the XXX:

C:\Users\XXX\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\inibuilds-aircraft-a350

Loading the simulator itself on my PC takes the time required to get to the part of the video where the small plane picks up the banner. In other words, not very long. With respect to loading an aircraft at an airport, this takes a few seconds.....every time. This is with either the PMDG 737-800 or 777F. The only time it took longer was when these aircraft were being compiled for the first time, and even that was pretty quick.

Its all mostly server related on the back end.  The map enhancer tool really helps with this scenario.  

 

 

I think it also depends on the complexity of the aircraft. The ini A350takes the longest after a update. I think that's because I always delete the wasm folder and let it build a new one.

15 hours ago, DAD said:

Initial WASM compilation especially for the ini 350 takes exessively long times here, too, I need to let it sit well beyond 10 (if not 20) min until the plane ultimately loads. however, that only happens once you load the ini 350 after an update of that plane (or even MSFS, cannot remember). Once done, every succesive loading is almost instantaneously. So if you updated the ini recently and did not let it sit reaaally long, grab a coffee or beer and then come back, then you may just be too impatient.

6 hours ago, Bigmack said:

I think it also depends on the complexity of the aircraft. The ini A350takes the longest after a update

Maybe this explains it all. I had updated it recently and never flew it again because I was flying other planes. Thank you all for your replies!

6 hours ago, Bigmack said:

I think it also depends on the complexity of the aircraft. The ini A350takes the longest after an update. I think that's because I always delete the wasm folder and let it build a new one.

Even if you didn’t delete it, any update on a wasm plane triggers a recompilation. The deleting is for when you think your current files are messed up and want to force a recompilation even though there’s no update. 

Edited January 9Jan 9 by JonathanC

6 hours ago, Luis Hernandez said:

Maybe this explains it all.

please report back whether letting it sit for well beyond 10-15mins helped indeed

13 hours ago, DAD said:

please report back whether letting it sit for well beyond 10-15mins helped indeed

The plane finally loaded some minutes after I opened this thread. It was already too late for me to try a flight that day. But last night I decided to try another flight in the A350, and as you said, it loaded almost immediately. I'm not sure I can call this situation as solved, because it will happen again the next time I get a new or updated plane. But that's an Asobo issue I guess, not ours. I say again: thank you all for your replies!

Edited January 9Jan 9 by Luis Hernandez