Looks like if KSDF is at the bottom of my Content.xml it is stable. Deleting it and letting the sim re-create it puts it higher up and seems to cause issues.
That finally clears up the issue, and confirm the scenery is fine.
Being "at the bottom" of the Content.XML, means the scenery gets an HIGHER priority, compared to what's below itself. It's like the FSX Scenery Library, but in reverse, the things down in the file are loaded last, getting an higher priority over the rest.
This also means, if KSDF "crashes" when it's NOT at the bottom of the file, it means SOMETHING ELSE is getting an higher priority instead, and THAT one is the thing that is really causing the crash, because when FSDT KSDF is at the bottom, it's EXCLUDING things from other sceneries that got a lower priority ( = higher in the .XML ) so, if any of these things caused the crash, KSDF manage to exclude them.
It can be anything, a mesh, static airplanes, it's difficult to say without knowing exactly what else you have in the Community folder but surely, if you can fix the crash by giving KSDF the highest priority, it's certainly proves KSDF is not the cause of the crash, but something else which can only be Excluded by KSDF if it's lower in the XML file.
Note that, in SU9 there still an old bug that hasn't fixed yet, which relates precisely with Exclusions, which I reported myself on MS Developers forum in January:
https://devsupport.flightsimulator.com/questions/5082/possible-bug-with-deletealljetways.htmlAs you can see Sylvain ( FlyingRacoon ) is one of the Asobo devlopers, CONFIRMED THE BUG, and later on, he confirmed is still not fixed in SU9, but it's likely planned to be fixed in SU10.
This bug would appear only if there are multiple add-ons Deleting things at the same airports. Usually, it results in missing jetways, but since it's a confirmed bug, it's possible it might have other side effect in some situations, like crashes.
