Computer has run out of available memory

[snoopy51]

thanks Fozzer

[flibinite]

If you are using photoreal sceneries, make sure to disable as many as possible, as they apparently use VAS. Also, suggest experimenting with different aircraft on this flight to see if the same problem keeps occurring.

[Bass]

Hello Bass
Okay I will then also use Bojote´s tweak tool, (and remember to make a safe copy first), what stands "hw aso" for (You wrote "every time i change hw aso" )
I can see why You call it " NickN's tweak bible" it´s a big guidance to come through, but it looks like there a many good things inside it.
regards
Otto

....hardware also?

Paul.... ...!

Thanks Paul. You covered Otto's question perfectly.
aso=and so on

[767-300]

FSX is a 32 bit program, it can only use 4gb max

[OldAirmail]

FSX is a 32 bit program, it can only use 4gb max

Actually FSX will use LESS than 4GB on a computer system that has 4GB.

Some of that memory is used by the OS, and some is held aside for "possible future needs".

In fact some memory is even kept aside for the Windows swap file.


One of the interesting things about FSX and memory is that EVEN if you're flying at 45,000 feet over a city FSX is loading that city into memory.

Unfortunately, after flying past the city not all of the memory is freed up.

And that is one of the reasons that FSX will crash. Particularly on long flights.


In a way, those with a very simple sim setup can do a little better on a 4GB system.

I usually have quite a few FSX support programs running with, along side, and under FSX.

Things like Plan-G, OpusFSX, two SEPERATE instrument panels, and a browser or two with airport charts, etc.

Using a CPU/memory monitor I have seen my memory go a little over 6GB while flying.

Normally? Between 5GB & 6GB while flying.