then we can start to offer suggestions on how to fix the problem.

 

Who is "WE"?

 

 

Who is "WE"?

 

The AVSIM Community, who else ?

Hhahah!! Always looking for interested volunteers, Tom!! :lol: :lol:

The AVSIM Community, who else ?

 

I just wanted to make sure I was not part of the 'we'... But I guess I am part of the 'we' using your definition, whether I want to be or otherwise. :rolleyes:

 

 

I just wanted to make sure I was not part of the 'we'... But I guess I am part of the 'we' using your definition, whether I want to be or otherwise. :rolleyes:

 

Well, you created the beast... Sorry if you feel I dragged you down into the mud...

Hello everyone,

 

With the new ORBX England installed I get OOM's when approaching an airport. For airports I use the Uk2000 sceneries. Beside of that i always fly a PMDG 737 and my weather is controlled by AS2012. When i'm about 10,000 feet from the ground i will receive a OOM message. I have very good hardware (as described below) so i think that is not the reason. Are there any suggestions to prevent the OOM's so i am capable of flying the PMDG on a UK2000 airport with FTX England without reveiving a OOM? Thanks in advance.

 

My specs:

- Intel 3770k @ 3,5 Ghz

- Nvidea GTX 670 2 GB videocard

- 500 GB satall drive

- Asus P8h77v-LE motherboard (with will be replaced next week for the ASrock z77 extreme 4)

- 8 GB Corsair Venegance RAM

 

The way I fixed a similar issue I had with FSX...was by removing the memory limit in FSX.exe.... this was done using a program called "Explorer Suite"... found on www.ntcore.com.

I have screen shots of what needs to be done but they cannot be posted here...does not like it...

 

email me & I will get it [email protected]

That's only if he's running stock FSX, i,.e. without SP1 or 2 - SP2 being already LargeAddressAware.

 

I have to assume that he's at SP2, with the addons he has. Of course a reply from the OP would help, too!

I was messing with FSX last night and discovered that if I disabled ORBXLIBS in the scenery folder I was able to land at EGKK at around 3.6 on VMAPP as opposed to running out of memory. Disabling it in the scenery library gave me an extra 400mb to play with, no idea why, not that techyy.....

I'm not sure CPU speed is a factor here - even with an ideal PC for FSX you will probably get these OOMs in places like London with AI, highly-detailed airliner, weather and max settings etc. The problem is virtual address space.

UPDATE:

 

Yesterday I've installed a new z77 motherboard that give me the oppurtunity to overclock to around 4,5ghz. Beside of that i've done a complete new Windows install. In this case, I'm ableto build FSX up from the ground again. This time, I will install FSX on a new SSD, only for FSX. For installing and tuning FSX i will read the guide of Nick. Are there any suggestions for preventing OOM's when i'm building FSX from the ground again? Thanks.

Word Not Allowed's guide is better, Rogier, and fully embraces the wealth of new and proven finds and changes from many people.

 

Personally the OS does not manage my page files:

C-drive is a 200 gig HDD with a 100MB-100MB custom page file.

D-Drive is the DVD burner.

E-drive is 1TB and is used for all file storage, and has a custom PF: 3172MB - 3172MB.

F-drive is FlightSim only. No PF

 

The desktop heap is 1024, 20480, 1024

 

Hope this helps!

I don't tweak (except for adding HIGHMEMFIX=1), but if you insist on doing it, try adding one tweak at a time. That way you can see what causes the sim to crash. That said, sometimes it is a combination of things that fail, and you'll never be able to solve it.

 

Also I recommend that you run some benchmark software to make sure that your computer is running flawlessly before installing FSX.

 

For twekas these two guides have a large fanbase:

 

Nick Needham, third post from the top:

http://www.simforums.com/forums/different-scenarios-different-settings-thats-how_topic41798_page3.html

 

Word Not Allowed:

http://#####.wordpress.com/fsx-software-and-hardware-guide/

Paul (and others who might be interested) your comment on DX9/DX10 memory and VAS got me digging a bit further, particularly following Umberto's similar comment recommending DX10 as an OOM fix in one of the CYVR threads. That eventually let me to this Microsoft KB article: http://support.microsoft.com/kb/940105 .

 

My takeaway from this article is twofold - first, Paul you were absolutely correct about DX9 apps duping video memory in their own VAS and DX10 not. But second, it doesn't matter in an up to date version of Vista or Win7, as Microsoft recognized that this would become an increasingly large issue, (GPUs were at that time beginning to expand past 512 MB and DX10 had not yet been widely adopted) and made a change to the way the OS' video memory manager worked for legacy DirectX apps. This patch has been a part of Windows since Vista SP1.

 

Prior to my finding this article, my own quick tests confirmed that this duping couldn't be happening on my system as FSX memory usage in DX9 and DX10 was very similar in simple tests.

 

That's not to say, however, that there might not be other memory advantages in moving to DX10 and this will probably push me over the edge to giving DX10 a more serious look. My new video card was supposed to be here yesterday, but seems to have gotten lost somewhere between Amazon and UPS, but as soon as it does get here I'll be doing some DX10 tuning myself to see where it leads.

 

So, thanks Paul for the stimulus to do a bit of learning,

 

Scott

It's an uphill battle, Scott! :lol: