Aagh, Sean, that's the bit I slipped up on. Ran test with all 4 sticks in. Drat! Okay, will try that tomorrow.

 

But, as you are a far more experienced simmer than I am as I've followed your posts wherein you do use top-level sceneries, can you then shed some light on this then?

 

As I was getting those OOMs at UK2000's Heathrow Xtreme v3, I decided to try the same aircraft loaded with ASN this time, from TropicalSim's SAEZ to TropicalSim's SBGR. Distance of around 946m, approx 2 hour flight, and landed with not an iota of OOM. So, is it EGLL that is eating up VAS?

EGLL and London scenery (autogen) around it. P3D isn't going to handle that very well. Especially if you throw an NGX on top of that. Unless you turn all the eye candy off, and even then it seems to be hit or miss. 

 

I'm really not trying to turn this into a Xplane thread, but that is what I love about that platform. Throw stuff at it like that as long as you have the hardware to handle it..just like the old days

No fear, Rich. You are not turning this into an X-Plane thread. On the contrary, you offer me another escape route. Thanks.

Aagh, Sean, that's the bit I slipped up on. Ran test with all 4 sticks in. Drat! Okay, will try that tomorrow.

Rick, yeah you have to test each stick separately. It will take some time, but that's what you have to do. Also, you'll have to refer to your mobo owner manual, but when you test each stick, you need to have it plugged into which ever DIMM slot that you would use if you were only running one stick of RAM. On some boards is DIMM 2 and some it's DIMM 1. If I recall when I had to test it was DIMM 2 for my Asus board. Btw, when I first ran Memtest with all sticks installed there error never occcured. It wasn't until I tested each one on it own. Also, if you get an error on one, don't stop there, test all of them to be sure the others aren't throwing errors as well.

 

But, as you are a far more experienced simmer than I am as I've followed your posts wherein you do use top-level sceneries, can you then shed some light on this then?

 

As I was getting those OOMs at UK2000's Heathrow Xtreme v3, I decided to try the same aircraft loaded with ASN this time, from TropicalSim's SAEZ to TropicalSim's SBGR. Distance of around 946m, approx 2 hour flight, and landed with not an iota of OOM. So, is it EGLL that is eating up VAS?

Well Rick, as you've probably read in the past from me, the key to running all these big sceneries and not getting OOM'S, even back when I was running Win XP 32 bit, was to never use any scenery, cloud, aircraft, water or any other misc texture larger than 1024. Of course that meant spending hours through the last 7 years resizing addon scenery textures that developers include in their sceneries that are larger than 1024 and/or 32 bit compression. Everything I have installed is 1024 or smaller, mip mapped when appropriate, DTX5 DXT3 or DTX1, except envmap textures which need to be 32 bit. Just setting your TML to 1024 in the cfg isn't enough since the larger mips of 2048 or 4096 texture will still load into the memory, but won't be rendered. I also don't use any extended LOD settings, mip map all my AI, user aircraft, and resize external user aircraft textures to 1024.

 

Aside from that, I have no other tricks, but it's served me well the last 7 years cause I have none of the memory issues that we read about all the time on Avsim and elsewhere regarding FSX or P3D.

 

Oh, a few other things as well, but you probably already know. If you use photo sceneries, don't keep them all active in the scenery.cfg when you not flying in them and if you use ORBX regions and fly complex aircraft than consume lots of memory, don't use the regions when flying those plane into those areas.

 

Hope this helps, but you'll have to remember that I never got on the P3D train yet, but a lot of this should apply anyway.

Has anyone had VAS OOM while still on the ground?

 

Yes, many times with 3rd party airports and complex aircraft.  I can OOM just about anywhere with enough 3rd party content active.

 

But these threads about OOMs do baffle me ... why would anyone point the finger at LM when the source of OOMs is from the multitude of 3rd party products that have been added?  Shouldn't you start with the 3rd party provider first and let them figure it out and/or have them work with LM?

 

I challenge anyone to OOM a base v2.5 with no add-ons ... I've tried many many times and I can't.  In every single case I had to add 3rd party content to get an OOM.  When a single 3rd party airport can consume 1.8 GB of VAS and then a single aircraft consumes another 1GB of VAS ... then add 3rd party AI traffic consumes another 400MB of VAS ... so where exactly is the "main simulator" supposed to fit when 3.2 GB of VAS is consume before even starting to taxi?  Does anyone really think LM can squeeze the entire core P3D product in 800MB?

 

