I'm pretty sure it's just a matter of accepting FSX's limitations and lowering the sliders a bit in those uber demanding areas

Hey Dario, long time no see.. hope everything is well. Quick question, when you used process explorer to monitor the user space memory usage did you by any chance monitor GPU memory usage at the same time? I'm pretty sure DX9 (both with WDDM 1.0, 1,1 and even the old XPDM) will page out to system memory and/or create a virtualized memory area which dynamically changes based on GPU memory utilization, so the more video memory being used the more SYSTEM memory the actual process will consume because a copy will be kept in SYSTEM ram. This was changed in DX10/11, but I'm 99.9% sure DX9 keeps a copy (or reserved swap area) in SYSTEM RAM I just can't find the MSDN article I read about this. Can you replicate the 3.8 memory usage scenario consistently? can you try it with DX10 and see if it uses less system memory?

I get the crashes on in the initial FSX menu area – only when I leave it there for quite a few minutes. Never had an inflight crash (computer, that is!). :) My DisablePreload is set to 0. I should change it, but I can't be bothered as I'm taking off at the same airport every time at the moment, so I have a default flight set. I have 4g/b of ram and a 512m/b video card. My theory is that FSX is overfilling my video card, which then spills into the computer RAM (I believe there's something in my BIOS that allows this - I'm not as technical these days as I once was!). I got an unconfirmed, unprovable theory that it's the video card memory spilling into the computer RAM that is causing out of memory errors for me. More computer and/or video ram would probably help. If I have more than 4 GIG, sure FSX can't use it, but can the computer use it to extend video card ram?

Well if it helps, and I'm sure it will not. I have Windows 7 64-Bit. Running the programs below, and I have not had any OOM errors, all my sliders are full right except for water. I run no Page File and have zero hard page faults. No tweaks execpt for HIGHMEMFIX. Thats it.

Yeah i dont understand it either

It's because the we push FSX harder. I know I do. The faster my rig, the more settings I turn up. One of the easiest ways around this is to make custom cfg files for certain areas you fly in. For instance I was getting OOM's in OrbxLand (mainly near SEA and PDX) with LOD 6.5 (custom edit I know I know) and max autogen. I turned it down to lod 4.5 and dense autogen. Then saved the settings to a cfg (options, display, save). It helped keep my VAS down to a more manageable level.

Well I increased my page file size to over 4gb, I deleted the FSX.cfg file and allowed the program to build another, *******'d it and put in [Main]DisablePreload=1 entry. It worked.... for an extra minute then I got OOM message. Really strating to get under my skin so I deleted FSX and reloaded with SP1 then SP2. Loaded PMDG 737NGX and all looked OK. Loaded ORBX FTX Australia(High grade scenery package) and started getting OOM messages again. Disabled ORBX scenery and returned to FSX generic scenery. Had my first flight tonight. I really enjoyed the flight model but a little bit of reading required to fully appreciate the goodies inside. 2D Panel looks stretched{any hints for fix would be appreciated) but 3D panel looks very nice. Thanks for all those who threw in their two bobs worth. I love flying but am not that computer savvy and really appreciate those who are prepared to share their knowledge.cheersJohn Cornish

I had the same problem, it is caused by the amount of memory the NGX can use. (Obviously) You need to allocate enough virtual address space (VAS) available to FSX to avoid the problem. (and Yes WinXP 32bit does support the /3GB and /USERVA switches in the boot.ini) Even allocating 2.5GB VAS isn't enough. I find you have to allocate 2.8GB VAS to avoid the OOM's. This isn't a problem if your video card is a 512MB card. If you have a larger card, like I do, you can potentially run into problems since the video memory address space will encroach on the extra application allocation. So far though, I haven't had a problem with it, and I've flown transcontinental flights from JFK with 100% UT2 traffic, REX and ASE successfully. My system is an E6850 3.0Ghz 4gb, with a 1GB GeForce GTX 460. running WinXp 32bit Home SP3.

