. I also don't want to set autogen to 0 or change the AI.
I asked to do it AS TEST, to prove you the problem was not anything from FSDT. Once we knew that, you could investigate it further. Nobody said you had to *keep* your settings that way.
By doing all that everything went back yo normal again. Too bad it can cause such crashes
No, KLAX scenery doesn't cause any crash, and of course nobody ever reported it, clearly indicating the problem was something else. But since you didn't wanted to TEST that way, using the TESTING settings as I've suggested, we'll never know.
A common cause were users can be easily mislead "The airport cause a crash", when it's not, is some AI or Autogen objects that DO NOT come with the airport, and have a problem and, due to the different AI schedule comparing when the airport is installed or not, or due to the different Autogen exclusion when the airport is installed or not, can be easily mislead you the airport was a problem "because it's fixed when I uninstall it" but, even if this SEEMS reasonable, that's not what's happening.
What's really happening, instead, if the presence of the airport is triggering the appearance of some objects (AI or Autogen) that are coming from other products, which are the real cause of the crash, and they don't appear if the airport is not installed.
That's why I asked to try with AI and Autogen at the lowest settings.
So, please, don't think you have fixed the problem by uninstalling KLAX, because you haven't, and the problem will likely surface again somewhere else. KLAX doesn't crash the simulator, it's a scenery that has been working for everybody since years, and if it really crashed the simulator (it's NOT) we would have heard it by now, and obviously fixed it.