After many hours of trial and error testing I was finally able to identify the single file causing this OOM issue.

 

filename: cvxOresund_Terrain.bgl

location: ...\Lockheed Martin\Prepar3D v2\Addon Scenery\FlyTampa-Copenhagen_LC\scenery

 

rename the file to cvxOresund_Terrain_blg.OFF

 

While investigating this issue I also notice that the following files caused stutters and performance issues in P3D V2.5 (12945):

 

filenames: ekch_rwy*.bgl

location: ...\Lockheed Martin\Prepar3D v2\Addon Scenery\FlyTampa-Copenhagen\scenery

 

Hope this helps others running into OOM problems.  Note the file size is Tiny (1KB), but it's memory impact is huge, it'll cause 1GB VAS to be consumed in just a matter of a few seconds.

 

Here is the original issue I was having with FT Copenhagen and P3D v2.5:

 

 

After applying my workaround above:

 

 

I have been in contact with the dev.

 

Cheers, Rob.

Great find, Rob! Thanks for sharing.

Many thanks Rob !

Awesome, Rob, thank you!

I wonder if the same would do the trick for FSX.

Many thanks Rob !

 

Do you test by taking out files and them add them back and test or do you have a tool for that !

I don't have this airport but the implications of your find are interesting and possibly far reaching. Your a star by the way as I would imagine that it took an age to eliminate.

 

I know zero about BGL's but would imagine that they are a script created either manually or with a scenery programme then compiled. So is it the scenery programme, the compiler or how a particular section of code is handled within P3D?

 

Rafal (above) mentioned FSX which implies this is old scenery, which further implies that perhaps when it was released FSX didn't OOM because it was not loaded enough with other scenery therefore the issue never showed up?

 

Perhaps this is a latent bug and what you have found will be amazing. Perhaps I'm making too many assumptions from too little knowledge lol

Thank you very much Rob.

Lost 100mb more VAS disabling this file. Default Cessna, 2.GB free VAS. Stayed like that for an hour.

So possible LOD may effect this file. I run a LOD of 4.5. I think it depends what settings you use that effects VAS.

I use Cloud shadows, but not vege or terrain.

You are relentless, Rob, thank you for all the work!

While investigating this issue I also notice that the following files caused stutters and performance issues in P3D V2.5 (12945):

 

filenames: ekch_rwy*.bgl

location: ...\Lockheed Martin\Prepar3D v2\Addon Scenery\FlyTampa-Copenhagen\scenery

A lot of lights in those files, they probably cost some performance:

C:\>dir "F:\P3D2\Addon Scenery\FlyTampa-Copenhagen\scenery\ekch_rwy*.bgl"
 Volume in drive F is FFS
 Volume Serial Number is BA54-A9B9

 Directory of F:\P3D2\Addon Scenery\FlyTampa-Copenhagen\scenery

18-10-2014  20:32           122.354 ekch_rwy_04L22R_lights.bgl
18-10-2014  20:32           112.056 ekch_rwy_04L22R_pads.bgl
18-10-2014  20:31            53.008 ekch_rwy_04L_appr_lights.bgl
18-10-2014  20:33             1.828 ekch_rwy_04L_papi.bgl
18-10-2014  20:32            94.634 ekch_rwy_04R22L_lights.bgl
18-10-2014  20:32            50.642 ekch_rwy_04R22L_pads.bgl
19-10-2014  02:20            35.904 ekch_rwy_04R_appr_lights.bgl
18-10-2014  20:33             1.828 ekch_rwy_04R_papi.bgl
18-10-2014  20:32            87.074 ekch_rwy_1230_lights.bgl
18-10-2014  20:32            35.102 ekch_rwy_1230_pads.bgl
18-10-2014  20:29             3.492 ekch_rwy_12_appr_lights.bgl
18-10-2014  20:34             1.828 ekch_rwy_12_papi.bgl
18-10-2014  20:27            53.008 ekch_rwy_22L_appr_lights.bgl
18-10-2014  20:34             1.828 ekch_rwy_22L_papi.bgl
18-10-2014  20:30             4.754 ekch_rwy_22R_appr_lights.bgl
18-10-2014  20:33             1.828 ekch_rwy_22R_papi.bgl
18-10-2014  20:29            14.272 ekch_rwy_30_appr_lights.bgl
18-10-2014  20:34             1.828 ekch_rwy_30_papi.bgl
18-10-2014  20:33               546 ekch_rwy_loader.bgl
28-10-2014  05:20         4.651.081 ekch_rwy_units.BGL
              20 File(s)      5.328.895 bytes
               0 Dir(s)  110.544.683.008 bytes free

Thanks, Rob. I've seen VAS usage with this scenery is dependent on which way I take off from. When pointing directly against the airport (sitting on the runway, 04R, L), VAS usage is 600 MB higher in contrast to if I'm faced the other way.

Thanks very much, Rob. I sense a great deal of patient trial and error here. I don't suppose there's a shortcut to finding the problem file, because I suspect there may be one (or two) in Aerosoft Dublin, which consumes a ludicrous amount of VAS for what it is, and it would be good to track that one down.

 

With these .bgls being disabled, does anything obvious go missing from the scenery?

I'm curious Rob, what amount of VAS do you measure when standing on the runway (04 R or L)? I disabled this file but did not experience any drop in VAS used. With LOD radius set to 4.5 and autogen set to normal, after activating ASN and FS2Crew in the NGX I have already eaten up 3600 MB !!!

 

 

Do you test by taking out files and them add them back and test or do you have a tool for that !

 

I wish I had a tool for that, but I don't.  Sadly the process is VERY tedious and is just a matter or removing files and testing.  But the bigger picture I'm more interested in is why such a small file could cause such a major VAS issue ... get the devs and LM discussing is my priority -- don't really care who's issue it is here just looking for solutions.

 

 

 

A lot of lights in those files, they probably cost some performance

 

Some of the lights are done with ASM process which is "probably" the source of the stutters/performance issues in P3D (only) ... the dev's are aware and they're working on a solution.

 

 

 

I'm curious Rob, what amount of VAS do you measure when standing on the runway (04 R or L)?

 

Sorry, don't have VAS numbers for that runway ... I have the VAS values in my videos above but they hard to read unless you run 4K and even then the video is highly compressed so the VAS text is difficult to make out.  But with my workaround I'm starting at about 1.4GB free after takeoff it drops to about 1.0 GB free, then increases again to 1.2 GB free once over Bunkeflostrand.  (note this is with FTX Global 1.30, PILOT's Mesh, and Orbx OpenLC EU, MT6, and ASN 'saved' weather).

 

 

 

With these .bgls being disabled, does anything obvious go missing from the scenery?

 

Yes, but I haven't spent enough time to determine exactly what as my goal was to resolve OOM issue first, the performance issue I just stumbled into while testing.

 

LM are aware of my testing also and are looking into it.

 

Cheers, Rob.

Thanks so much for that Rob. I was going crazy about my oom's and your workarround seems to work cause currently i fly where i get oom' before withour your "tweak"

 

Cheers, carsten

Just did a test flight from EKCH to 29 palms new airport EDBC

with LOD set to 6.5

 

 

 

 

 

 

Perfect