i ended up reinstalling p3d 2.4 and i added a 16 gig page file on a seperate ssd and haven't had an oom yet.and i have 16 gigs of physical ram

 

 

and i have 16 gigs of physical ram

 

This is completely useless for FSX and Prepar3d. 32 bit applications can only address 4 Gb of RAM. Regardless of how much physical RAM you have. The size of the page file also does not change anything regarding potential OOMs.

must be a strike of luck then, something was eating my vas up,i understand there is a difference between vas and physical ram, i just simply stated i havent had an oom since changing my pagefile,in the past i had no page file at all.

Second Test Flight

 

EETN-EKCH-EIDW-EGHI (non-stop)

 

 

Addons used:

 

* FTX England

* FTX Global

* FTX Global Vector

* FS Global Ultimate Europe/Africa

 

* Drzewiecki Design Tallinn X

* FlyTampa Copenhagen Kastrup International

* Aerosoft Mega Airport Dublin

* FTX Southampton Airport

 

* Aerosoft A319

* Ultimate Traffic 2 (65%/15%)

 

* REX 4 Texture Direct (1024 textures, dxt1/5, non-HDR textures. Everything installed)

* OpusFSI

 

No scenery was disabled.

 

No OOM, no warnings. I would say Prepar3d is pretty darn stable.

Well I managed to finally get a complete flight from KLAX to LSFO in my CS777 without an OOM after making a few changes.

 

I created a saved flight to bypass the scenario startup menu

Removed the .bgl files in question per Robs advice

Turned off FTX Hybrid mode

Turned off Global trees

Turned off Panel serialization in P3d

Turned off Air Traffic Manager and not just lower the settings

I lowered my overclock speed from 4.6 to 4.3

 

I did each step separately and rebooted between each test.

I will now turn on Air Traffic Manager and start off with minimal ai and see how that responds. 

 

 

Turned off Global trees

 

Oh hadn't thought about that one Nick, good suggestion.   But what's LSFO?

 

Cheers, Rob.

 

 

i just simply stated i havent had an oom since changing my pagefile,in the past i had no page file at all

 

For Windows OS you ALWAYS want a pagefile ...personally I've always let the OS manage it as whenever I change that setting I seem to run into issues ... not P3D related but other applications.

 

Cheers, Rob.

 

 

No OOM, no warnings. I would say Prepar3d is pretty darn stable.

 

That sounds very good. What is your LOD setting?

 

I also completed a flight today from Flightbeam KPHX to LatinVFRs KSAN. No OOM, no warning.

That sounds very good. What is your LOD setting?

 

I also completed a flight today from Flightbeam KPHX to LatinVFRs KSAN. No OOM, no warning.

 

I haven't touched the LOD so it's set at the default (LOD_RADIUS=6.500000)

Sorry LSFO should have been KSFO.

Wow, OK so my SSD just went south. That's two of them now, and so I am pretty much done with using SSDs - a topic for another thread, no doubt.

 

The good news is the only thing I had on my SSD was P3D and the P3D SDK. The bad news is that I just lost my whole P3D installation.

 

<sigh>

 

That's OK, I will do a full install from scratch (previously I had it patched) and just gradually add stuff back in. I'll just take my time to smell the virtual avgas along the way.

 

Still I am not able to see how my setup is any different than some of yours, but clearly there is something. I will find it.

 

Good info, regarding the pagefile -- I have mine set to 'Automatically manage paging file for all drives'. Anybody using anything else?

Wow, OK so my SSD just went south. That's two of them now, and so I am pretty much done with using SSDs

 

That's unfortunate because they really help ... you might want to investigate why you had two failures - not running any defragmentation on them are you?

 

I've got 7 SSDs (various brands from Intel, Samsung, OCZ) and they have worked flawlessly and perform extremely well (and I write huge files to them frequently with all my video work).  MTF for SSD is 1-1.5 million hours (that's higher than most mechanical hard drives).  For example. even the older technology SSDs from Intel say you can do 5GB worth of writes every day for 5 years straight before you'd start to see errors - more recent SSDs are considerably higher.

 

I would look elsewhere (motherboard, virus, BIOS, power supply) as the source of your SSD failures.

 

Cheers, Rob.

 

 

One thought that I have had long before this is that it might be more interesting and fun to just set up the actual approaches to airport X in P3D than to continue to wrestle with making the whole flight. I admit it is a bit of a leap to assume that even THAT will be possible in P3D, in some of the more sophisticated aircraft, but it is something that I am looking into.

 

@Ripcord. This might be what you are looking for.

 

 

Right now, I would say that effective virtual storage allocation and reclamation would be a better investment than going to 64 bit. When your plane leaves that airport, why hang on to all that stored data that you last used 30 minutes ago?

 

And that seems, from my early experiences, to be precisely what has been done with FSX-SE.

 

 

And that seems, from my early experiences, to be precisely what has been done with FSX-SE

 

P3D will release the 3rd party airport resources also ... not sure why you would think otherwise? 

 

Cheers, Rob.

P3D will release the 3rd party airport resources also ... not sure why you would think otherwise?

 

I'm assuming that when you say 'will', you are referring to a future release? It doesn't appear to happen with P3D at the moment.