Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Airport buildings cause severe memory drain

Featured Replies

Can anyone kindly help me identify what is wrong here? I have an old version of LFPB for FS9. I haven't flown there for years, but now that I do I see that there are a batch of airport buildings/hangars (one block, which represents about 25% of the scenery) which cause real problems. When I point towards them in spot view, all the airport (inc. AI a/c) loses its textures (i.e. going silver/grey) for up to 15". The textures do load eventually, but my RAM used shoots up from c.50% to c.75% and everything becomes rather sluggish. If I go back to cockpit view (the RAM slowly recovers somewhat), then after half a minute back to spot view, the same thing happens. The hangars never load properly like the rest of the airport (which, once loaded, stays in memory and is redrawn at view changes in a fraction of a second).I tried moving all the texture files to the main fs9/texture folder, to no effect. Then removing various bgl files - remove enough so that the hangars in question go and things are OK, but of course I have a big gap in the scenery then.Maybe someone a bit more expert than I am (I would say I only dabble in scenery design, and not so much airport/autogen creation) might recognise what the problem is from my description so that I can repair it if possible. Thanks,Martin

Martin Stebbing, EGLF (UK)

Can anyone kindly help me identify what is wrong here? I have an old version of LFPB for FS9. I haven't flown there for years, but now that I do I see that there are a batch of airport buildings/hangars (one block, which represents about 25% of the scenery) which cause real problems. When I point towards them in spot view, all the airport (inc. AI a/c) loses its textures (i.e. going silver/grey) for up to 15". The textures do load eventually, but my RAM used shoots up from c.50% to c.75% and everything becomes rather sluggish. If I go back to cockpit view (the RAM slowly recovers somewhat), then after half a minute back to spot view, the same thing happens. The hangars never load properly like the rest of the airport (which, once loaded, stays in memory and is redrawn at view changes in a fraction of a second).I tried moving all the texture files to the main fs9/texture folder, to no effect. Then removing various bgl files - remove enough so that the hangars in question go and things are OK, but of course I have a big gap in the scenery then.Maybe someone a bit more expert than I am (I would say I only dabble in scenery design, and not so much airport/autogen creation) might recognize what the problem is from my description so that I can repair it if possible. Thanks,Martin
Hi Martin:Could be a bad or missing texture bitmap, or a texture bitmap that needs MIPs to be made in a copy of that file via SDK ImageTool and dropped back into the \Texture folder.Also, be sure there are no "Land Class" BGLs in a \Scenery folder which has been paired with a \Texture folder (this usually crashes FS9).Do you have a link to the download for the airport in question ? :( All I saw at AVSIM was these:http://library.avsim.net/search.php?CatID=...;Go=Change+ViewGaryGB
  • Author

Hi Gary,Thanks for the reply. I think I got this airport (several years ago) from France VFR - as far as I recall it was payware, and I don't see any other version around. Unusually I no longer seem to have the original setup file (I keep all my setup files usually, payware and freeware), just the airport folder itself (of course). I did accidentally delete some setup zip files a few years ago - that must have been one of them. (I now keep two backups, especially of payware stuff!). FranceVFR no longer have LFPB on their website, though it seems to be available in a pack with other airports.As I indicated, removing bgl files in small groups didn't help (I too thought there may be one 'rogue' bgl file, landclass or not). The buildings in question do disappear as their associated bgls are removed (be a bit surprising if they didn't!) but there doesn't seem to be any one particular file or group of files that causes this.If it is a bitmap, how would you advise me to proceed? It's not a disaster if I keep it as it is, I just don't point the view towards the hangars that cause the problems, but it would be good if it were fixable without too many hours spent on it!Thanks again,Martin :-)

Martin Stebbing, EGLF (UK)

Hi Martin:Indeed that would be a nice airport to fix ! :( In which part of the airport are you having display issues with buildings ? :( Perhaps you could identify the area from this top-down view taken with the aircraft at a heading of 89 degrees (looking East).GaryGB

  • Author

Hi Gary,My LFPB looks like this. Pretty much all the buildings in the light-shaded area take several seconds to reload their textures each time you go back to Spot View, and the RAM used shoots up in the process, as I say.LFPB.jpgMartin.. the heading is c. 300 in that screenshot BTW

Martin Stebbing, EGLF (UK)

Hi Gary,My LFPB looks like this. Pretty much all the buildings in the light-shaded area take several seconds to reload their textures each time you go back to Spot View, and the RAM used shoots up in the process, as I say.LFPB.jpgMartin.. the heading is c. 300 in that screenshot BTW
Hi Martin:Sorry for the delay in getting back to this thread.I must say I goofed in my rather hurried FS9 load-up of what I thought was going to be LFPB. :( As I was working in haste that day, I wasn't watching the ICAO display when I typed "LFPB" and immediately hit enter.So I ended up falling victim to the odd mechanism in FS which loads the next nearest alphabetical name in the ICAO list when the string you typed is not in the airport list; if you aren't watching carefully (I wasn't), you'll end up at the wrong airport.FYI: I often disable files for world areas in FS which I don't fly often or at all; I use SCM2004 to "cut and export" Scenery.Cfg areas in favor of a faster FS start-up (at load-up, FS inventories every file in the Scenery Library even if it is not "checked" to be active in the list).And I (used to) sometimes edit a copy of the default airport files in FS9, so without the default LFPB available on my system at the time, it would seem when I started a flight requesting LFPB, I ended up getting LFLB instead... and thus the wrong screenie above ! :(It had been so long since I did anything in France in FS9 I did not recognize that your airport in question, LFPB, was actually Paris Le Bourget 2005 (Simudesign) from FranceVFR, and it did not 'click" that the airport layout should be Paris, rather than the smaller airport shown. :( NOTE: You may wish to review the content on these webpages at the FranceVFR web site:http://www.francevfr.com/promo.asphttp://www.francevfr.com/patch.aspNow having reloaded LFPB, I can see the structures that you are referring to; on my system, however, I do not get the graphical and memory anomalies that you reported. Assuming you do not also have installed (and active in FS Scenery Library), any of the few other freeware or payware add-ons from sources other than FranceVFR that cover that specific Paris airport, it might be helpful to know first of all, if the hangar with the "Air Paint" logo on it displays normally if you save and re-load a flight with the hangar wall and sign in full view of the virtual cockpit of your aircraft being used for inspection. :( BTW: The "Air Paint Hangar" pertinent "LBG_AirPaint01.bmp" texture file is a 512 x 512 8-but bitmap with no Alpha and only 1 MIP; some older systems may need multiple levels of MIPs in textures for better FS rendering performance at complex airports.Knowing if this texture displays OK on that hangar object in FS, but other BMPs in the texture folder pertaining to nearby buildings do not, might help one to better prepare a plan for further analysis.I suggest that you check this out first, before you begin checking to see that you have all texture bitmap file names listed in the BGL / MDL files (as seen in a Hex viewer) present inside your \Texture folder.NOTE: My LFPB \Texture folder presently has 540 objects in it.Also, I am not sure if parts of some nearby buildings are using default FS9 GMAX "gray-scale" materials or if all use custom textures, however I was intrigued by the extruded 3-D sign characters for example on the "Dassault Falcon Service", and I wonder if how they were textured might play a role in the anomaly you reported seeing.As it seems that add-on uses all photoreal ground textures, it does not appear likely that there would be a misplaced land class BGL for controlling "default" land class texture placement in the \Scenery folder, and thus an FS9 land class crash is not implicated IMHO. Hope this belated info might still be of some help ! B) GaryGB
  • Author

Hi Gary,Thanks for taking the trouble to write a detailed reply on this.Yes, I too have a little 'widget' that only enables scenery that I am flying from/to. In fact over the past couple of years I have this tweaked to a 'fine art' (I am, I must admit very proud of my tweaked FS9 setup, with all the extra script files I've written - the result of thousands of loving care (or as my family would say, thousands of hours of wasted of time!! But what do they know?!). I use scenery_ align (AVSIM) - a great little programme, I don't know how I'd fly without it now.But as far as LFPB is concerned, I am wondering whether the problems I have are down to a much more basic cause. I have experimented with this for half an hour or so only, and still cannot say conclusively. But in Spot View the buildings which have trouble loading are in the direction of Paris CDG, for which I have a pretty 'heavy' addon scenery installed. If I load LFPB but view the problem area from the other side of the buildings, so that I am looking away from LFPG (towards the south-west), they load much faster ( though not as fast as buildings elsewhere in the airport) and I don't get so much memory drain.As I say, I may need to experiment a bit more to be certain, and this in any case doesn't explain the memory drain I get, but this look to be a possible cause of some of the problems. If I decide in the end that it is not, I will look in more detail at some of your other comments. (Yes, I too have 540 bmps in the LFPB texture folder).Thanks again,Martin

Martin Stebbing, EGLF (UK)

Hi Martin:I'm curious what computer system specifications you are using, especially what type (AGP versus PCI-e) video card, and what CPU you have.Regardless, in FS9 we seem to have a lot of elbow room to play with in controlling the speed with which textures are allowed to render, and I have resolved some "slow to texture" scenery objects with FS9 via some "work under the hood".There are a few selected and well tested tweaks you could implement in a 'copy' of FS9.Cfg that might help; just let me know if you'd like to try them some time.GaryGB

  • Author

Hi, I recently tweaked my fs9.cfg file for the nth. time ( though the first time in a year or so ). What I have now works brilliantly, textures load quickly and crisply, no matter how complex the scenery, so I wouldn't want to alter it..My PC specs are below my name (as my signature).Martin :-)

Martin Stebbing, EGLF (UK)

Hi Martin:Ah, yes... I see the tiny (gray) text now that I've zoomed in a bit; certainly a hardware performance issue would seem unlikely in FS9 with that rig ! :(BTW: Thanks for the heads up on Scenery_Align... I had missed seeing that when it was released.Hope you solve the Paris scenery display anomaly satisfactorily ! :( GaryGB

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.