Rob,

 

I said it before and I'll say it again. I really appreciate all your efforts. I only get a very short amount of time to 'fly' so I really haven't (right now) got the time to be disabling BGL's or scenery or this or that. I truly appreciate folks like you that still find the time somehow, and therefore make our lives better. I know we'll never be happy with our sim, we are born to mess with it. Years ago I spent so much time tweaking stuff I never got to fly. Now I just want to fly in my limited time and not tweak quite so much. One thing I did like about XP is that I threw a whole bunch of crap at it and it hasn't crashed once. I just jump in and fly.

 

Again, I truly appreciate your efforts with P3D. I am vocal about it because I really do think LM have made something worthwhile with P3D. I can see the future of FS with it, but like many others, I'm frustrated we are stuck with 32 bit. We are always going to be chasing our tails unless we move on. We are always going to be minutes from an OOM, and we will never have all the eye candy that developers are capable of.

 

Rich.

@Rob

 

Hi Rob .. I don't think we have spoken before but 'Hello to you from the UK'

 

These tools you are talking about .... do they exist and if so are they available to third party developers such as PMDG, Aerosoft, ORBX etc etc

 

If so ... and I do realise that the combinations of software are limitless .. but surely they could put a few sets of very popular software packages together and test things to see if they can create OOMs and then come to a conclusion of whose software is causing the issues?

 

As I say .. it's a huge task to take on what with the amount of settings the end user can fiddle with in P3D .. but maybe there is a way of coming to a compromise

 

Paul 

These tools you are talking about .... do they exist

 

No, I've begged for them ... it may or may not happen.

 

 

 

but surely they could put a few sets of very popular software packages together and test things to see if they can create OOMs

 

That's not really LM's job, but they have done that to some degree (acquired 3rd party products) and sadly can't replicate OOMs ... but there are millions of possibilities, LM trying to hunt down the right combination of events to cause the issues could take months or it could never happen.

 

If you think about all the 1000's of 3rd party vendors and then add the numerous updates from 3rd party vendors (which LM would have to also apply), the possible combination is simply mind boggling.  Now, add 3rd party installer errors message (like Orbx installs will produce a Terrain.cfg error which one must hit "Continue" button to proceed and then re-apply latest Orbx libraries) ... just getting 3rd party products installed "correctly" in P3D v2.5 has been a big challenge since the relocation of some key .cfg files.

 

PILOT's came up with a very good solution where the Installer itself will check for an installer update and load the new installer that will deal with the changes in P3D V2.5. 

 

Point being, even with "common" popular 3rd party products there is still a rather lengthy and in some cases cumbersome install process ... LM could spend the rest of time testing out every single one of these products and combination of products.  It's not really their job to test other 3rd party installers/products, if 3rd party have issues with P3D V2.5 they either need to adapt/correct (or not) and/or try to work something out with LM.  3rd party are obviously NOT going to be too happy about having to change installers for P3D ... but good solutions do exists, PILOT's installer is an example of that.

 

P3D is an evolving platform, so 3rd party will need to build in some flexibility to work with that evolution IF they want to continue to provide products for P3D users.

 

Cheers, Rob.

A great reply Rob and let's hope LM come up with the goods

 

When I said about putting some popular software packages together I meant this would be for the third party developers to get together and thrash out ....  not LM ...

 

Surely it would make sense for them to try to get to the bottom of this because .... as we all know ... the way forward for Flight Simulation is indeed Prepar3D!!

Hi Rob

 

Like both Rich, and Paul, have stated, we all admire your input into this issue that takes away so much of the fun from this hobby. And you do make a very apt point of us trying to do  the 'shuffle' with 3rd party add-ons quite never ever gets us on that 'dance floor' where we all move in unison, i.e. a sim platform in parity with what we can throw at it.

 

Like your experiments, besides the results I discovered using Paul's suggestions earlier, likewise I went a stage further.

 

• Sim=P3D v2.5
• Aircraft=PMDG's 777-300ER latest revison
• Scenery=TropicalSIm's SBGR-SAEZ
• Weather Engine=ASN Active
• Flight Planner=PFPX

And not a single inkling of OOM as I successfully landed the flight.

 

So, either the Aerosoft Airbus X does not like UK2000's Heathrow Xtreme, or the autogen, or mesh or whatever that makes up a complex scenery add-on, is far too much for the sim to handle. Have no idea.

 Have no idea.

And that is the problem in a nutshell, Rick. The 3PD and LM are in the same boat. Unfortunately it's almost on an individual case basis. One size DOESN'T fit all here.

 

Vic

