fwas is the author, airports 5B2 (which he interestingly called K5B2) and KGFL, both in upstate NY. The way to tell that this is an issue, at the root level of the scenery package, you’ll find two files,
AirportServices\<airporticao>\Services.xml and LivingWorld_Config\<airporticao>_LWcfg.xml
Easiest thing to do is remove the two files from the layout.json and see what effect it has on your installation.
I’m assuming the way it’s supposed to work is those files should only effect the airport they are associated with. I hope that’s what they’re spec is. Unfortunately, they seem to affect the whole installation. I don’t know how to confirm exactly what’s going on, but my experience dictates that the last read files effects at least those airports that have services and living world config files in them. I didn’t study it in detail, but, it fixed my airport when I removed the files from those airports I had of his.
But, for instance, I have them in my airports KASH, and 69NH and soon to come KCON. He cranked up the traffic so I’d have a couple hundred vehicles running around my airport. I turn them nearly off as at both of these airports, I think KASH probably has 5 fuel trucks and a couple of operations vehicles and 1 or two pushbacks at most (you rarely ever see them, only when the big boys show up). So, my airports might negatively affect other installations as well in that regard.
Hopefully Asobo eventually addresses the issue and the files only affect the airport they are associated with, soon.
Funny thing is, 3 versions ago, they introduced a bug where some Livingworld config files caused a CTD if you spawned at an airport other than the airport with the config file. I had two airports with nearly identical files, and one caused this CTD, and the other didn’t. The difference was, one was a replacement for an existing airport, and the other was a new airport that wasn’t in the game (it was torn down in 2005). That bug was fixed in the November update.