I have finally found a workaround to the crash’s after loading in, and I’ve testet it multiple times and it works every time. After loading in the flight, wait between 1-2 minutes before pressing the ready to fly button. Would anyone else try this and see if it works? I’ve not had a single crash when trying this 3 times in a row. Pressing the ready to fly button right after the plane has loaded in makes the sim crash still.
I moved a lot of them without any problems.
Note:
Reno aircraft purchases will appear in the Asobo section.
Example: asobo–aircraft–t6–eros
Famous Fliers and Local Legends will appear in the Microsoft section.
Example: microsoft–aircraft–an225
If you want to remove them from the add-ons for testing, you’re going to need to scan those sections of the directory for any purchased aircraft, and supplied liveries related to the aircraft, and move them, too.
It is scaring me, too. Since I have two PCs, I have the current release on one and the beta on the other. The current release is so significantly better performing than the beta that the difference is actually frightening. The performance issues of the beta are, seemingly everywhere — sim launch load times, flight load times, logbook load times, hangar aircraft model load times, World Map airport target pop-up menu load times.
None of those load time issues are subtle. Stripping the sim down to its base does improve the performance, but even then it still shows these tendencies.
I cannot understand (based on the release notes) what was changed here to cause all this. That might be the most disturbing part about it.
3 Likes
Have a similar feeling. Something important related to these issues is probably missing from the release notes. Maybe if we know more about these changes, we (including those of us with strong software development backgroud and experience) may help better to identify the root cause of this. Without more detailed info we are kind of “half-blind” here. I really want to help, but really don’t know how at this point.
2 Likes
I’ve done very little flying with the beta. Honestly, maybe two flights.
All of my beta experiences have been surrounding the loading issues, CTDs and trying to isolate causes.
This has resulted in a radically (and I do not use that term lightly) different beta experience from any of the previous I’ve participated in.
Like you, I’m not really sure what to do here to help. I’ve done what I can within the bounds (and sometimes out of bounds) of what I feel is fair to ask of my time.
I tried to fly the beta for the Community Fly-In Friday, yesterday, but it CTD when I was sitting on the taxiway just as the event was taking off. I didn’t bother retrying and flew on my other PC with the current release.
I have barely even tapped into how the simulation performs in the beta.
2 Likes
It almost sounds like they released a developer build with optimisation off and extra debugging on. Should be an easy fix if so, but I find it hard to believe they’ve done that several times for these SU13 betas.
2 Likes
I just tried this and no go. Interestingly, when I waited to click the Fly Now button, the sim crashed without me even clicking it. Took about 20 second but then a CTD.
1 Like
I was thinking about the same - released with some debugging stuff turned on…
Plus these “smarter” guys from the team are probably on the vacation and the rest of team don’t really know what is going on here and what to do. That’s the scenario I’m guessing.
Maybe better to postpone SU13 for a week or two we have lost already for good enough testing of other aspects of the sim.
My final thougts - if they really want to involve us to this, I can imagine better ways how to do it, especially in terms of much better communication process.
1 Like
Maybe they are trying out some new integrity check to prevemt piracy . Would explain why only marketplace content is affected.
But their approach is just not working well with all addons (yet) and so it fails / loops…
Just another blind guess.
I did notice something today when I tested delaying the click on the Fly Now button…which did not work.
When I re-enabled the Marketplace FSDreamTeam Chicago and Louisville addons, I got a message saying something like “VDGS already running, shutting down”.
Many airports can use VDGS if you have Nool Aerosystems or Aerosoft VDGS installed as an addon. Which I do. I think GSX Pro also from FSDreamTeam has a native VDGS feature. I don’t have GSX Pro enabled.
I wonder if these airports include some kind of embedded VDGS solution which is causing a conflict. Seems unlikely to be the cause of the CTD, but did think it was odd that I got the message when they were enabled and don’t get it with them disabled.
I experience a significantly longer load time for the logbook, too.
Would be great if one of the forum moderators could share an update on this problem.
Do they need more information from us? Have they been able to reproduce it on their end? Anything would be great. I’ve easily invested 10+ hours in this problem (as have many others) and it would be helpful to know it has led to progress being made on a resolution.
Thanks in advance.
6 Likes
Maybe community managers should instead? I’m not sure if regular forum moderators have access to such information.
4 Likes
That is what I meant. Yet, at this point, I’d welcome an update from anyone who might be able to give one. 
5 Likes
Yes, the speechlessness makes me speechless. 
I hope Chewwy will change this in the long run.
Things did not get any better on my side. Zero flight time. I do not have to click “Ready to fly” any more. Just waiting creates a CTD.
I’m “on the same wave”, really looking forward for any actual info. I believe that many of us will really appreciate any update on these unplesant issues in order to “unlock our motivation” for further more efficient and potentially usefull beta testing… 
1 Like
I’m finding this load time thing really perplexing.
I’ve only got 5 Marketplace add-ons installed (aside from WUs, CUs, Top Gun & Red Bull), all of which are aircraft:
- ATR
- F6F
- DC-6
- 737-700
- 631
Nothing in Community folder.
Sim load time: 4:55
No add-ons (other than those WUs, etc. mentioned above): 2:16
I feel like this issues morphs and changes and isn’t consistent. I didn’t identify any of these as particularly hard on my loading times individually. However, combined they really affect it.
That makes this even harder to narrow down or understand.
1 Like
Maybe some of these aircraft come with large liveries? PDMG?
Last night, I accidentally started a flight from runway 4R (I usually start cold and dark from the gate) at IniBuilds KJFK with the Fenix A320 and got a CTD. Tried again, CTD!!
This is the aircraft and airport combination I used at the start of my testing to identify the marketplace addons that were causing problems on my system – FSDT KORD & KSDF. Once I found and removed those, my system has been pretty good with different planes and airports and I have mostly avoided the CTDs.
During my initial testing I was starting the aircraft cold and dark from the gate–which still works. However, any attempt to start the aircraft, running, from 4R, 22R, etc. runway causes a CTD even with KORD and KSDF removed.
If I remove all the other MP addons, I can start from the runway!!! I’m not sure I have the energy to go through and eliminate the other problematic MP add-on but it is interesting that the start location/aircraft state seems to drive different conflicts.
4 Likes
Looking at that list of 5 aircraft, it occurs to me that they are spread out alphabetically:
The F6F has a directory starting with “F”.
The ATR and 631 have directories starting with “M”.
The DC-6 and 737 have directories starting with “P”
That means that when I was doing all the testing via “take half your add-ons, then half of that half, etc.” these aircraft wouldn’t have ever been in an add-on group together due to their directory spellings. When I go back and look at my entire MP purchases together and then divide that at an even point down the list. The PMDG aircraft aren’t in the first half.
I couldn’t have easily stumbled upon this combination without doing what I’ve done — just randomly happening to put them together.
Taking what you’ve said and looking at that list of aircraft, the ATR has its liveries separated out as individual add-ons each with their own directory.
The PMDG aircraft have their liveries separated as a single add-on that has all of the liveries contained within that single add-on’s directory.
(I’m assuming here, that a directory at the root level of the OneStore directory is considered an “add-on” and any subdirectories within are a part of said add-on.)
If the issue here of slow loading is being influenced by liveries, then the combination of the ATR and the PMDG together, might be the cause.
EDIT:
Messing around here, I removed the F6F, ATR and 631 leaving both the PMDG 737-700 and DC-6.
Load time: 2:25
Then I reversed it – removed the 737-700 and DC-6 and added the F6F, ATR and 631
Load time: 2:24
This reinforces my statement that individually these add-ons’ impact on load time is very minimal, yet when combined they act in unpredictable ways by adding significantly to the loading time. This is not an easy issue to make sense of.
(Also, what’s up with the 1:10 we have to wait for the launcher (22 sec), Xbox, Asobo, Black Shark and copyright splash screens before the loading screens even start? I hope the sim is actually loading while that is all going on…)
EDIT2:
This is ridiculous. I recombined them all and the load time remained 2:25.
Prior to these tests, they were loading in 4:55.
I did recieve an update to fs.base and fs.base-ui-widgets earlier this AM.
Is this a fix? Are we seeing an update to the beta today?