No waste of time for me. Zero CTD’s since downloading FS2020 within a week after it came out.
Given the same timeframe, FSX was nothing BUT CTD’s. Some things I learned about “fiddling with things” which I include add-ones coming over from FSX are…
I download all the freeware from one source. At Flightsim.to the manager keeps track of downloads plus a HUGE advantage is it lets you know from day to day which ones need an update with one simple click. Payware gets downloaded from withi FS2020’s Marketplace. Of course the only time this would change is with a major payware aircraft purchase with something like PMDG where it’s not available anywhere’s else but on their website. The point being it’s easy enough to backtrack it for an upgrade of fix.
I have ALL my freeware sceneries, airports, etc in one folder. Inside that folder I have a sub folders I made with all the major continents. From there I made more sub folders containing all the individual states or countries. In the case of Canada I made sub folders based on each Territory or Provence. Originally I didn’t and quickly found my growing freeware library causing a massive increase in boot times within FS2020. It also saves TONS of time when all sceneries are logically grouped when you need to find a specific one for updating.
This method for me is two fold. One, why have sceneries in Spain load when I’m only flying in-state with sceneries from Florida? And secondly, if there ARE problems with a new update it’s very easy to home in on a culprit if indeed it’s a scenery by deleating the add-on sceneries within the sim and then adding back in the sim within smaller groups in order to achieve the process of elimination.
I don’t ever follow through on a download if it eventually involves changing anything anywhere in a configuration file. In my waning days years ago of using FSX it was directly related to this action. One thing effected another and next thing you know even with backup .config files it became a nightmare of sorts trying to untangle everything.
Never again in regards to messing around with .config files. Either I wait for an official update and/or learn to live with it.
And with the potential for installing corrupted or conflicting freeware files (which I had to install a new SSD just to store them all) it’s very easy now to home in on the problem file in question.
I have been trying to figure out what may be the cause of the increased CTDs.
I now have evidence that something in the update to 184.108.40.206 is the cause of most of the new CTDs. I did not have this problem before the update and have started to see alot of people talking about more CTDs after the update. I have tried everthing suggested from graphic card driver reverts or updates to an empty Community folder to setting changes on computer and in the SIM. It all comes back to this last update. I wish there was a way to go back and revert to the state before 220.127.116.11
I’ve already have round about 300h in the log book and almost all of the payware you can have, until now I haven’t had a single CTD apart from the current thing with the Bing data that caused CTDs in 3rd party addons, but that is easy to fix, turn off BingData in Trafficsettings for now.
Ok, not a waste of time to take a look at your own system. Coincidence or not, my CTD’s seem to have stopped now after I updated Win 10 with “optional” Win 10 20H2 update. I tested the sim last night and this morning to the point I’m satisfied the CTD’s have stopped. Actually, the program was not crashing to desktop, but crashing and restarting my computer to a desktop.
I think I have narrowed the CTDs for me down. Just flew one of my best flights ever in this SIM. Flew from KSTL to KATL using RexWeather Force2020, SimTool Kit Pro, Imagesim KATL,Navigraph and Pushback Helper ALL active and working on 2 Monitor. Not a single problem but the TOO Talkie Talkie ATC.
Crashes are happening with FlightBeam KIAD and Cloudsurf Asia Simulations WSSS. Something that these too have in common are causing my crashes. Happens in other places in the world but these are the two airports I purchased last.
It started since last update and after I purchased KIAD and WSSS a week apart. Its not anything else as I have done every suggestion including memory and all hardwire ideas. It is to do with the software.
The issue that seems to be causing the problems is with addon scenery that have a .CGL file in them. Nothing to do with reinstalling windows, memory or anything else. As soon as you turn off the .CGL file, the crashes stop. Apparently this file holds Bing data used at custom airports, but Asobo have changed something with how Bing maps operate which is why the crashes are happening to addon scenery. Asobo are aware and dealing with it as already acknowledged.