• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

"Out of memory" Error messages

R

randyjohnson

Messages
1
Country
us-missouri
Hello everyone. New to the forum....I look forward to getting to know you all better.

Here's my system:

Intel Duo Core 2...E4400 at 2.0
2GB DDR 2 Ram
NVidia 8500 GT w/512mb DDR2

I have been tweaking the setttings on FSX for a while now...but I keep getting these "out of memory" error messages.

As a general rule of thumb, what settings would you guys recommend for this system?

Thanks again...and it's nice to be here!
 
Phil Taylor (Aces) reported it's currently possible to get this error under Windows XP 32 bit because the maximum addressable amount of memory for a single windows process is 2Gb, no matter how much physical memory you have. This happens on higher end systems that can handle higher levels of detail at reasonable frame rates. Also seems highly dependent on how much physical video memory you have to hold textures - meaning, that the problem is worse with say a 256Mb video card than with a video card that has 512 or 768Mb of memory.

My experience is that it is more frequent with add-ons that load dlls in the FSX process space, example, my .NET loader that can easily use 500Mb just for itself when running the CLR and the programs. Essentially, you compound the effects of high polygon counts in memory with program memory loaded by the FSX process. Any request beyond 2Gb total will give you the out of memory error. This doesn't happen necessarily immediately in flight as it may take some time for the total memory allocation to reach 2Gb.

The only choices available seem to be:
- switch to 64 bit version of OS (XP or Vista)
- add more memory (4Gb), and use the /3Gb bootstrapper switch on Windows XP 32 bit - this is set in the boot.ini file.
- decrease level of detail or number of in-process add-ons (those added via the dll.xml file) to reduce the memory footprint.

Note: not adding memory and using the /3Gb switch is theoretically possible, but my Nvidia drivers went bonkers when I did this. I found out this has something about how DirectX handles the /3Gb switch and systems with less that 4Gb total physical memory. DX allocates memory near the top of the physical memory range and (euphemism aside), behavior is "undertermined", read, "use at your own risk and don't be surprised if you get a blue screen". Oh, and it's not supported because 64 bit alternatives exist.

Etienne
 
Last edited:
You must log in or register to reply here.
Back
Top