Where did that come from ?

when one throws around words like heaps, stacks and handles it sounds like one really knows what one is talking about. ps.

yes, although mine is himemfix=1 instead of highmemfix=1

*cough*

when one throws around words like heaps, stacks and handles it sounds like one really knows what one is talking about.

LOL -- yes,,, that's why I deleted 90% of what I typed earlier,, and just asked the SIMPLE question -- "where did that come from ?" One can actually monitor & visualize the VAS in real time, with the right Software Development tools, and although it slows FSX down to a crawl, one can clearly see VAS memory being allocated, and de-allocated.In all my years of FSX development, I have never seen the Microsoft written part of FSX request more than 64 megs of Contigeous memory at a time. It is up to the addon developer, (If they are writting In-Proc Dlls), to check memory availability, and raise handled exceptions, if they make a request for Unavailable memory. Otherwise, it is no wonder that a FSX addon dll might crash FSX. I known, I obviously do not have a clue what I am talking about, because I did not mention Heaps and Stacks .

I use Disablepreload=1 in the cfg, without any issues with PMDG aircraft. All complex aircraft in fact! http://forum.avsim.n...virtual-memory/

Yeah except I was a total noob when I posted that... I had to learn more about the virtual mem/VAS stuff... it's actually the VAS not the virtual mem.