After reading what's in the forums on landclass files, then downloading a few files, and reading install instructions, I'm even more confused as what to do and what not to do to avoid a memory leak. Lately, after I close off FS9, I've been getting the dreaded yellow triangle/exclamation mark in the bar at the bottom saying that windows ran out of memory and adjusted itself (which would explain that long pause that occurred just as I was coming into that tricky landing w/ crosswinds 'n' all...you know...the one where I bent my prop in the dirt just ahead of the landing strip). Does this mean I've got a memory leak?With all the different advice, and filenames that all look the same because they have the same identifier, I'm more confused now than when I started to search for info on this topic. For instance...1. Some files I download from Avsim are referred to (in the description) as landclass files, yet they are bgl files. Are bgl and landclass the same thing?2. Someone in one of the forum writings said not to have a texture folder in a landclass folder. Yet the default addon scenery folder (which I take it is full of default landclass files) has its own texture folder. Should I delete that texture folder?3. Some scenery (mesh and landclass, and (have mercy) lod) files I have downloaded tell me to just put them (with bgl identifiers) into the addon scenery folder. Is this the wrong thing to do? With every bgl file I download, should I make a separate scenery folder? And then make sure there's no texture folder in that scenery folder? Good grief!It's getting to be so that I'm not sure of what to do and what not to do. My head is spinning so many different directions I think I'm possessed. Can someone please explain this a little clearer for me?

1. BGL is just the format/extension FS uses. Those files can be landclass or mesh.2. The default landclass is stored in the Scenerybasescenery folder which doesn't have a texture folder3. Landclass files should not have a texture folder. 99% of the scenery developers know this by now and should know if their scenery will trigger the memory leak. So their instructions should be correct in almost all cases.It's easy to check, just hit ctrl+alt+del before starting FS it will log memoery usage (there are other ways to do this as well). It should stabilize somewhere around 500-700MB when flying, depending on AI and scenery complexity. If you suffer from the memory leak it will slowly but steadily creep upwards until the paging file is filled and FS likely crashes.

I wrote one of the handful of landclass creation tools, Landclass Assistant.For installing Landclass, you can have as many bgl's as you want in a central folder, although the bgl's shouldn't be landclass areas that overlap.I don't like placing add-on bgl's in MSFS's default folders, so I place all my add-on Landclass creation in a folder which is simply called "Addon Landclass". My scenery.cfg has an entry for this folder. I created just one folder inside--"scenery", which is where all the bgl's get placed.When I add new landclass, I add the bgl to inside the folder's scenery folder, and can start MSFS as usual.You raise a valid point--there's some "Landclass" circulating out there that's actually mesh (3-d terrain) and some "Mesh" circulating out there that's actually landclass (ground cover). Read the file description closely before downloading. If someone says something like "38M Landclass adds hills to South Dakota", likely they're actually talking about mesh. And if someone says "This mesh will add autogen buildings around Winnemucca", likely the file is actually landclass. Regards,John

Thanx John and Jimmi. Helped a lot. Appreciate it.

I think this is a case where a little information can be dangerous.If you are having problems, the first step would be to try to remove the last scenery added, and see if the problem resolves itself. If it does, then, depending on your interest, you could attempt to troubleshoot what went wrong with the new scenery.Without using scenery design tools, I don't think there is any way of determining if a given file specifies "landclass" unless the scenery author tells you in a readme. I also think that at this point, the vast majority of authors understand the "memory leak" issue with FS9 , and provide installers or installation instructions with their sceneries that will avoid this problem. Of course, if the file date is old, it could be that it was built before some of these details became generally understood.