It's because the we push FSX harder. I know I do. The faster my rig, the more settings I turn up. One of the easiest ways around this is to make custom cfg files for certain areas you fly in. For instance I was getting OOM's in OrbxLand (mainly near SEA and PDX) with LOD 6.5 (custom edit I know I know) and max autogen. I turned it down to lod 4.5 and dense autogen. Then saved the settings to a cfg (options, display, save). It helped keep my VAS down to a more manageable level.

I've never had a OOM in the 10 years i've had FS, i've had other issues in the past with addon scenery,aircraft ect... never a issue with any PMDG produtct thru the years guess i've been lucky

So far though, I haven't had a problem with it, and I've flown transcontinental flights from JFK with 100% UT2 traffic, REX and ASE successfully.

Tom, which is your REX texture seeting? 1024 or higher. Just asking because for me it helped to reduce the REX texture size from 2048 or 4096 (whatever I had before) to 1024 and since then no OOMs. Seems to help some though not all who see OOMs.

Hey Dario, long time no see.. hope everything is well. Quick question, when you used process explorer to monitor the user space memory usage did you by any chance monitor GPU memory usage at the same time? I'm pretty sure DX9 (both with WDDM 1.0, 1,1 and even the old XPDM) will page out to system memory and/or create a virtualized memory area which dynamically changes based on GPU memory utilization, so the more video memory being used the more SYSTEM memory the actual process will consume because a copy will be kept in SYSTEM ram. This was changed in DX10/11, but I'm 99.9% sure DX9 keeps a copy (or reserved swap area) in SYSTEM RAM I just can't find the MSDN article I read about this. Can you replicate the 3.8 memory usage scenario consistently? can you try it with DX10 and see if it uses less system memory?

Hi Jesús Sure, I will try that, both in DX9 & DX10, and I will try with different AA settings, like the VRAM hog AA_MODE_METHOD_SUPERVCAA_64x4v12 to see if there's an increase in FSX's virtual space with it.I know about that Windows article, we discussed the matter here in this thread where Ron linked it Will get back to you later today

Ok, I'm testing now.I can see a lower VAS than before, not sure why but a couple of things changed since the first tests:- I was loading the plane in a pre-saved flight in LEPA, then changing the location to KSEA (I'm not too smart, I know )- I have the Hot Fix installed now- I have removed one GTX480 since the SLI wasn't helping with AA in the VC and DX9 mode (I even tried a fresh Win 7 + FSX install to no avail, I couldn't get the SLI working at more than 50% each GPU even in bad weather and massive 8xSGSS / 32xS). Also reinstalled the graphics driver as a consequence With my original "demanding" settings including Extremely dense scenery, Very dense AG, 75% airline traffic and 25% GA traffic (MyTrafficX) 30% road vehiclesAA set to 8xS + 4xSGSSKSEA PNW, fair weather, frames unlimited, DX9 2.8GB initial VAS - hitting 3.3GB after a while700MB of VRAM I changed the LOD to something ridiculous like 8.5 to force it to crash and sure enough, it did (OOM) as soon as it reached 4GB of VAS in process explorer, that was sort of expected, and is 100% repeatableWith 8.5 LOD, VRAM usage increased just to 850MB Gonna test the VRAM usage impact on VAS with 64x4v12 now, in DX10 too EDIT: tests with different IQ settings / VRAM usage in DX9. This is just sitting on the tarmac, no flying, lined up RW34 at KSEA AA off / AF off / LOD 4.5VRAM = 534VAS = 2511 MB (initial) - 2587 MB (after 4 minutes) AA 64x4v12 + 8xSGSS / AF 16x / LOD 4.5VRAM = 907 MBVAS = 2508 MB - 2589 MB AA off / AF off / LOD 8.5VRAM = 734 MBVAS = 3266 MB - 3464 MB AA 64x4v12 + 8xSGSS / AF 16x / LOD 8.5VRAM = 1105 MBVAS = 3240 MB - 3444 MB An extra 400 MB of VRAM from no AA/AF to max IQ settings doesn't seem to translate into an increased VAS usage now DX10 tests... that's going to be a little different since AA doesn't work too well in DX10 AA off / AF off / LOD 4.5VRAM = 621 MBVAS = 2337 MB (initial) - 2434 MB (after 4 minutes) AA on / AF anisotropic / LOD 4.5VRAM = 709 MBVAS = 2342 MB - 2446 MB There's not much I can do to push VRAM in DX10 with the limited AA that can be run, so I tried at 1280x720, no AA, no AF.... AA off / AF off / LOD 4.5 / 1280x720VRAM = 588 MBVAS = 2323 MB - 2415 MB meh, still 588 MB of VRAM. nothing conclusive when comparing DX10 runs I guess, but there's not a big difference with the DX9 tests either. 200MB of extra VAS in DX9 is not too much. If WDDM is supposed to keep just a VAS window of VRAM, as opposed to the full shadow copy in XPDM, these tests don't seem to show much benefit

