Sunday, April 28, 2013

Possible OOM fix for FSX/P3D.

FSX/P3D. So as I continue to dive deeper into P3D I also am looking for tweaks to make my experience better. Now mind you, I am not messing around with bufferpools and nor am I keen to screwing with my .cfg  files. Now for the most part, I have figured how to reasonably enjoy P3D and various addons and this is mostly due to trying to come out of my FS9 mindset. But one thing I just could not get over was the constant OOM's I would get in P3D. So I tried something I don't think anyone else has thought of. An idea most of you might call stupid. But you know what, for me, it freaking works! I would like to know if it works for you too.


So if you former FS9 folks out there remember NTCore, these guys developed the 4GB patch which allowed FS9 to take advantage of a 4 GBx64 based operating system. This was the ultimate fix in killing the dreaded OOM's in FS9 when end users migrated to the Windows7 platform.

Now this left me wondering if an 8GB patch was possible for P3D. Well it doesn't seem likely at all. However, so damn desperate as I was, I went on ahead and tried that old 4GB patch on my P3D.exe and I have to honestly say I have not seen an OOM since. Now before wasting your time on this I have been conducting tests over the last 2 weeks and I have done many things to attempt my P3D to crash but it will not! Moreover, my P3D used to crash when my RAM reached 60% (all background programs switched off) now my my system is reaching up to 85% without OOM in P3D.

Today I selected 5 payware aircraft including the heavy Carenado's like the SR22GTSX and B200. I also changed scenery locations several times both in and out of FTX regions. Still no OOM!

So I would like for some of our readers to try this if you are willing. Please back up what you need to back up first!! I would really like to know if this is working for others. I don't know why it is working for me. No clue. I have no reason to believe why it should work. All I can say is it seems to work for me. I have not seen an OOM in quite a while and I am still trying. Now mind you all I have are helicopters, ultralights, VFR aircraft, and commuter short range turboprops (Majestic Q-400) with a couple biz jets. So I don't know if this will work on you NGX folks.

But please give it a shot and let us know if it at least helps at all. If it doesn't help at least in the tiniest bit, feel free to call me an "A"hole for wasting your time.

You can get the patch here: http://www.ntcore.com/4gb_patch.php

Please report back either way.
_______________________________________

Follow us on Twitter! / Like us on Facebook!
AirDailyX -We do things differently!



35 comments:

Anonymous said...

Downloaded. Will report soon.

Anonymous said...

Will it work with FSX too?

Anonymous said...

Hi there,

Had 2 OOM's yesterday in Prepar3d - driving me mad. I will definitely try this - it doesn't say which files it edits or which ones to back up. I have a diskimage from last night of my Prepar3d drive - will this be enough? Let me know and I'd be happy to test to get rid of this nightmare!!

Anonymous said...

What exactly are you saying? You patched the P3D.exe to be largeaddressaware? Wasn't it that already?
P3D is a 32-bit application, like FSX is. That means it is physically impossible for it to address more than 4Gb. We are talking about the physical limitation of 32-bit applications here. The ntcore patch sets the largeaddressaware flag in the file header, allowing the file to address more than the standard 2Gb of virtual address space that can be allocated to a 32-bit process. On a 32-bit operating system, you need to tweak the userva value, so that the system can still run. If you allowed the application to address 4Gb, then the 32-bit OS would have no space left to allocate to system-critical processes and thus crash your system.
This issue is not a problem on a 64-bit OS, as the 4Gb max limit is not present. Where dies this 4Gb value come from? 2^32=4294967296 bits, divide this by 1024 3 times and you get 4...
For your information, 2^64=17179869184Gb...so VAS theoretically on a 64-bit system is not an issue...
Running a largeaddressaware 32-bit application on a 64-bit OS allows you to address the maximum 4Gb of VAS available to a 32-bit application, with no issues for the OS. But the 4Gb wall is still there...

The only way to get round this is to create 64-bit versions of FSX/P3D...

I can only assume from the lack of OOMs you have been receiving since patching the P3D executable is that the file was not largeaddressaware... which I find hard to believe...

AE

ALX WNT said...

