There's no "memory exhaustion" anywhere in our products and Flightbeam products.
In fact, of all sceneries around, our and Flightbeam's, are probably the ones that would suffer LESS of memory exhaustion caused by other products you are running, most likely a very memory hungry airplane.
The reason for this, is that we create most of our objects ( which makes for 90% of the scenery ), programmatically, ONLY when you are inside the scenery loading range, which is fairly short, usually from 10 to 20 NM around the airport center. This way, we surely don't suffer of any memory exhaustion that other scenery developers have to face, because if they do everything using .BGLs, they are entirely in the hands of the FSX memory management, which is known to be very buggy, and usually keeps in memory .BGLs that don't have anything to do with the area you are flying in.
I don't think that program you are referring does anything to improve memory management, since it's just a glorified FSX.CFG tweaker, with many of its functions already offered for free by the Addon Manager tweaks sections, but if you had memory exhaustion problems caused by your combination of add-ons ( memory hungry airplanes, too high settings, etc. ), that resulted in our sceneries being AFFECTED by them, because those other products exhausted your memory by the time you landed, they won't be fixed by any tweaks.
As discussed many times already, when CYVR came out and, being located in an area where many users already had too many add-ons to run FSX safely, and mistakenly thought that CYVR had anything to do with OOM, when proving this wasn't the case, the usual suggestions still applies to every other place:
- Lower your settings in the most dense areas
- Switch to DX10, which saves quite a bit or memory
- Don't use 4096x4096 textures.
- Use less memory-hungry airplanes (or configure them to use less memory, if the allow it)
