If you have experienced the infamous hang upon world loading at 97% (so common that it has become an internet meme since MSFS24 was launched), I came across a workaround that has solved the issue for me where I am now able to load and access the sim.  Before this, I was getting these random stalls on startup where I would get the message "Loading unusually long: log saved to Report-loading.toml" with the world loading stuck at 97%. I say random, but it was happening probably 4 out of every 5 attempts.

The solution that worked for me is posted here: Stuck at 97%

The gist of it is this (reposted with h/t to RaginWombat839 on the official MSFS forums)

Quote

 

So here’s the detailed method I used to fix my stuck at 97% after 4 days:

These paths are for the MS store/Xbox Store PC version. They will be different for steam, and I’m guessing any poor Xbox users that have incompatible addons are just stuck until MS actually fix it.

1. Open directory C:\Users\[username]\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState
2. Open file in this directory Report-loading.toml (can use notepad)
3. Search for FlightSimulator_Packages (around line 89 for me)
4. Delete every line above and including this one.
5. Search for FlightSimulator_PublishingGroups.
6. Delete every line below and including this one.
7. Now you have a list of packages-names=1.
8. Search and replace to remove =1 on every line.
9. Delete all of the lines that start with asobo or microsoft, it’s alpabetical order so very easy.
10. Edit every line to add the prefix mkdir , ie. with the space.
11. Copy this line to the very top:  cd C:\Users\fly\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages\Community
12. Save the file anywhere, and make sure you add a .bat extension on the name you choose.
13. Double click.
14. That’s it, restart and play!

To be clear, the top of my 2024fail.bat file looks like this:

cd C:\Users\[username]\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages\Community

mkdir 4simmers-a310-1-livery-pack
mkdir antsairplanes-tiger-moth
mkdir blackboxsimulation-bn3-trislander
mkdir cowansim-cowansim500e
...etc...

 

What it seems you are basically doing is adding empty folders into the local "packages" Community folder on the C drive for all of your previously purchased MS2020 Marketplace content. It appears that on initialization the sim is looking for these - that's why they are logged in the "report-loading.toml" file - and if there is some issue with one or more of them (I don't know if that is an incompatibility, or just the absence of the folders, or what... I don't understand how they are handling this content in the cloud) the sim fails this startup check and never recovers.  After placing those empty folders in that directory on the C drive, I have been able to start up the sim every time within 2-3 minutes. It is odd that it needs to see the empty folders, but that is indeed what fixed the problem.

I suspected that there was something in the loading initializations with cloud-based content that was buggy, and sure enough that seems to be what afflicted me.  It also seems like the sim performance is snappier and I haven't had the CTDs on loading a flight that I had before (though that could just be placebo effect or I haven't run the sim long enough yet).

I don't know if this works for everyone having loading issues, but it solved my problems to where I can at least experience the sim now.

I don't understand why all this MSFS2020 content needed to be rushed over to load from the cloud, since I really don't want anything installed from 2020 that is not proven 100% compatible (and some of the 2020 scenery I don't want anyway, as it may be lower quality), but Asobo in their infinite wisdom haven't given us that option.

Hope this helps someone out there. Encourage you to follow the link and upvote the people who found the solution.

Edited November 26, 20241 yr by PurdueKev

I only ever bought iniBuilds EGSS on marketplace (2024 compatible) and have never had trouble with the sim after the 48 hour meltdown following release.

39 minutes ago, flyingscampi said:

I only ever bought iniBuilds EGSS on marketplace (2024 compatible) and have never had trouble with the sim after the 48 hour meltdown following release.

I don't think including all of the folders is necessary; there may be incompatibilities with just one that would that would create the loading problem. But I wasn't going to try to spend the time isolating which one. If the addon is tested to be compatible, then it wouldn't be the cause. But many of them are not yet compatible so it does not surprise me that Asobo porting them over en masse would create a bug.

I wonder if market place content purchased in 2020 is the reason why people are having totally different experiences with the sim?

I have 1 marketplace add-on from inibuilds and have no problems, yet others...

11 hours ago, flyingscampi said:

I wonder if market place content purchased in 2020 is the reason why people are having totally different experiences with the sim?

I have 1 marketplace add-on from inibuilds and have no problems, yet others...

I think it is certainly a potential cause, yes. At least there is some compelling circumstantial evidence.

I think it was a bad choice for Asobo to port over all that 2020 content so quickly without first ensuring they have been debugged and compatible. I can't imagine that all of them work flawlessly at this early stage.

Edited November 27, 20241 yr by PurdueKev

Thanks for posting this @PurdueKev

I didn't follow the procedure exactly, but I did install Ant's Airplanes Tiger Moth into the FS24 community folder which I had previously installed in FS20.

It took another three 10 minute loads before, presto, everything lined up and my loading times are now down to 3 minutes!

I haven't checked if all my marketplace planes are available yet because I'm just really glad to see an end to the long loading times.

HELLO

 

its ok for me

file with all aircrafts or only aircrafts purchased in the shop

 

cordially

I just emptied out my community folder. Obviously something in the current folder is not up to 2024 snuff. Loaded right up.

Well, for 2 days I have been working on this first, it was that I could get in the game and load up from the airport to my go-to airport I was going to but when I hit Start flight in would stop just as it was just about to spwan in the airport but was stuck after trying bunch of stuff I secided to uninstall and reinstall (Bad mistake don't do that) so then now it would only go to 97% so here we go again search the worls wide web for an answer with no clear winner then I remembed back in the FSX days to go in and delete the running back ground steam running in task manger so you "guested it" that's what I did and low in behold it work loaded right up and was able to spawn in to our FSE Aiport KFNT 

Hey, looking for help, we most likely can help you, or if you want to go flying with us 
join us on our Discord  https://discord.gg/easternhops

I have over 100 sceneries in 2024, most of them come from 2020 and all of them purchased through marketplace. Have not had this bug or even heard of it.

I’m on Steam if that makes a difference, and my Community folder is on a custom path - maybe that helps?