No it's not working, never will - if you already have x64-. Because P3D is actually FSX + SP2 so, P3D is already have this extra 2GB as default. I say it's placebo effect, nothing more. To test 4GB VAS 'really' start on YMML or Coffs Harbor in Australia with NGX HD VC textures. Or YSTW - Canberra flight with NGX. I tested this patch couple of days ago, and made test flights between YSTW - Canberra one of the most demanding flight routes of FS history i believe, each time in Canberra approach i get OOM error. Because 4GB VAS is passed.

Anonymous said...

Guys, i don't want to stop your enthusiasm, but this can't ever work.

P3D startet its development on FSX/ESP SP2. So the large adress awareness bit is already set in the executable. Which allows you to use 4gb VAS in 64bit environment.

how to measure?:

Your RAM consumption is no help to proof your workaround. The only thing that counts is VAS. So pls download and start process-explorer, make the column "virtual size" visible and monitor the p3d.exe As long there is no 64bit executable of this task you can't gain VAS over the border of 4GB. If you reach it it will cause OOM, regardless which tweak you use or how much physically memory is on board or used.

P3D has a main disadvantage compared to FSX. They removed DX10 renderpath, which wouldn't waste VAS of ~500mb anymore, like this happens in DX9 conditions on operating systems starting from NT6.1 (vista) and younger.

There are only 2 strategies to avoid OOM:

a) less details: autogen, LOD, parallel working addons within FS,...

b) the usage of DX10, which needs compatible products.

fridberg said...

This is interesting indeed. I am going to test this out.

Anonymous said...

Just so you know, this may only be relevant on P3D, as FSX's SP2/Accel implemented the 4GB switch into FSX for 64bit operating systems.

Anonymous said...

Just tried this. My problem airport has always been CYVR with Orbx PNW, FSDT Vancouver, Opus FSX, NGX737 PMDG - LOD only 3 and other settings all ok for other locations.
I'm afraid to report it doesn't work - I got marginally further out of CYVR before warnings started but it wasn't by much and flying back on a circuit caused my OOM to come back again. Sorry but I don't think we have found the magic fix here yet!

DAndre Newman said...

Simply back up your P3D.exe and navigate to it in the patch.

DAndre Newman said...

I agree with you. There is no reason in the world why this should work. And yet, for some odd reason, it just seems to be working...

DAndre Newman said...

Like Ai said in my post, may not work for NGX folks...

DAndre Newman said...

Ill dig further into that. Thanks!

DAndre Newman said...

CYVR is a tough cookie isn't it? FT made that whole city of Dubai get 30 fps but get a mile within YVR and BOOM!!!

Anonymous said...

It can't work for you either. FSX and SP2 is upgraded to use 4GB and P3D is the same. The patch doesn't do a thing, it does however for Sony Vegas which costs 8 - 900 dollars and just uses 2GB but that's off topic. You not getting OOM's is pure luck and I would enjoy it while it lasts :)

Anonymous said...

P3D = FSX's SP2/Accel

Anonymous said...

Getting OOM's is easy, avoiding them is something else. Lower settings and most of the times you will be in the safe zone. I create video's and have had this problem at CYVR and Helsinki. Helsinki I found out though that when I looked don in the VC, so at the chair, and only look up when I was about to land that the OOM didn't happen. I think it has to do with the amount of **** it needs to display and crossing certain invisible FS borders.

Anonymous said...

It's actually ridiculous. I take off and speed as far away as I can as quickly as I can with the OOM's hot on my tail. I escaped them earlier but it was close! Time for a 64 bit release (Prepar3d v2.0 perhaps?) - drives me mad

DAndre Newman said...

We are expexting LM to release a fully new P3Dx64!in Q4 2013. I cant wait for that. Honestly, sorry it doesnt work for you guys. Perhaps its something else I did.... I admit, there is no reason at all why this should work and the concept is stupid, but im not getting the OOM's anymore... I dont know what to say guys...

ALX WNT said...

DAndre, you can use process explorer and watch your VAS usage. I'm actually curious if you passed 4GB VAS or else.

I made a flight to Vancouver by FSDT with NGX, and even in lowest settings it's impossible to fly there.

Therefore it appears that you can fly to FSDT Vancouver only with default aircrafts...

