After reading Phil's post about high memory usage I set the userva at 2560 2.5Gb instead of 3072 to give the OS more room to operate.It still works and may even be smoother.

Hi Bob,can you post a link to Phils posting?I guess the use of 2560 MB might be enough, and more for the OS might be help too.I will try these settings too and report back.

I don't even know how to post a link to a thread. Tried but it didn't work. It's in the long 'Is anybody not getting the blurries' thread. Posted on May 22 5:29PM.Do a search on 'VRAM' in the past 7 days and then search on VRAM in that thread and it will get you close.It doesn't address this specifically, but you'll get the idea. The links to MS Technet that I posted above say essentially the same thing.I've done 2 flights of about 2 hours each since changing this and have not had any problems.

Hi Markus,>>Try this only if you have at least 2 GByte of RAM and at your>own risk.>>Enter "bcdedit /set IncreaseUserVA 3072" (without quotes) in>the command window and press enter.I am getting OOM errors after flying with the LDS767, and saw your OOM fix. I have 2GB of RAM, so would your fix work on my system? Just wondering, because it looks like the IncreaseUserVA command tells Vista to use more than 2GB... but I only have 2GB installed.Thanks!

As I have stated before, there is a known bug in D3DX and effects files when using the /3G switch; which is why we havent done this and dont recommend it.YMMV as to faith.

>As I have stated before, there is a known bug in D3DX and>effects files when using the /3G switch; which is why we>havent done this and dont recommend it.>>YMMV as to faith.True. Using /3G + Windows XP 32 bit:-Plane textures not loading (silver) (in-flight and free flight/choosing plane view).-Airport textures not loading (black)-IL-2 Forgotten Battles does not work properly (extreme slowness)And yes, I made all steps properly. Maybe this tweak improves blurries (I didnt noticed. All seems to look the same to me), but the price is too high.Tested with 4Gb + Dual Core 6400 + SP1 (and w/o it too) + XP Pro 32bit.Sorry.

Hi,why not give it a try?Cant check it, because I changed too Vista 64 so there is 4 GByte awaylable without tricks.

va==virtual address, not physical ram.this expands the virtual address space. the paging mechanism handles mapping that to hw memory.

I blogged about the fact that the June DX update is supposed to have fixed the D3DX issue.I would still raise caution about doing this, the 2560 userva choice seems like a better limit than 3G due to the other reasons I raised.But if it works for folks without crashes with the June DX update, great.

Hi Bryan,I used that trick and only have 2GB Ram. I also took Phil's advise that he posted on his blog and set userva to 2560 instead of 3072. I haven't seen any OOM messages since making the change.Regards,Jim Karn

Thanks folks for the replies. When I get back to tinkering with FSX, I'll give it a try.Cheers!Bryan

How to set 2.5 GB in Windows XP? I use the 3B switch in bios.ini. I don't suppose i can change it here to 2.5GB???

I was reluctant to try this but other fixes, like newer drivers only extended the time I could fly. I got up the courage to go for it and it has worked for me. I can crank it up and fly and fly and fly. No more oom for me. It doesn't get better than this.c2d [email protected], 4GB ram, Nvidia 8800 GTX, Vista 64 Ultimate, Dell 24" LCD

remember there are 2 things we are doing:1)tweaking the OS to allow processes to access up to 3G virtual address space2)tweaking apps to set how much process address space they can accessSo you always tweak the OS to enable 3G. Then you tweak the app to what is appropriate. So far it looks like 2560 is the best for the app setting for FSX.

I posted how to edit the boot.ini file for Windows-XP in the last post in this thread. Including how to set the userva switch.http://forums.avsim.net/dcboard.php?az=sho...d=405828&page=5No blurries or OOM CTD for me since setting "/3GB /userva=2560" in my boot.ini file while currently only runnig 2GB of physical RAM as my second pair of 1GB sticks had to be RMA'd.Good luck...