Lets hope we (3rd party and end users) get some tools from LM so we can stop guessing (or resort to brute force work-arounds).  I know if these tools ever do come to surface, it'll take time to code them so I don't have any expectations of near future availability.  If we're lucky maybe something that gets bundled into V3 ... and this is entirely my speculation.

 

Cheers, Rob.

vc10man

 

Try EGLL with all the same settings as with the Airbus BUT use the PMDG 777 instead

 

Just placing my bet at the bookies now  hahaha  

 

Paul

Probably late to the party but I run UK2000 extreme (EGLL) and very early on I had to load the airport with its lowest settings otherwise I'd OOM on the ground using the NGX. It still won't play with ORBX EU and the NGX. those three in combination guarantee an OOM on the ground for me. If I want to fly out of EGLL in the NGX I have to turn off ORBX EU and use lower settings.

Hmmmm ... very interesting Darkstar

 

Well there you go .... in the space of a few hours we have whittled (no pun there!!) it down to a few possible culprits

 

Surely ORBX ... PMDG ... Gary Summons .... and  Aerosoft should swap notes and play together in sorting this out!!

 

Come on guys .....

 

Instead of calling it the G7 ... let's call it the  G4   .....

vc10man

 

Try EGLL with all the same settings as with the Airbus BUT use the PMDG 777 instead

 

Just placing my bet at the bookies now  hahaha  

 

Paul

Once again, Paul, you read my mind. Bit too late to try that now, but that was my next plan. Will do so tomorrow and report. I feel teh more 'experiments' we as a community conduct and share around, with the coding experts we have in this fraternity, ala Rob, and maybe LM, we may yet just be on the trail of that dreaded ogre that haunts us, OOM.

Paul

 

Guess what? Just out of eager curiosity, loaded the PMDG 777-300Er at EGLL, with Button Version FS2Crew. No other add-on. Now, the FS2Crew Pre-Events has a counter set for 55 mins countdown Before Start Procedures. Sadly, before I'd even gone past 2 minutes elapsed, that dreaded sceptre of OOM kicked. That in itself is a record, for me, at least. At least with the Aerosoft AirbusX, I got to 28 minutes.

 

At this juncture, I just throw my hands up in exasperation!

Guess what? Just out of eager curiosity, loaded the PMDG 777-300Er at EGLL, with Button Version FS2Crew.

 

Did you post the 5 key graphics settings screens in P3D ... or did I miss it?

 

Things that will consume your VAS and suggestions:

 

1.  Running HD textures at airports (> 1024) select NON-HD textures

2.  P3D Max Texture setting (stick to 1024 which doesn't control ALL textures, only some)

3.  Disable features from 3rd party airport configuration app (if available)

4.  Keep building autogen at Normal

5.  Keep scenery complexity at Very Dense or less

6.  Keep tree autogen at very dense or less

7.  You will not be able to use an Orbx region if you have a very complex 3rd party airport

8.  Keep tessellation ON

9.  Keep AI traffic 20% or less, no ship or boat traffic

10.  Keep road traffic 14% or less

11.  Check your DLL.XML and EXE.XML ... disable anything you don't need for your flight

12.  Do NOT set any real aircraft up as AI aircraft

13.  Use flight manager tool (freeware) to restrict the number of flights with 50nm radius (can save you up to about 400MB at heavy traffic airports)

14.  Use tools to check that you don't have multiple AFCADs for the airport (freeware tools)

15.  At complex scenery areas like EGLL, drop the level of detail down one notch

 

I don't have FS2Crew so can't give you any info how much VAS that product uses (my hunch would be not a lot unless they pre-load lots of sound files).

 

I believe their is a guide on AVSIM with the same or similar information as above, suggest you check it out and see if there is anything that might help you.

 

Cheers, Rob.

Did you post the 5 key graphics settings screens in P3D ... or did I miss it?

What 5 key graphics settings, Rob? Please elucidate and I'll have another shot at it tomorrow.

 

1. Do not run beyond 1024
2. Same again, set to 1024
3. Not sure about this
4. At the moment set to Dense, but will take heed here
5. Set to Dense
6. Set to Dense
7. Did not disable FTX EU:England, again will do
8. Is set to ON
9. Set to 30% using MT6, nil land, ships, boats sliders
10. No road traffic
11. No idea where to look for this
12. All AI aircraft is what MT6 sets
13. Do not have that tool
14. Again, no idea which tool to use here
15. Where's the setting for that?

Here's my screenshots

 

I know I am so tried  with OOM  also,  My question is how come FS:SE can fly PMDG777 / 737 with many add-ons,  with out any OOM.