I've been watching the threads on ctd's and out of memory errors and wondering if I may have caused a few. I wasn't aware of the issue at the time, and have a few g2k files that I assume are "landclass" in my lighthouse sceneries. Do the landclass files need to be in sight to cause the problem? For example, in Washington State, Tatoosh Island, located off Cape Flattery is a g2k file. Could it cause an out of mem error 125 miles away at Seatac? The island uses the same MS texture as the surrounding area, located in the main texture folder. Does the fact that it uses a texture at all mean it won't cause the out of mem error? The same would be true for golf courses, etc.Is it considered bashing to post the scenery name if you find one at fault? I may have missed something, but I don't see where anyone has posted it was "Acme Aiport by John Doe". I have not received any emails on the issue either. I've left the scenery in it's original structure on my system, and have yet to get an out of memory error. If someone has found mine caused a problem, I for one would sure like to know about it. Since it sounds like it either has or could be an issue, should I upload a corrected version of the three lighthouse sceneries?Larry

Hi Larry."Do the landclass files need to be in sight to cause the problem?" No."For example, in Washington State, Tatoosh Island, located off Cape Flattery is a g2k file. Could it cause an out of mem error 125 miles away at Seatac?"Probably.Most MS scenery should be in a "scenery" folder that is paired with a twin "texture" folder. But landclass and waterclass cannot. Landclass must be in a project folder that has NO "texture" subfolder twin. The existence of one such violation of this rule in an active scenery could cause a fatal memory leak.Dick