The stuttering was the result of an un-optimized fsx.cfg.
The issue is, there are some settings that, while promising to be "optimized", are very dangerous and cause crashes. The most very well known is the Poolsize=0 setting. Yes, you might see a smoother flight but, if you have too high settings, a memory hungry airplane and too much texture memory taken, it will INCREASE crashes.
This has been discussed a lot when we released KMEM: people were convinced there was something wrong with it, because some were getting lots of crashes in FSX. Of course, the scenery didn't had anything to do with this, and it was caused by having manually added the very dangerous PoolSize=0 tweak, which should only be used if you have plenty of spare memory.
with the update to the PMDG777 and 737, PMDG now has a similar issue with a .dll not allowing FSX to close properly. I bring this up because they've heard their customer reports and are investigating.
This seems to indicate the problem was never KCLT to begin with. Are you able to quit the sim when NO 3rd party modules, except our own are loaded ?
With "no 3rd party modules loaded", I mean *everything*, not just the ones you don't care for...Obviously, just AS A TEST. I'm not trying to say you must use the sim like that, but it's not possible to "investigate", if you don't remove all the extra factors.
What about FSDT? I've seen at least 4 people (probably more) post about this SimObject crash on your forum.
Fact you see a post, doesn't mean that is the cause or there's a problem with the scenery.
You are confusing the cause with the effect. If the Simobjects are not there, nothing will work, of course. But if the objects are there, they will be created, and they will take memory and, if you use the scenery together with lots of other stuff, it's possible there might be a conflict with another module
caused by that one, but just because KCLT, being a fairly large a new scenery, is big and takes quite a bit of memory.