Out of memory error (WinXP)

[macca22au]

I haven't followed this accurately so I apologise for any repetition.  For WinXP there is a /3GB fix that is available.  This allows FS to allocate more than the fixed 2gigs. It seems to be well established. There is also a 3GB enabler that can be downloaded from Game forums for Vista, which involves rebatching FSX.exe.  If you look at the Flightsim forum there is plenty of reference to this.  Phil Taylor warns against this because of a DSD bug in FSX - something I thought would have been corrected as his bio speaks of his experience with this functionality.  However I am going to give it a try.  I have a tech lined up to do it.  If you see a mushroom cloud over the southern horizon, you will know it didn't work in Australia, and the whole reinstallation process is beginning again.

However when the new hardware and drivers are available post DX10 patch and the end of the year, and the equipment is fast enough to run the game well, I am contemplating going back to RTM for the benefits of the better handling of scenery (no verdammt 2 mile pop-up ring).

[macca22au]

As a postscript, I blogged Phil Taylor about the known D3DX bug.  I wondered why, seeing this was his specialty area before FS, this bug was not fixed.  His response was "if and when" the D3DX team do anything, he will look at it again.  It means that FSX users with more than 2 gigs of RAM are condemned to microstutters and Out of Memory crashes, or they take the risk and use the gaming work-arounds that are now available - with the responsibility being carried by the consumer.

[Hansie]

Thanks guys for all the replies! I'm now only checking the messages, but will give all these new insights a chance over the weekend.

[macca22au]

Go to Flightsim forums, FSX, thread #22622 for a full discussion of the fix. It also contains all the necessary links.   [glow=yellow,2,300]If you use it do so at your own risk[/glow].  Incidentally as I read it FSX allocates a total 2 gig for all memory, no wonder it can clog up.

[justpassingthrough]

Thanks guys for all the replies! I'm now only checking the messages, but will give all these new insights a chance over the weekend.

Someone suggested you may want to try these:


http://downloads.guru3d.com/download.php?det=1644



Operating System: Windows XP/2K 32bit
Driver Version: 158.27
Driver Date: 2007-05-11 (YYYY-MM-DD)

They were leaked and are beta but will bring you out of the 9xx series driver and put you into one that is recent which is said to include fixes FSX likes

Wednesday, May 23, 2007 3:33 PM by Phil Taylor

2.     Install updated drivers ( nVidia recently released the 158.22 nVidia Forceware drivers ) and we hear that a release in 2-3 weeks will fix the texture locking issue that the glass panel tweak addresses.

They are designed for all cards up through 8800 for Windows XP x32

I was also told you may have to retweak the FSX.cfg file after installing them.

good luck

[Hansie]

I

[macca22au]

Regarding memory, I suggest you look at Flightsim forums #22622, where you can access the 3GB enabler.  Phil Taylor warns against it, because, yes, there is an unfixed DXD3 bug in an FSX .dll.  And like government the problem is handballed to another department to fix!  Many have tried this fix and found that it works.  At the moment I note that with an e6700 CPU my machine is running 100% at certain times, so the stutters.  It needs to run off RAM and MS can't give us a fix because someone else is responsible for a problem.  I thought Microsoft was a business - I thought it was only governments that ran inefficiently, in firewalled departments, and with diffuse accountabilities;  and only governments that told us going backward was the way to the future.

[macca22au]

sorry I should have said it gets all clogged up because regardless of your installed RAM and the space that you set aside for paging,  FSX only allocates 2 gig.  The game is the problem.

[justpassingthrough]

[quote]sorry I should have said it gets all clogged up because regardless of your installed RAM and the space that you set aside for paging,

[Hansie]

@macca22au, memory clogging again; just to make me understand exactly:

I did the following: Before starting FSX, I had 1408772 bytes free memory, on idling on the runway FSX used 849500, at the time of the crash: 792900, so FSX only used 615872. That's nowhere near 2Gb. Do I have to add some virtual memory to the equation? Where do I find that figure?

The numbers in a table:


BTW, I have the patch downloaded to my HD and I do now understand the whole concept, but want to be as sure as humanly possible before I have a go at it.

[Hansie]

More stuff I tried. Maybe useless, but at some point you start trying stupid things.

• Installed latest DX (Find it here) => OOM
• Deleted fsx.cfg so FSX could rebuild it => OOM
• Ran the repair utility of SDK SP1 => OOM
• Installed SDK SP1a => OOM
• Installed SP1 again => OOM

[Hansie]

Hi, I'm back!

You'll see by the title of the thread this message that I'm now past the patch of trees and I was able to check out Lake Mead and the Hoover Dam. I'm happy for now: Track IR works, joystick works, SP1 works...sweet!

Edit: (OK, I was hoping the [SOLVED] tekst was copied to the beginning of the thread. Well obviously not)

What did I do?
Tuesday night I uninstalled FSX; today I reinstalled it. In approx. 1 hour it was done. OK, I still have to install the SDK and get all my add-ons back from the backup and above all my own created scenery, but I'm confident about that it will work too.

Mind you, I did not do a thing about the stuff that was still in the registry after the uninstall! All I did extra was manually deleting the folders C:\Program files\...\Microsoft Flight Simulator X and the folder for the SDK.

I installed the game in a different folder!

I'm glad that I didn't experience all the problems others had with reinstalling FSX, up to losing everything on the harddisk (I read that somewhere; don't know where).

I checked the memory situation as I did in the beginning, but could not see any difference, Well I didn