If you don’t overfly any other addon airports, it is bound to grow maybe couple of 100 MBs. When you fly along, this usage will slowly grow. So for example: you start your flight with an addon aircraft and addon airport, and your VAS usage is 2800MB.
And most importantly, due to nature of FSX, this space is not freed as you fly along, nor has anyone yet come up with a plan how to free it up or fix this problem. Some use more, some use less, but they always take some VAS space. What we should be aware of, is how much our addons use. When this space fills up, you are presented by windows with a very nice message that your memory is low and the application will now close.
This setting alone offsets the VAS usage by couple of hundred MB when bumped from default 4.5 to 6.5 (I also suggest this in my guide, but with the caveat that it can pretty quickly cause an OOM). One of the biggest culprits when VAS is concerned is LOD_RADIUS in FSX.cfg. All those nice airport sceneries, HD aircraft textures, they take a very heavy impact on the VAS when loaded. Since we do have a limited space of 4000MB, we have to have concerns when this space is going to fill up.
Be that an aircraft textures, airport scenery, tree texture, whatever you install and run, is going to have its place in VAS. Everything you load into FSX, basically loads into VAS. So what does it mean? FSX has 4GB of VAS to work with. Does it matter how big or disabled your page file is? No. Remember this, as this is the 101 for OOMs.ĭoes it matter if you have 4GB, 8GB, 16GB, 32GB of RAM? No. (32bit OS + 32bit application = 2GB of VAS, or max 3GB with a tweak) VAS is a specific space for an application, which can, under 64bit operating system be up to 4GB for the 32bit application.Ħ4bit OS + 32bit application (FSX) = up to 4GB VAS DO NOT think physical memory or page file have anything to do with this. Simply explained, VAS is a working space of a program (let’s just call it that). I also have to give my thanks to many other fellow simmers, who also helped me understand the basics of memory management and how FSX works. I have been observing this development in the last couple of years, as the first OOMs appeared.
I’d like to keep this simple, for everyone to understand why is FSX crashing as of late more and more. Please note I’ll try to keep this document as little technical as it can be – all the technical information about the VAS can be found on the pages like Wikipedia, Microsoft, Memory Management explanations etc.
Where i can find ,if ever,the fsuipc log,because i'm newbie to this.I found the event log of windows and here it is: Log Name: Applicationįaulting application name: fsx.exe, version: 7.0, time stamp: 0x46fadb14įaulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000įaulting application start time: 0x01cfe49d44a32662įaulting application path: F:\Microsoft Flight Simulator X\fsx.Due to the fact that an OOM discussion pops up every now and then, and it usually starts from beginning, today I’d like to start a page about Virtual Address Space.