The symptoms of FSX running out of memory were autogen spikes from the ground till the sky, blue or untextured polygons on the ground, gauges that kept freezing and very bad framerate. After these signs started to appear it was impossible to continue to play. Sometimes FSX crashed and gave an out of memory error.
My problem proved to be not the actual size of the memory (in my case 2GB of RAM and 1GB of video memory), but actually the way Windows was allocating that memory, in this case the VAS (Virtual adress space) which is the same size no matter how big the memory is. In some cases FSX needs more than it can access from the VAS. By default FSX uses up to 2GB of the VAS, while the rest remains available to the system. In some cases this is not enough for all the complex addons in FSX.
There is a way to increase the maximum available VAS for any application, incl. FSX. More details about this and the method to fix it can be found here.
Below the method to do it:
- Disable hidden files and folder.
- On the root C:\ you will find a file named: boot.ini
- Open boot.ini in notepad and add the following to the end of the OS boot line:
like in example below:
multi(0)disk(0)rdisk(0)partition(2)\WINNT="Microsoft Windows XP Professsional" /fastdetect /3GB /Userva=2560
- Save and close the file;
Windows Vista/ Windows 7
BCDEDIT /set increaseuserva 2560
BCDEDIT /set increaseuserva 3072
It is possible to starve the operating system's slice of VAS to the point that your system will no longer boot!
If this happens, you must reboot the computer into "Safe Mode" (which bypasses the /3GB switch, and then edit your boot.ini (WinXP) or use bcdecit (Vista/7) to reduce the size of the application slice of the VAS.
Do not try this method if you don't have enough computer skills to do repair it in case something goes wrong. Use it on your own risk.