Simviation Forums

While FS was admittedly running for a few hours already, ADE really had no excuse to use that much, all I did was just now start it up and load a single stock airport (KMSP), that's it, so it's only been up for just a few minutes. Then I got the "out of memory" pop up. The problem is, I have already applied the 4 gb patch to FS, since my system (seen in my sig) has 4gb of memory....

FS itself is still running fine, just with the pop up still up.

What do I do?

PlutonianEmpire wrote:

While FS was admittedly running for a few hours already, ADE really had no excuse to use that much, all I did was just now start it up and load a single stock airport (KMSP), that's it, so it's only been up for just a few minutes. Then I got the "out of memory" pop up. The problem is, I have already applied the 4 gb patch to FS, since my system (seen in my sig) has 4gb of memory....

FS itself is still running fine, just with the pop up still up.

What do I do?

The 4GB patch has nothing to do with this error you are running out of disk space on your system or C drive

First thing I would do is to bring up the uninstall window and remove any thing from your system drive that you do not need.
I would than invest in a good DEFRAG utility program the one that comes with windows is not all that great.
The only other thing you can do is to get another hard drive even a external one will work. Of course a external hard drive will usually be slower with data transfers than a internal drive unless you have a external 3.0 USB port
Some store bought computers do not have a open space for another internal hard drive. I bought a 1 TB external USB 3.0 hard drive and have both FSX and FS( installed on it.
The best way to go is to not have FSX or FS9 on the same drive as your OS is on. But not every one can afford another hard drive.

My internal hdd has 274 gb of space, with 132 used and 141 free, according to the properties window. I do have two external drives, one is an old one about the same size as the internal, and the other is a 1 tb drive. FS is only one of two major graphics program on my laptop, the other one is an open source space rendering software.

As for defrag programs, do you know of any decent freeware/non-trialware ones?

try it without airport design editor running.
you ARE running out of avail memory not HDD space

whats your operateing system ?

Windows 8.1 x64 bit.

OOMs even after the patch are not too unusual when running complex AC or scenery. I wonder if your 4gb or RAM are adequate - FSX can't use more than that, but Windows and other programs need RAM too. I'd have at least 8 gb

Given my current pace, I won't have enough money for that until at least 2050.

And you memtioned FSX being unable to use more than 4gb of ram; I take it then that it doesnt include FS9 since you recommended having at least 8 gbs?

PlutonianEmpire wrote:Given my current pace, I won't have enough money for that until at least 2050.

And you memtioned FSX being unable to use more than 4gb of ram; I take it then that it doesnt include FS9 since you recommended having at least 8 gbs?

My old system had 4 gigs of ram on it and I never ran out of memory. Have you changed the way your system handles Virtual Memory? Some people prefer to set this at a certain amount so as not to take up so much ram the problem with this is if you guess to low you will get this message.
As you can see by my signature I am also running windows 8.1 but I have 12 gigs of ram.
But I never ran out of memory with FS2004 even on my old system.

Hi,

I don't know about setting virtual memory on win 8.1 but so far throughout windows
history it's been the same method, on my win 7 64bit system it automatically
sets virtual memory to the same value of your systems RAM, in your case 4gb.
I'd set it to double that and you should not then run out of memory.
You may need to adjust it slightly, if you try and set too much the chances
are you will actually start to slow your system down.

On my win7 if I try to set it too high it warns me so hope that win 8 does the same.

This is how I'd do it on my win7,
Right mouse click on 'my computer' (Computer on start menu) and select properties.
left click on 'Advanced System Settings.
Now then, on mine it's called Performance and a button called Settings, if yours has
that then click on the Settings button then click on advanced.
Somewhere on the next screen it may say 'Virtual Memory' and give you the current
setting, on mine it's 7930 MB for a system memory of 8GB : click on change.

If there is a box that ticked indicating the system is managing the virtual memory size
then you need to clear this: click on custom size on set the maximum size to 8000,
it maybe worth while leaving the initial size at 4000 which it maybe set to, the reason
for this is that it may slow your system startup down if the initial setting is too high.
It doesn't on mine but may do on yours.
Click on SET and then OK and it will warn you that you have to restart to change settings.
If your in the middle of something then restart later.

If win 8 is diff to win 7 and the above is not right then a search on the internet should give
you a guide.

Also on win 7 task manager you can set the number of processors that fsx.exe
uses, I'm guessing you can do the same on win 8.



regards

steve

About virtual memory/page file, windows should pop up with a recommend size, which is 1.5 your installed ram.
That means 4gb x 1.5 = 6.

Doing the virtual memory thing made OOM errors skyrocket. Reverting to the automatic managing of it fixed it. And rather oddly, the "Recommended" was displayed as 3377 mb, even though I have 4 gbs of ram.

If you're running a 32-bit version of Windows, it will never see the entire 4 gig of memory. Your numbers look "normal".

gwillmot wrote:If you're running a 32-bit version of Windows, it will never see the entire 4 gig of memory. Your numbers look "normal".

You are correct at best you can see 3.2 to 3.4 gig if you know what you are doing. This is a limitation of a 32 bit system and can not be changed.

Hmm. My system is indeed 64-bit; all the labels I've seen, from the box it came in, to the dxdiag info, all indicate a 64-bit system...