Memory Problems...

[Alexander M Zoltai]

I have FS2004 on WinXP-home with 2gig of RAM. I have an NVIDIA GeForce Go 7300 with 256 MB of memory (128 MB dedicated).

I have my virtual memory (swap file) set at 3gig.

I've maxed out the display and aircraft settings and all runs very smooth for about 45 mins.

[microlight]

Hi Alexander, welcome to the big V.

Your spec sounds very similar to mine and the page file is about the same size, although I don't get the kind of problem you mention.

There is always much discussion about OOM errors and what to do/what not to do (many threads on this around the web), but I think what's fairly commonly agreed is that some add-on sceneries can cause memory leakages, resulting in an OOM.

Is this a recent phenomenon; does it only happen when you are flying over a particular scenery area? If the error takes 45 minutes to show itself, then it might be scenery-related; if it was something to do with the sim itself, then I'd think that it would happen a lot sooner.

I'm sure other more knowledgeable members will also chip in.

[Alexander M Zoltai]

Hi Alexander, welcome to the big V.

Thanks for the welcome!

There is always much discussion about OOM errors...

OOM errors?

...it might be scenery-related

Yeah, been flying around Christchurch, NZ alot and I did load in more scenery files there. But then, I also loaded some global files, like water textures...

I'll go somewhere I haven't been and check it out again...

[microlight]

OOM = out-of-memory.

I haven't heard of replacement textures (e.g. ater) causing any memory leakages. Try flying in default scenery and if it doesn't happen, then the scenery addons might well be the issue.

[Fr. Bill]

OOM = out-of-memory.

I haven't heard of replacement textures (e.g. ater) causing any memory leakages. Try flying in default scenery and if it doesn't happen, then the scenery addons might well be the issue.

Just to be crystal clear, the "Out of Memory" error message has nothing whatever to do with physical or virtual memory, nor any "memory leakage."

It has everything to do with the Virtual Address Space table. See my Wiki article for details:

http://forums.flightsim.com/fswiki/index.php/OOM_Error

In this specific instance though it may well be a scenery related "overload" causing the problem. Try flying in another direction, or in a different part of the world to see if it occurs again.

[Alexander M Zoltai]

OOM = out-of-memory.

I haven't heard of replacement textures (e.g. ater) causing any memory leakages. Try flying in default scenery and if it doesn't happen, then the scenery addons might well be the issue.

OK, I ran three test flights.

First, in India where the only additions to scenery are dirt runways and water texture.

I flew well beyond the 45 mins of my Christchurch, NZ experience.

Then, I flew in Scotland. Still the dirt runways and water but also a general Northern Europe scenery enhancement.

I flew well beyond the 45 mins of my Christchurch, NZ experience.

Finally, I returned to the Christchurch area where I have more scenery enhancements specific to the Christchurch area...

Program ran out of memory at 45 mins. just like before.

So, it does appear to be a function of how much scenery additions are in an area...

But...

I now have an interesting challenge...

The places I want to fly are where I have the most scenery augmentation but that leads to reduced flight time...

:-/

What to do?

[Alexander M Zoltai]

Just to be crystal clear, the "Out of Memory" error message has nothing whatever to do with physical or virtual memory, nor any "memory leakage."

It has everything to do with the Virtual Address Space table. See my Wiki article for details:

http://forums.flightsim.com/fswiki/index.php/OOM_Error

In this specific instance though it may well be a scenery related "overload" causing the problem. Try flying in another direction, or in a different part of the world to see if it occurs again.

Please see my test flights in this thread...

I will try to digest all that your recommended thread contains. I'll be back if I don't understand what that post says or if I accomplish what it says and still have my "scenery leakage" problem...

[Capt.Propwash]

my suggestion, .. reduce the amount of scenery in that area, or cut your flights to shorter than 45 min (which is going to be the real bear)

or, you might be able to play with your GLOBAL MAX TEXTURE SIZE, and possibly your MIP MAPPING QUALITY.  as well as other settings.  

its an off the wall question, but what are your Frame Rates durring the 45min span leading up to your crash????

[Alexander M Zoltai]

my suggestion, .. reduce the amount of scenery in that area, or cut your flights to shorter than 45 min (which is going to be the real bear)

No way! Those are not "Solutions"...

[quote]or, you might be able to play with your GLOBAL MAX TEXTURE SIZE, and possibly your MIP MAPPING QUALITY.

[SubZer0]

Hey Alex, and welcome to SimV!

Sometimes, bad scenery design can be the cause of OOM errors. It may not be that you have too much scenery in one area, but that one or more sceneries are poorly designed and cause these errors.

Best of luck finding a fix

Andy

[Alexander M Zoltai]

Hey Alex, and welcome to SimV!

Sometimes, bad scenery design can be the cause of OOM errors. It may not be that you have too much scenery in one area, but that one or more sceneries are poorly designed and cause these errors.

Best of luck finding a fix

Andy

Thanks, Andy! I'm going to explore the info Fr. Bill recommended. Maybe I'll find a fix in the bowels of Microsoft...  

[ShaneG_old]

Welcome to SimV, Neighbor! Right next door to you.

Can't really help much with this one, but Fr.Bill is a wise man in these kind of things.

[Capt.Propwash]

as to settings, it would depend on what you are running at right now.

[Alexander M Zoltai]

[quote]
see pic below for MY settings.

[Capt.Propwash]

to find out how many processes you have running, hit CTRL + ALT + DEL > Processes tab.   look at the bottom of the window.

Processes = ?          CPU Usage = ?             Commit Charge = ?


at current, mine is sitting at 25 // 7% //  520M / 4195M