Where oh where

[macca22au]

Miltestpilot had a great thread with a link to a utility that enabled greater than 2gigs of RAM

And an excellent cookbook approach

I have quoted it to many, and now I can't find the thread

Simviation's research function treats me like the idiot I am

I need to repeat the process as I am starting to get CTDs unspecified but which are similar to OOM problems

Miltestpilot if you can't locate your original thread please repeat the post.

[justpassingthrough]

The search feature on this board could use some work

I used:

Search For: VISA

[macca22au]

Thanks MTP:  I did finally find the thread by going through the pages one by one:  not a great indicator of efficiency on my part.

However I still have the problem.  Some time into a flight the whole game shuts down blank and quickly. No notice or warning except for the occasional big stutter-

(btw I think we need a scaled list of micro-stutters, stutters and hitches!!! so that we are all talking about the same thing)

I do get that pathetic window which tells me that FSX has closed down and that Vista is searching windows for an explanation -  It has never given an answer yet.

- I have the game enabled through CFExplore to use more than 2gigs, and the change to bcedit was accepted through the command prompt.

So I assume that was correctly done.  

I have a paging file of 4096-4096 set aside.  I have oceans of disk space so I can make it any size up to 50gigs!

I have 4 gigs of RAM, Cougar 800mhz, should I physically remove one stick?  I understand that 3 gigs will still operate and might overcome these problems.

Or does the problem lie in the game.  I am using FFTF of .10 and a TBM of 30,  rather than the swap and TBM table that others are using.

Or should I upgrade to x64?

signed:  Frustrated

[justpassingthrough]

Dun'no Macca

The only thing I see is that the page file is usually larger than the memory installed, at least that is how default Windows works and that is how NickN has posted for 2GB systems

If you have 4gigs running, the page may need to be higher than the installed amount

With 2gigs we run 3072 or 1.5 times the installed memory

Sounds outrageous but that would be 6144 for you. I cant believe that would be necessary, but if the allocated area is exceeding the page limit, perhaps it is a factor.. maybe raise it 1024 over the installed memory?

You could also try setting to: System Managed, reboot and see what Windows automatically choose for the amount under "currently allocated"

The perhaps fly a short flight that wont invoke the OOM problem and recheck the page to see if Windows made it larger.


All I can tell you about x64 is I have never seen anyone post they have that issue and I have never seen it.

All you have to do in x64 is change the header in FSX.exe



Come to think of it, PTylor did mention if the mapping address amount was too high or low that may cause the same issue and you may have to play with it to tweak the number right.. I am speaking of the value you use for VISTA cache edit in the DOS box. Perhaps 256 higer or lower may trim it out

[Nick N]

Come to think of it, PTylor did mention if the mapping address amount was too high or low that may cause the same issue and you may have to play with it to tweak the number right.. I am speaking of the value you use for VISTA cache edit in the DOS box. Perhaps 256 higer or lower may trim it out

Good thought

That is what I would do as well, tweak the cache change up 256 and see if it fixes it. If it crashes faster, lower it by 128 from the original value. If during the first 256K increase it crashes much further into a session, raise it another 128 and continue to do so until it stops or gets worse.

A reboot must be performed between each change

As for the page.. hmmmmmmm

with 4 gigs of PM a page is typically not needed but in the case where you have a switch set to allow more, it may not be a bad idea to raise it a tad, but I dont expect that will resolve what is being seen.

I do also assume this is the OOM error appearing "Windows has run out of available memory" and not another error of some type.

[Nick N]

The maximum that value can go is

bcdedit /set IncreaseUserVA 3072

Dont set it any higher or you will probably crush the OS address. Even 3072 is really pushing that way too far in my opinion, but try and see. All that can happen is you crash and reboot


that is why I suggested 256 and 128 increments and not bigger jumps

The error you may be seeing is not OOM for the game but OOM for the OS, in which case the original number needs to be lowered to allow more address for the OS itself. The first lower value I would try is:

bcdedit /set IncreaseUserVA 2432

and drop that in increments of 128

[macca22au]

Ok I'll try it tonight.  I am still allegedly working for a living.

It sounds right - everything seems to run backwards in Vista and FSX

- to get FSX smooth I have invariably to push the scenery sliders UP, and to solve the OOM problem I need to reduce not increase the cache size.

I was always told bigger is better - a humiliation for a short man.

[Nick N]

[quote]Ok I'll try it tonight.

[macca22au]

Have any of you used the new Hifisim product, that is the FSX replacement for Active Sky 6.5, which I found good in FS9.

They offer  a bundle that includes the weather program and an environment addition that they claim improves airports, roads rivers, runways etc etc

I suspect that Flight Environment X would be attempting to do the same thing.

[justpassingthrough]

I am waiting for FE X

In FS9 AS6 was the best weather engine but their clouds were not very friendly. FE clouds were the best so I used AS and FE.

Its my understanding you wont be able to use AS with FE this time so you have to choose one or the other. Since FE did such a great job in FS9 I am going to wait and see how well they do in FSX. If there are too many complaints and it turns out they messed up then I will try the new AS for FSX.

I dont want to buy both so I am waiting to see how it does.

[Nick N]

I am waiting for FEX as well

http://www.simforums.com/forums/forum_p ... ?TID=21780

They will be releasing it in stages though. Their weather engine will come after the graphics release but you can

[macca22au]

I might just go the FE X route as well.  If for no other reason than it gives me a financial breather before I invest any more money in FSX.

I reduced the userva number to that which you recommended.

I then did a long zigzag flight in the default Caravan from Friday Harbour (I have the USA terrain add-on) across to the north shore of the Olympic Peninsula, back west, down and over Seattle, out to the coast, more zigs and zags to finish at Portland.

There is a touch of nostalgia there, as I landed a C172 with wife and three kids there in 1973 on runway 10L.  Back in those days I was immensely impressed by the relaxed approach of American controllers compared with the anal behaviour of their Australian counterparts.  It was great to roll-out with 727s, DC10s and DC9s all around.

Back to the point.  I used real world weather, which was fine but cloudy, so there was plenty of loading going on.  In the whole two hours there was no hint of stoppage. (Looks like you had a nice day in the Seattle area). So unless something else happens your advice appears to have cured the situation  

(pro tem, always pro tem with this version).