I recently ran into constant OOMs at Copenhagen until I found one tiny 4K file that was the source ... and guess what, I can't replicate the OOM in a base v2.5 install using the same airport.  Obviously there is some conflict in my main sim between the many 3rd party products I have installed that was consuming VAS at a rate of 400MB every few seconds ... even a 64bit product will NOT solve that issue, it would only extend the OOM message a few minutes or so.

 

 

 

Another thing that puzzled me was why did the 3 TropicalSIm airports I bought 2days ago all install themselves in the Windows root directory? Very odd.

 

This should be a RED FLAG and definitely needs to be investigated.

 

Bad RAM will not cause OOM .. Bad RAM will simple freeze the computer or trigger a BSOD or worst case is corrupt your OS registry (this is when you need to do a complete OS re-install).

 

The error message you got during warm boot can be many things, but the first thing you should do is:

1.  Update the BIOS to latest version

2.  Disable an features you don't use via the BIOS (i.e. onboard WiFi and extra LAN ports onboard Audio if you have another sound card/device)

 

But by all means try XP10 ... it's good to keep one's eyes and ears open but ultimately any flight simulation product will be a game of compromises, you just have to decide what you can and can't compromise.  There are many people that have bounced from one sim to another sim and then another and eventually walk away from flight simulations completely ... and I honestly don't blame them, some come back a few years later, it's a pretty common pattern.

 

Like I've said before, I've asked LM if they can provide some diagnostic tools that can help end users and 3rd party determine the actual source of the OOM.  Without identification it's all just guess work.  I can only hope LM understand how important it is to get diagnostic tools that can pin-point OOM problems ... and it doesn't matter if it's 32bit or 64bit base ... such tools would be useful.

 

Cheers, Rob.

Hi Sean and Rob

 

Many, many thanks to you both for taking the time to post such detailed replies to my issues.

 

Sean, I have sent you a PM.

 

Rob, some very good wake-up-and-smell-the-coffee points there, and valid too. I should not be blaming LM nor did I seek to do so.

1. Update the BIOS to latest version

2. Disable an features you don't use via the BIOS (i.e. onboard WiFi and extra LAN ports onboard Audio if you have another sound card/device)

 

I have an Asus Z-87A De Luxe mobo. The BIOS has been updated via its in-built BIOS Update, and everything in bullet 2 has been de-activated.

 

What puzzled me was that I had, in the Scenery Library, de-activated all the 3rd party add-ons except for the UK2000 and the Orbx libraries, and the defaults, but still got the OOM sat on the ground at UK2000's Heathrow Xtreme3, and yet same aircraft this time loaded with ASN+AivlaSoft's EFB, I get nothing on the TropicalSim's SAEZ-SBGR. Yet Gary Simmons at UK2000 states that Heathrow Xtreme3 has no known issues, yet that is the only airport I'm getting OOMs just merely sat on the ground?

 

Head-scratching-go-back-to-the-drawing-board time.

@vc10man

 

This was a big big problem with FSX  .....

 

If you start at a complex area such as EGLL .. FSX would fully draw all the 5 main London airports namely ..London Gatwick ... London City .... Luton .... Stansted and Heathrow  ...

 

If you are using enhanced airports for all 5 .... a traffic program .... complex aircraft ... Rex or Active Sky ... Orbx or VFR scenery ... and the very fact you are almost on top of the city of London you are bound to run into problems and have the VAS sucked from your system!!

 

I can only think that with P3D it is a legacy that has been passed on!!

 

Paul 

Hi Paul

 

Only have Heathrow, no London City, no Gatwick, no Stansted. Was not using any weather engine. Plain vanilla P3D. Only had Orbx's EU:England active. Would it then be a conflict between Orbx's EU;England and UK2000 that was 'sucking the VAS out of my system'?

It happens for the reasons I stated I think, Rick. EGLL is sitting right in the middle of a big city.

 

I dont see anyone pointing fingers at LM in this thread, but I know what you mean Rob. It obviously isn't their fault, just I hope they will be the ones to fix it one way or another - 64 bit.

 

