Recently, I have been having oom errors while flying. I use the ngx, along with REX, and also fsdreamteam KFLL. However, the oom's can happen at any airport. The symptoms begin towards the end of my flights, when I begin my approaches, or begin my final descents. If I switch views, the textures of the vc begin to take a long time to load, and then, I receive an oom error. Sometimes I am able to touchdown, but I end up getting the error while taxiing. Also, I have tried using process explorer, and it appears that my virtual memory begins at about 1.7-1.8 gb, and it begins to slowly increase the longer I am inside fs. Could this be a memory leak, or is this normal? If so, how I do I get rid of this leak.

KjjjI would suspect that this is an issue with the Virtual Address Space. FSX under win 64 has a maximum of 4GB VAS and this cannot be increased. If the VAS becomes defragemented ie there are no contiguous blocks for FSX to load into or it becomes depleted ie using complex scenery and planes and in long flights the end result is an Out of Memory Error (OOM). This is P Taylor's blog on the error: http://blogs.msdn.co...ress-space.aspxThis has nothing to do wioth the physical RAM or paging file in that if they are compromised FSX would slow down dramatically and you would likely see a message similar to "Your computer has run out of available memory, etc" and in the worst case scenario a BSOD. http://support.microsoft.com/kb/892610 The best tool to see what is going on in the VAS is VMMAP downloadable from sysinternals and there are a couple of technet videos on how to use it or interpret it. One "fix" I have seen posted is to use an autosave feature (eg via FSUIPC4 or other) and this seems to reset the VAS and possibly prevent OOMs.One registry hack that I have tried with some limited success is: to use a cmd prompt (as admin) and type infsutil behavior set memoryusage 1 (in win 7 the default value is 0 - not set, 1 = default and 2 = increased.To reset just use 0 as the value. It should only be used if there is lots of Physical RAM on board, it may not work on every PC and you should back up the registry before use. I can supply the regedit version if you feel comfortable in editing the registry.I do hasten add this may not work.RegardsPeterHRegardsPeterH

Thanks for the supply Peter, I guess I have some reading to do, and based on what I find, I might use your suggested registry edit. By the way, I do receive the "your computer has run out of available memory" error and then fsx crashes (my fps also gets extremely low, almost 1-3 fps, as you said). Although most of my settings are maxed out, I still think it is strange that the virtual memory fsx is using just slowly increases as time passes.

Edited February 6, 201214 yr by kjjj11223344

Try the FSUIPC autosave option, as suggested above.. easy to try!Just set it to save every 600 seconds..

Try the FSUIPC autosave option, as suggested above.. easy to try!Just set it to save every 600 seconds..

Works a treat Bert. Tried it after Peter posted this on another thread. 600 seems to be the magic number

Okay I will try this. I don't really have experience with FSUIPC, but I can't seem to find this feature. Does this feature exist in the non-registered version?

Okay this is becoming very annoying. I just had to quit a flight as my VAS was around 3,800,000 kilobytes. Before quitting, I decreased my LOD Radius to minimum, decreased my cloud draw distance (as the sky was very cloudy), and still, looking at my vas, it continued to increase until it reached 4,073,808 kilobytes. At this point, I was down to 1 fps, and my whole cockpit was a skeleton. Do you guys think reinstalling the ngx, rex, fsdreamteam kfll, or the trial version of gsx will help? Those are the only addons I have installed, but I don't want to reinstall them if it wont fix the problem. Or, even worse, do you guys recommend a complete fsx reinstall. My settings are almost completely maxed out, as I said before, but I just confirmed that even lowering some settings, the vas just continues to increase. Or maybe decreasing my aa? I am currently running inspector using the 4s profile as is posted in the PMDG forum.

Edited February 6, 201214 yr by kjjj11223344

I am watching this thread with great interest because even with maxed out hardware, software and settings I never had an OOM error until FSUIPC4 fixed the G3D.dll problem. Until then, FSX would not run long enough to hit the OOM wall. Now I cannot conclude a decent length flight in the ORBX PNW with a complex airplane (like the Accusim B-17) without smashing into it.FSSave will install, but will not run in FSX (possibbly due to some obscure Simconnect issue) so that option is closed for me. According to at least one case in this forum, the FSUIPC4 autosave seemed to reduce performance to below acceptable FPS. When I manually try saving flights with the ; button, there seems to be little difference, with FPS still slowing until the end comes shortly thereafter.We need a cure, or a prevention, or an ingenious workaround like Pete's G3D.dll breakthrough. For now I will settle for anything that helps. Unfortunately I have no positive contribution to make towards a solution, and have my hope in you who are blessed with a larger braincase capacity than my build version was released with. :Nerd:Kind regards,

I too have been suffering OOM's with my 12GB of RAM. Just now, I had one. I have my displays cranked full up while my traffic for airlines is at 35% (MTX) and my road traffic is at 25%. My LOD_Radius was set to 6.5 and I just lowered it to 6.0 and still suffered the OOM.

I too got OOM last week after ... I don't even remember... years. I was quite surprised about it. Are you getting this OOM's only lately or are you getting them "on the regular basis"?

It seems FSX has something like a memory leak bug.It consumes VAS as long as flight proceeed, faster in certain areas/scenery, slower in others.The main workaround I found is to use an older version of uiautomatiocore.dll, a version "aged" almost the same of fsx sp2.I tried different versions and the better I found was downloadable herehttp://dl.dropbox.com/u/28441/UIAutomationCore.zipor herehttp://www.mediafire.com/?mik2mlqdz1w.It don't solve completely the problem but reduce it a lot.Another important thing is reduce lod_radius.If I use 737NGX and lod_radius=6.5 I have oom in 15-20 minutes.737_ngx and lod_radius=5.5 ---> oom in 60-120 minuteslod_radius=4.5 ---> tried 4 hours (up to now) withouth oom.Also, using simpler planes you can have longer "memory endurance".Someone told me another thing to try is reduce autogen density but I prefer play with lod_radius; I change it to 4.5 when flying with liners, and set it to 6.5 when flying VFR with Carenado planes.

bump

I just did a screen shot of how much memory FSX is using, I have 8GB with windows 7. Only use this computer really for FSX. I have been getting oom also.

The main workaround I found is to use an older version of uiautomatiocore.dll, a version "aged" almost the same of fsx sp2.I tried different versions and the better I found was downloadable herehttp://dl.dropbox.co...omationCore.zipor herehttp://www.mediafire.com/?mik2mlqdz1w.It don't solve completely the problem but reduce it a lot.

Both of these UIAutomationCore.dll's are also the wrong version. These are both v 6.0.6001.18000.You can get the correct version here:-http://dl.dropbox.com/u/52676345/UIAutomationCore.place_in_fsx_root.dll The correct version is 6.0.5840.16386Download it, rename it to UIAutomationCore.dll and put it into the root folder of FSX. Don't put it anywhere else and don't register it.!

Both of these UIAutomationCore.dll's are also the wrong version. These are both v 6.0.6001.18000.You can get the correct version here:-http://dl.dropbox.co...in_fsx_root.dll The correct version is 6.0.5840.16386Download it, rename it to UIAutomationCore.dll and put it into the root folder of FSX. Don't put it anywhere else and don't register it.!

Right, I forgot specify this. Put in fsx directory WITHOUT delete or substitute the one in win7 directory.I tried both this version and the version you indicated, and I found v 6.0.6001.18000 more stable and less "memory consuming", but any fsx is different from any other so... maybe in other systems is better the other.