It would be a great shame if you and other people like you pull out of creating super scenery. Asbo have got to sort this out. I thank you and all the others for all your efforts in making this sim as real as possible.
It’s a pure world update 4 problem for all the people who’ve reported it to me. And all of the relevant folders already had unique names for my efforts.
I seem to have cured most of them by building a new project with the new developer kit and transferring the info across, but that doesn’t explain why certain ones don’t need that.
Since GOTF I started to get this problem too (perhaps because I started to buy airports in the recent month)
What I find interesting is the following:
I select and airport on the world map … and start the flight
sim loads the world
CTD
I load the sim … try it again … CTD again … OK, as this seems reproducible
I load the sim again … and then pick some tiny airport near to the “crashy” one
sim loads fine
then I fly to the “crashy” airport
… and everything is fine … no problem what so ever
It is the last part that I find interesting … as it means that the 3D model of the airport does work in the sim without problems … unless it is the initial load.
Anybody else seeing such behavior?
Side note: My “airport CTDs” do not seem to be restricted to add-on airports. I had this with the commercial FlyTampa Sydney Intl. (YSSY) … but also with a totally autogenerated airport in the middle of Venezuela
Hmm … seems like my crashes are less reproducible then I expected.
I retried two “CTD airports” in Zimbabwe … FVTL … FVTS
Sometimes they CTD … sometime they do not.
Since there are no commercial or free add-on in that region those CTD events can not be due to wrong 3D data.
Now I do run on DX12beta … and the “random” nature of the CTDs feels like there is some race condition during the initial asset loading phase which might be the cause.
If things get loaded … then there are no problems at all.
Dear developers! What about the UUEE(Moscow, Sheremetievo) Airport from Drzewiecki Design ? . I have wrote about this problem a long time ago and no changes have made, since that time! It still have problems with very low FPS and CTD cousing. Can’t taxi and fly normaly like I 'm doing in all other airports without any problems! The Drzewiecki Design developers on forum told me that it’s not their problem, but problem of MFS 2020, which they can’t fix! Please, check it out and try to fix it! Very good airport - I think, on of the best in realism, but this problem don’t give a chance to fly normaly! Thanks!
I have just seen this “CTD” in a slightly different context (and aircraft) … which for me actually is typically more like a “GPU driver” crash.
Since SU10 we seem to get a “nicer” crash alert. For me it looks like this:
Now this case of a crash caused me to think about what crash we are seeing … and I suspect that there is:
a race condition in MSFS loading 3D assets
where some are referencing assets (textures, 3D objects, shaders?) which have not been uploaded yet
What makes me confident in this is that with aircraft, there is the “My Hangar” test (which does not exist for airports). In the “My Hanger” case the MSFS loads a simplified version of the aircraft … where on the 3D object is loaded … no glascockpit code or flight physics etc. …
The crashing aircraft worked perfectly in “My Hangar” … but I could not load it into the flight … because a custom livery seems to have been loaded “too early” … as the base aircraft was (most likely) still stuck in a WASM flight physics compile phase (or whatever is going on there)
That aircraft craft is 100% reproducible
… but “good” airports also come with custom “physics” (like rotating radars, flags in the wind, driving cars, etc.)
… and just to clarify my previous post … I only see those CTD events when I use DX12beta … with DX11 this type of crash does not happen (but there are sadly other more severe issues which make DX11 basically unusable for me)
I just had a sequence of crashes when trying to fly from FQCB …
I tried a regular start … CTD … restart
I disabled the Rolling Cache … still CTD … restart
I switched from “live weather” … now it worked
Same aircraft, some community content, same airport, same gate … same PC … in this case I only disable fetching weather data.
I still suspect that at its core this is a race condition when loading 3D assets into the GPU. But perhaps … just perhaps … live weather plays a key role in this chain of CTD events.