From the Wiki
VAS link;
"In computing, a virtual address space (VAS) or address space is the set of ranges of virtual addresses that an operating system makes available to a process."So this is a computer operating system problem, that can affect
ALL computer programs. But flight sims are the ones that we use with high memory demands.
Any flight sim can run into the same problem because of the massive amount of memory needed to create & hold the world environment that you see
and fly over.
The high quality of the Philadelphia airport
KPHL from Sun:Sky:Jet is enough to raise my VAS memory by 200 megs
JUST FLYING OVER IT!.
The problem that they are talking about, is that the operating systems that we use aren't completely releasing that memory.
The article by Kosta makes some general suggestions.
One solution in
FSX, OOM and Addon VAS Usage is to use a program called
FS2004/FSX Scenery Config Editor to activate/deactivate the scenery that you fly over.
After all, if you're in an airbus A380, a mile high
over KPHL, you don't need all that detail.
BUT your flight sim will load most of it anyway.But read Kosta's comments before you use it.
Another is to limit the amount of high detail textures that you use.
Still another is to save and reload the flight after restarting the flight sim.
To do the last one, you need to monitor how high your flight sim program memory usage is, and stop it before it hits the brick wall.
That program, for anyone who's interested, is also great for tracking down a great many problems. Among other things, I used to use it to remove viruses when nothing else would.
That program,
Process Explorer, is very simple to use, but can be very hard to understand.
In Kosta's article he give EXACT instructions on how to use it for monitoring the
VAS related to your flight sim.
If you want you can read
FSX, OOM and Addon VAS Usage for tips & skip over all the fine points.
To over simplify the problem - The high quality that you like is the cause of the problem.
Use simpler scenery detail. Reduce the "Level of detail" radius in the sim. Save and reload the flight every now and then.
There is one problem with memory that is assumed by the people discussing the problem.
A 32bit computer operating system can have up to 4 gig of memory. But as soon as you turn it on, it will use some of that 4 gig to operate. So in reality, that 4 gig machine will only have about 3.4 gig for you to use.
And it could even be less depending on what other programs autoload on your system.That means that the
VAS memory space for your flight sim is going to be much less in practice.
My 64bit machine has 16 gig.
BUT FSX will only be able to have a
VAS of 4 gig reserved for any program, FSX included.
With you and I using the
EXACT same plane, flying over the
EXACT same scenery,
you will crash & burn, as I keep on flying.