I dont care this though, i'd like to see VAS usage of iFLY users, if it consumes less VAS, i might consider to test it

Cheers

DAndre Newman said...

Sure I will do it later today and update you.

DAndre Newman said...

I fully understand the logic. But my OOM's have stopped for some reason. And only after applied the patch. Yes very odd. I know.

Anonymous said...

'P3Dx64!in Q4 2013' hasn't Lockheed said that it would not be x64. I believe I read that somewhere. And from reading alot about 2.0 a lot of people are speculating more likely 2014 than Q4 2013... just info that I read. But heres hoping to 2.0 and big fixes!!!!

Here is a quote posted by a Prepar3d team member back in january this year

"Thanks for the question, we are all very hard at work at v2.0, and sincerely think with the aforementioned move to DX11 and some of the other things we are working on, you all will be very pleased.

This code base has never been to DX11 before, so it does take some time to get everything right, so we appreciate your patience

Have a great weekend!"

Anonymous said...

Not to get on the this touchy subjet again but you can fly there with the NGX but you need to use DX10. I will say that I did have to drop the ground res to 2048 and the shadows to 1024, but my buildings are 4096 and I'm running REX, UT2, Vancouver V3 and ORBX PNW. I run everything else on max including water except for road traffic at 35, only because you get some weird artifacts in areas of high road volume in DX10. I get close to the limit on descent but not over and I even did a multi-leg run yesterday all in one shot, KPHL-KORD-CYVR.

wideloadwhitford said...

Reinstall with fsdt settings all low for YVR?

DAndre Newman said...

No your normal settings.

Mark Batarina said...

Running FSX with the NGX+REX textures+CYVR+REX weather engine in the background, I can say that 8GB is definitely not enough. I constantly check my memory usage and 3/4 of my memory is being used then boom, crash. No other programs except what's listed above is running. I just installed 16GB of ram and no OOM errors occurred anymore, even when EZdok and fraps are running in as well. So unless you don't use external programs, 8GB is probably not enough to run. Just what I encountered.

DAndre Newman said...

I agree too... With a flick of a switch I can upgrade to 16GB. Just waiting and hoping...

Mark Hrycenko said...

So maybe D'Andre is onto something with his OOM fix. We have been contacted by an undisclosed developer who has been able to create a second FSX/P3D process with a second VAS (Virtual Address Space) which can under very specific circumstances prevent OOMs...

Anonymous said...

http://kostasfsworld.wordpress.com/2012/09/24/oom-out-of-memory-helperfix/

Anonymous said...

Just installed but how do I know if it is running at all. I usually dont have any OOM

Anonymous said...

This has been said 1000 times... no doubt it will repeated again and again. RAM is NOT the same as virtual address space. Upgrading the PC to 16, 32, 64, 1024GB RAM will not stop FSX/P3D from OOM'ing at 4Gb VAS use...

We are not talking about RAM here, we're talking about VAS, virtual address space, which is limited to 4Gb for a 32bit application.

A 64 bit system has tons of VAS and can run a large number of 32-bit applications, each one receiving 2-4Gb of VAS for itself, depending on whether the application has been modified to be largeaddressaware.

The only way to stop FSX/P3D from OOM'ing at 4Gb is to create a 64-bit version of the software. Then Windows can allocate a much greater VAS, how much is dependent on the release and version of Windows...

AE

DAndre Newman said...

Then why bother??

Mije said...

I thought I should give this a try.
All was fine except system freeze and buzzing looping sound.
Right after applying the patch. I tried running prepar3d. Sim won t start anymore. Starting p3d forces my screen resolution down and prep3d says u need higher resolution.
I then click OK to improve res but this will open a box appearances that has nothing to download with resolution. Manually changing resolution at that point or before running p3d doesn't help.
Tried removing prepar3d cfg file to reconstruct send use exe backup but ni luck.

Is there a place where oreoar3d keeps display information that I could delete... Maybe a temp cfg file? Thanks for your help in advancs

Mije said...

system restore help solve the issue but i would appreciate an answer to my question if anyone knows.....

Post a Comment

Comments are now deactivated. Please visit our new website: AirDailyX.net

Note: Only a member of this blog may post a comment.