Damn the edit timeout heheDid one more test on DX10, LOD=8.5 VRAM = 910 MBVAS = 3165 MB very close again to DX9 figures. Managed to crash the sim after a while, just the same

Tom, which is your REX texture seeting? 1024 or higher. Just asking because for me it helped to reduce the REX texture size from 2048 or 4096 (whatever I had before) to 1024 and since then no OOMs. Seems to help some though not all who see OOMs.

My textures are 1024. I never had a OOM on my system til the NGX. I had a 9800GTX 512MB card with USERVA set to 2816, and was able to fly the NGX with no problem, except low frame rates. After seeing the performance Sean (cambellsjc) was getting from his shots in the screenshots forum, with his system, which had a 1GB card, I was thinking that maybe the low FPS was from video memory starvation, so I replaced it with the 460. I set the USERVA to 2306, which is what you're suppose to set it for a 1GB card. Result OOM immediately after NGX load. Tried 2560 (768MB card) , lasted a few minutes later. Set it back to 2816 (Which is normally for a 512MB card) and FSX and the NGX was happy. Each time I got the OOM, checking the task manager showed FSX using 1.7GB memory. I can only surmise there was an even higher spike at the time of the actual error. I've never seen FSX use this much, not even with the 747-400. I have yet though to see a OOM with the USERVA set to 2816, and no visual sign of graphic corruption or any problem. Like I said though, I have flown long flights in dense scenry conditions like JFK with traffic, so I think I'm good. As for FPS, it didn't improve that much, but does appear more stable, and I can fly her better without traffic. Not my preference, but I can live with it. I didn't expect a boost from the GPU of course, but I thought I'd get a little from the extra memory, and higher video memory bandwidth.

I get constant OOMs if I start cycling views in a rapid succession. Especially form exterior to interior. So I try and limit my view switching.

Best solution:Find someone who patches FSX and makes a 64 bit applikation out of it.Then you will have enough virtual adress space under a 64 bit OS and no more OOM's. I think the NGX has pushed FSX above his limits but alter my display settings in such a rawly way is not what I want.In this case it will be better to go back to FS9 which is running stable and looking much better as a castrated FSX.

Based on ongoing OOM, BSOD, CTD's ...whatever, I digged in to the past posts and gave it a try to get the events visibleRead the full story and (my) resolution HEREBased on ongoing OOM, BSOD, CTD's ...whatever, I digged in to the past posts and gave it a try to get the events visibleRead the full story and (my) resolution HERE

Hi, If I use a single visual (Virtual or 2D) I not have memory or texture problems. But if during a flight I switch visual between 2D and Virtual panel or others Visuals I get texture errors and finish with memory error. I use REX combined with ASE and IVAO. Definitely this 737 cause problems in 32-bit Systems where the Memory is limited. My System:Windows 7 32 BitsFSX with SP1 and AcceleratorIntel Core 2 Quad Q9650 OC 3.6ghzNvidia eVGA GTX570 OC4 Memory Corsair Dominator CM2X1024-8500C5D (4x1GB)ASUS P5K Premium