The post about resizing textures and turning everything off is exactly why I called the state we are in with this platform pathetic in an earlier post. P3D out of the box isn't bad, but it is nowhere near where developers such as Orbx have made it. However, to use those add-ons we have to turn them off, or drastically resize them so they dont eat memory - and don't look so good either. I don't feel like paying for all the orbx stuff and aircraft like the NGX only to have to spend all my time resizing textures or removing everything I just paid for. 

@vc10man

 

Try this exercise ...

 

Set yourself up at EGLL .. running everything as you normally do ... BUT put yourself in one of the default P3D aircraft such as the Beechcraft Baron 58

 

Take off from EGLL ... do a few circuits around the airport ... go for a spin around London .... make your way back to EGLL ... do a few circuits .... land .. taxi .... and I reckon you'll make it without any OOM's  !!

 

Paul 

 

 

I dont see anyone pointing fingers at LM in this thread, but I know what you mean Rob. It obviously isn't their fault, just I hope they will be the ones to fix it one way or another - 64 bit.



The post about resizing textures and turning everything off is exactly why I called the state we are in with this platform pathetic in an earlier post. P3D out of the box isn't bad, but it is nowhere near where developers such as Orbx have made it. However, to use those add-ons we have to turn them off, or drastically resize them so they dont eat memory - and don't look so good either. I don't feel like paying for all the orbx stuff and aircraft like the NGX only to have to spend all my time resizing textures or removing everything I just paid for.

Spot-on, Rich. Specially your last two lines.

 

You must be a mind-reader, Paul, because that was precisely going to be my next tack.

Okay, did a test at EGLL as suggested by Paul.

 

Airport: UK2000 Heathrow Xtreme v3

Aircraft: P3D's Mooney

Weather: no engine, daytime flight

Other add-ons: nil

 

RESULTS:

• Using the P3D default Mooney, short circuit around EGLL, landed with 972Mb VAS free
• Shut down P3D. re-started
• Loaded Aerosoft's A319---on Rwy 09R------just about made climb-out to 2000' AGL before OOM crash

 

Is this maddening or what? I leave observations/comments to others.

Well .... it looks like you have found the culprit!!

 

With all of these things it's process of elimination

 

An unusable aircraft with your present settings I am afraid 

Going to try that 'experiment' with Just Flight's Fokker F27 and see if I get the same. Can't believe an Airbus+EGLL cannot do the 'dance' together.

 

 

Rob, some very good wake-up-and-smell-the-coffee points there, and valid too.

 

Sorry, wasn't trying to come across that way ... I can understand many people's frustration with OOM, we all want to add the stuff we buy from 3rd party and just keep adding it, it's natural process.  Unfortunately 3rd party's quest for the best to make us visually happy results in the 3rd party shuffle ... disable some, enable others, but never all at once.

 

 

 

I dont see anyone pointing fingers at LM in this thread, but I know what you mean Rob.

 

We don't really know who's at fault (and I honestly don't care so long as whatever "it" is gets resolved), but given no-adds = no OOMs.  Hence my quest for tools to find out what's the source of the problem.  A good example of just how difficult it is to determine the cause ... here is a test I performed:

 

Test 1

Base P3D v2.5 

Added Aerosoft's Antartica X

Fly over a specific coordinate

Results: No OOM

 

Test 2

Base P3D v2.5

Added Orbx FTX Global, Vector, PILOT's Mesh

Fly over a specific coordinate

Results: No OOM

 

Test 3 

Base P3D v2.5

Added Orbx FTX Global, Vector, PILOT's Mesh, Aerosoft Antartica

Fly over a specific coordinate

Results: OOM

 

Is it Orbx, is it Aerosoft, is it LM?  Who knows ... yes it's pretty frustrating.  The only "Work-arounds" I've come up with is hammer and sledge approach by disabling BGL's until the problem doesn't happen (tedious) and then it does really mean the "offending" BGL is really "at fault" as it's the "combination" of 3rd party products that causes the issue.

 

Do I like messing around spending countless hours trying to resolve or emulate so LM can emulate?  No, I don't ... I really do have better things to do with my time.  I can toss my hands up and walk away, but that isn't going to get me what want.  I use XP10, DCS, and others, but the product I keep coming back to is P3D.

 

Cheers, Rob.