I have 2 Samsoft Sceneries, "Shanghai Today 2004", and "The Very Singapore"I have been experiencing severe memory degradation and increasing page file usage in both scenery areas.Searching the forums I came across a post regarding Landclass .bgl files causing such a problem when they are in a scenery file in a scenery folder with a texture folder. In both of those sceneries the LC files are mixed in the main scenery folder which also has a texture folder. I created a sperate Landclass folder for each scenery, put the LC .bgl's in there assigned the folder in the FS9 scenery cfg, and VIOLA!! NO more memory leak I'm now going to check all my other sceneries.Paul Gardner

Paul, I don't understand how a .bgl file, which contains only data, can produce a memory leak.I can understand how .dll files, which contain algorithms that initiate and terminate processes and threads, can be responsible for memory leaks. How can a .bgl file cause a memory leak?

>Paul, I don't understand how a .bgl file, which contains only>data, can produce a memory leak.Agreed. Never heard of "data" causing memory leak.Michael J.WinXP-Home SP2,AMD64 3500+,Abit AV8,Radeon X800Pro,36GB Raptor,1GB PC3200,Audigy 2http://www.precisionmanuals.com/images/forum/747400.jpghttp://www.hifisim.com/images/asv_beta_member.jpg

Hello,When FS finds a LandClass scenery.bgl file in a scenery folder AND there is a texture folder related it search AND LOAD ALL the textures into memory ---> out of memory.If there is no texture folder related no problem.This is a simple explanation in fact it is a bit more complicated !

I'm no computer expert and therefore I haven't any idea but I read in another post that a landclass file in a scenery folder with an associated texture folder causes memory leak.It solved my problem!!!!!Paul Gardner

Paul is absolutely right.... I do not have a technical answer but he is right! :-lol

regardsEd

http://forums.avsim.net/user_files/125085.jpgAMD Athlon 64 3500+, 1024Mb PC3200 DDR, 300Gb HD 128Mb DDR Nvidia 6600GT PCI Express, Audigy 2 ZSCH Products Yoke, Pedals and Throttle Quadrant

very easy answer. The bgl by itself doesn't cause the leak, the existence of this file in combination with the texture folder does. FS9 exe or one of its dlls causes the leak - code relating to the landclass bgl (yes, it's a known bug). However, as far as I know, this has been fixed with the 9.1 patch (not 100% sure though).Christian

Which folder are the landclass files supposed to go?

Hello,What I did : I did create a World LandClass folder with his scenery folder and I put ALL Landclass .bgl files in that scenery folder ......> and it works !It can be more sophisticated , you may create a LandClass Folder per country, per continent , ......Hope it helps

I

Hate to bring up such an old topic again, but . . . . Would these memory leaks also cause bad "flashing" of textures at WSSS? I have a VERY serious flashing problem at WSSS. What are the names of these LC bgls? I would like to move them and see if that works.

Be very careful here folks, check with the developer. The leak is not anytime you find a landclass file with an associated texture folder. IF the texture file contains autogen for the landclass file then having the texture folder is ok. The leak is actually well known BUT it is when there is a lanclass associated with a BLANK texture folder. In this case, the landclass searches the blank texture folder and when it finds nothing it goes on to search the global texture folder. Problem is the memory space used for that search is never released, hence the memory leak. In summary, just because their is a LC with a texture folder does not necessarily mean an automatic memory leak.-PaulLiquid CooledAMD 4000 San Diego2 Gigs Kingston Corsair XMS CL2Dual 7800 GTX 24 inch widescreen dual 19 inch LCDRaid-0

Actually I fixed the issue on my end. The flashing was indeed the AFCAD file move. I "copid" instead of "cut". Once I deleted the AF2 file from my scenery folder and left only the copy in the addon scenery folder, my flashing went away instantly. The issue was the AFCAD elements trying to override the scenery elements.I had a similar problem with Flightsoft's HK2k4 when I accidently was stupid enough to put the AFCAD I downloaded into the HK2k4 scenery directory. Whipped it out of there and put it into addon scenery folder and all flashing went away there too. I also had very similar issues with Simflyers and moving the AF2's in the same manner cured the issue.Now as a religious rule I examine ALL scenery I ever install. If the scenry installs AF2's in their directories, I immediately move the AF2's to a single folder where all of my AF2's go so that I never have flashing texture issues again.:-)

Good tip, I am going to try that at my FlyTampa sceneries and see if it helps...Thanks,-PaulLiquid CooledAMD 4000 San Diego2 Gigs Kingston Corsair XMS CL2Dual 7800 GTX 24 inch widescreen dual 19 inch LCDRaid-0

:-) Now I never had an issue with the Flaytampa sceneries, but did with the Simflyers, yet some folks have issues with some and others with others -- so best to indeed try that and see if it helps. If not it may be another issue -- like Flightsoft's HK2K4. Moving the AFCAD killed the AIRPORT flashing, but that hertrocious watr flashing will always remains because the silly folks made the water and mountains OBJECTS instead of mesh :-(At least, though, it was great to learn of the AFCAD placing for the airport's sake :-)