Yes. My deleted content was only the MSFS/Xbox Aviator’s Club liveries and KLAX, KSEZ & TNCM airports. It redownloaded those.
I’ve had to delete the three airports to ensure no conflict with my 3rd party versions.
Although theATR livery package is pretty big.
Yes I am in beta. I have both inibuilds JFK and FSDG KORD. And they are not marketplace version.
Now I could normally load my flight in these two airports without CTD.
If they are NOT from the marketplace,you are not impacted. Only certain 3rd party Marketplace items have this loading time issue.
1 Like
Loading time and for some of us…CTDs.
I’ve been in all the BETAs and a couple of them have had real showstopper problems like this. Those got fixed very quickly though. I’m actually a little surprised some kind of patch for this has not been released. One of the forum moderators asked for some additional information last week – almost 10 days after the release – but the request gave me the sense they had only just started to really investigate this.
2 Likes
I kinda of assume most of their French staff are still on vacation (which seems like a terrible time to release a beta, but… 
)
Well Said.
Although I know that Beta stands for „Better expect torture and anger“, I am a little bit shocked that the sim is not usable for me any more due to the CTDs. Okay, I could go back to the stable build.
But what really scares me is that they carry the bug over to the final build, as has happened before.
Really hoping for a fix.
Today I tried several possible solutions, such as deleting FlyTampa KLAS and inibuild KJFK, to no avail.
Try removing ALL the Marketplace purchased airports and see if it works. Easy with the addon linker. Otherwise, just move them to another directory.
If that works you can add them back slowly until you find the culprit(s).
In my case it was FSDreamTeam Chicago and Louisville.
Yeah, thanks, I know.
But given that I have 90 MP addons by third parties in the Onestore folder and regarding loading times currently 30 mins+ this is an endless endeavor. Even if I re-add them in groups.
After removing the CE Europe World Update, I can at least start the sim in safe mode.
Since the problem obviously lies in addons sold via marketplace and the problem started with the beta, I would say there should be some interest for Asobo to get things going. And I am still confident they will fix it.
Thank you for your analysis. I didn’t think this was my issue but it was.
So for me… having Marketplace version of FS Dream Team KORD installed causes me CTDs at seemingly random airports, however, I can replicate the CTD consistently at the Latin vfr KSAN that I purchased from simmarket using the marketplace Carenado PC-12. As soon as I remove KORD, no CTDs.
What’s worse is I get no events in Event Manager. A quick death I suppose?
Agreed, it is really strange. Never suspected that an airport add-on could cause a CTD when not being used. Tomorrow, I’m going to purchase KORD directly from FSDreamTeam just to see if I have the same problem.
1 Like
So given my 2 hour load times, I decided to try one again and this time I ran Process Manager which shows a live scan of every file being accessed by Flightsimulator.exe. What I found is an endless loop of accessing
E:\WpSystem\S-1-5-21-1092819900-1705126784-3710444166-1001\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MSFSReport-Crash.txt
and OpenRegKey
HKLM\Software\Microsoft\Windows\CurrentVersion\Appx\PackageSidRefMicrosoft.FlightSimulator_8wekyb3d8bbwe NAME NOT FOUND
These lines don’t appear in 1.33.8,
Does anyone have any thoughts on this?
3 Likes
I am away on a short trip, but have been following this topic. I am on the new beta, own FS Dreamteams KSDF , not KDSF, Louisville, and purchased it from the Marketplace. I have not been having any of the issues being reported here regarding extra long load times or Ctd’s. I hope I don’t have them when I get home. I do not own KORD, if that is any help. Not trying to make this problem solving task any more difficult, but thought my info regarding KSDF should be reported here.
Seems like some kind of telemetry things that:
- is on in SU13 beta and off in stable release; or
- this is caused by a lot of errors during loading “problematic” packages in SU13 beta
This might slow down the whole process of loading.
May I ask you:
- what is inside the crash txt file you mentioned? What is it’s size?
- what kind of disk do you use (HDD, sata SSD, N ME SSD)?
Anyway, your finding may be helpful for asobo, if the even read these comments. 
2 Likes
Well the MSFSReport-Crash.txt is 48 KB it appears to be rewritten with each occurance of the error rather than each error being added to the same log. And the file didnt contain any error messages or reference to the missing regestry key from what I could interpret. But what I Iater found is even more interesting.
I still get those errors in Safe Mode! And the Sim starts up within just a few minutes and after its loaded to the main menu those error are still continuing! So they dont seem to have anything to do with sim taking 2 hours plus to load.
I watched each file load for over an hour and there was no other errors or pauses on a perticular file in the procees. Its just slow at doing it.
I have my content loaded on an external Cruicial x8 4TB SSD over a 3.2 USB connection with about 2 TB of free space.
1 Like
OK, thanks for your findings. I believe that your extreme slow loading times might be caused by the fact you have it on EXTERNAL USB drive instead of internal one. It might be cause by some system overhead compared to the internal drives (SATA or NVME). Please remind me, what was your sim loading times before SU13 beta?
As mentioned couple of days ago, I have my MSFS content on separate SATA SSD drive (so not so fast as NVME drive is) and with 750GB and consists of 665 packages (982 items) it took about 15 minutes to load the sim from the desktop to the sim home screen. With pre-beta build it usually takes about 3 minutes with exactly same content.
Are you able to try with internal drive (even sata or nvme) or no option for you?
Before the Beta, it was taking 17-20 mins. 1.5 TB of data out of ~1300 packages.
I once ran the sim from a dedicated internal 1 TB drive, but I filled it up. So I use a external 4 TB drive
Oh wow, that sounds crazy. I didnt go into the beta as i was afraid of these loading times peoples talked about, but when i read things like that, it starts to make sense.
I will jump into the beta right now and i will compare the times and report my experience here. Hope it wont take like 15mins then…
17-20 mins is still lot of time for normal sim loading, so I suspect your not so fast USB drive (in comparison with internal sata or nvme drive) from significantly increase you sim loading times.
What is obvious is the influence of curreny SU13 beta. Where I have 3 vs 15 minutes (with exactly the same content), you have 20 vs 120 minutes. So still roughly 5 to 6 time longer loading than with pre-beta build. There is definitely something really changed within SU13 build code related to sim components / add-on packages loading or checking. Something that isould be general systematic modification. That’s my very own opinion.
Yeah I accept the slow SSD theory. It’s a 10Gbps drive so I thought it would be enough. Or Maybe 10Gbps is enough, but the drive itself is under performing.