NGX and Windows XP

[SimonWard]

HelloSorry for the dumb question but I use XP 32bit and fly with default FSX scenery most of the time,with all the system programing etc will I have to go to 64 bit ??Kind RegardsSimon Ward

[flyerboy]

HiI wouldnt think so. Many simmers would be using 32 bit. In fact, I dont think FSX was designed for 64 bit anyway IIRC.You should be OK

[thefsxflyer]

HiI wouldnt think so. Many simmers would be using 32 bit. In fact, I dont think FSX was designed for 64 bit anyway IIRC.You should be OK

No you don't have to but its recommended. Can usually get rid of OOM (out of memory) errors. Although not sure if XP suffers from that.

[Tabs]

It'll run on 32 bit but we highly recommend 64. You're likely to get virtual address space OOMs in 32-bit, especially if you're running a bunch of scenery addons and stuff too.

[SimonWard]

HelloThanks for your answers will look at upgrading in the future but dont use any addons with FSX so hopefully ok for now.Can run PMDG J41 and MD-11 ok without OOMs.RegardsSimon Ward

[NJ_Flyer]

Ryan..Short of upgrading to 64-bit, is there an "easy fix" to this OOM issue? I get it pretty much every time I try to use FSX on W7 32-bit. Ive read a lot of posts but they all seem to be hit and miss. I was running FSX on an XP 32 bit machine but I spent some money and upgraded the majority of the hardware and obviously W7... been getting the OOM issues in FSX since!.... if you wouldnt mind just putting the NGX to the side and come around and fix this problem that would be much appreciated!

[Tabs]

Ryan..Short of upgrading to 64-bit, is there an "easy fix" to this OOM issue? I get it pretty much every time I try to use FSX on W7 32-bit. Ive read a lot of posts but they all seem to be hit and miss. I was running FSX on an XP 32 bit machine but I spent some money and upgraded the majority of the hardware and obviously W7... been getting the OOM issues in FSX since!.... if you wouldnt mind just putting the NGX to the side and come around and fix this problem that would be much appreciated!

There's no true solution - it's a fundamental limit of the mathematics of 32-bit memory addressing. You have a theoretical maximum value of 4GB of addressable memory in 32-bit Windows - by default 2GB is reserved for User and 2GB for System. The procedure below shifts some of the System space to User, but you're cutting into what's reserved for the System by doing that. This is especially dicey if you have a video card with a lot of RAM on it, as the card's memory is considered part of the system portion. If you run out of system address space, Windows itself is going to crash, not just FSX. 64-bit has a much higher limit (8TB) and it can't run out of address space there.You can try this procedure, but it may not solve the issue:Credit to NickN's guide:

1. Open a command prompt with Administration rights. You find the command prompt box under "Programs-Accessories-Command prompt" 2. Right Click the command prompt and select "run as administrator". 3. Enter in the box at the prompt:bcdedit /set IncreaseUserVA 2560 and press enter 4. Reboot

To set that back to default just start the command line prompt with Admin right again and type: bcdedit /set IncreaseUserVA 2048 Hit enter and reboot

NOTE: It is possible you may need to TUNE this value if out of memory errors still display, especially with large video memory video cards (640mb and above)

If you sill see OOM errors, do the following:

Depending on your OS follow the directions above about editing the system for the cache value. What you will do is LOWER the value edited to the system originally. The amount should be DROPPED in lots of 64.

EXAMPLE:

Original Edit = 2560LOWER this to 2496, reboot and retest.

If OOM still appearsLOWER the edit to 2432, reboot and retest.

If OOM still appearsLOWER the edit to 2368, reboot and retest.

If OOM still appearsLOWER the edit to 2304, reboot and retest.

etc