Hi. Is it possible in group of bgl files, to find which one is landclass. I would like to move landclass files in separate folder to prevent mem leak. Thanks

 

Some developers will name the landclass files with _lc as a suffix.

 

If you cannot tell by looking at the filenames you could try decompiling the files. Depending on the program used to create the file, there are different utilities to do this.

 

The easiest way might be to determine what files do what by removing them from the active scenery folder and seeing what changes are made in the sim.

 

Are you having problems with a specific addon?

 

If so, which addon is it and where did you get it?

 

Maybe somebody has already done this and can post specific info to help.

 

regards,

Joe

Does landclass really cause memory leaks? I know that autogen did. In all the years of flying FS9 LC has never caused me any leaks - or not that I have ever been aware of.

 

David

I have never heard of autogen causing memory leaks.

 

There is a bug in FS9 that causes memory leaks if landclass files are in an active scenery folder that is paired with a texture folder.

 

As I understand it, FS9 allocates memory resources when it looks for expected texture files called by landclass files.

 

When FS9 looks in the paired texture folders and does not find the textures it is looking for it then looks in ...\FS9\Scenery\World exture yet does not release the memory it had allocated for the paired texture folder.

 

This leads to a situation where unused memory is tied up waiting for FS9 to find the textures and eventually will result in an OOM crash.

 

regards,

Joe

LWMViewer2 will load all scenery bgls for a location and show what type of scenery they contain. Otherwise you can load files into the sdk TMFviewer one by one (terrain files only).

 

scott s.

.

Thanks.

I generaly asked because as I remember there was a tool, which could scan all scenerys and give information about incorrectly placed landclass files.

But I cannot remember the name.

About explanition from Joe about Memory leak, I don't understand if fs9 looks in World/Texture folder how is possible that if I copy same textures from World/Texture in to specific scenery Texture folder, then I don't have Memory leak. First I identify missing textures and then copy from World/Texture into specific Texture folder.

Another solution will be to copy landclass bgls in to new LC folder without texture folder.

Example is my post about LTBA memory leak. I copied textures from World/Texture and after that no Memory leak. But easyest solution will be to move specific bgls in to new LTBA_LC folder.

 

Thanks

About explanition from Joe about Memory leak, I don't understand if fs9 looks in World/Texture folder how is possible that if I copy same textures from World/Texture in to specific scenery Texture folder, then I don't have Memory leak.

FS9 will always look in the texture folder paired with the scenery folder that contains the .bgl first.

 

If it does not find the called textures it then looks elsewhere. For most scenery objects the second location is ...\FS9\Texture. If FS9 recognizes the .bgl as landclass it will instead look at ...\FS9\Scenery\World \texture.

 

As I understand it, when FS looks for textures it reserves memory addresses for those textures. The landclass bug is that FS does not release those reserves when it does not find the textures in the paired texture folder. Instead FS reserves different memory addresses when it looks in ...\FS9\Scenery\World\texture.

 

As you fly around FS is constantly looking for those textures and every time it does it reserves new memory addresses until there are no more available, then you get an OOM crash.

 

When you copy the textures from ...\FS9\Scenery\World\texture to the paired texture folder FS no longer needs to look in multiple places to find them and no longer ties up unused memory addresses in the process.

 

The cost of that procedure is hard drive space and additional challenge if you should ever want to change the default textures.

 

My description of events might not be 100% accurate, this is how I understand it works.

 

regards,

Joe

I have never heard of autogen causing memory leaks.

 

regards,

Joe

 

This was included in Microsoft's read me file which accompanied their FS9.1 patch:

 

Fixed Autogen performance degradation –

Flying out of an area then back to the same area may cause lower frame rates. The problem was due to a memory leak and how Flight Simulator handled autogen objects. Depending on the specific configuration and scenario, some users observed significantly lower frame rates. The update fully addresses this issue and users should have full functionality of all autogen objects without adverse performance problems.

 

So there certainly was a memory leak associated with autogen.

 

David

So there certainly was a memory leak associated with autogen.

Ahhh, I see.

 

My FS9 came pre-patched to 9.1 so I never had to deal with that.

 

Thanks for posting.

 

regards,

Joe

That explains it then !! I seem to remember it was a much discussed topic before the patch was released.

 

David

 

I generaly asked because as I remember there was a tool, which could scan all scenerys and give information about incorrectly placed landclass files.

But I cannot remember the name.

 

IIRC the old FSManager program could scan for landclass files. I don't know why, but for some reason I didn't think it was too reliable and didn't use that function. Of course getting FSManager to run takes a bit of effort. There is a patch around for it that will let it run as long as you put it in the right folder.

 

scott s.

.

Thanks Scoot.

Yes, FS Manager :Peace: