Shadows for clouds, terrain, buildings or vegetation, and also water settings too high will give you OOM`s in P3d if your using high end aircraft, as others have mentioned you need to bring the sliders down, as frustrating as it may seem you need to strike a balance for your system, and its way better than FSX.

 

Rick

I have nerved everything down after my transition to P3D. Heck, I'm even running lower settings than in FSX:SE. Everyone is talking about improved VAS usage in P3D 2.5 - well, not for me either.

You wrote that you can't finish single flight without an error.

 

So solution is simple - tune down every settings and then check if you get en error. If not, you can slowly tune it up.

 

I suspect that the problem may lay somewhere in Orbx scenery. I've read that it is VAS heavy and you've written you installed it all for North America.

 

Blaming P3D for every error is like blaming Microsoft Windows for a every software that crashes on it.

 

Lukasz

My suggestion to everyone wanting to try any new sim is to try it with the defaults first. Then add things slowly and test.

 

I get the impression, folks install P3D, install all their addons, whack all the sliders up to max and then complain it's a stuttering OOM riddled mess and uninstall it.

 

Play with it. Treat it like you used to treat FSX - with kid gloves. Tease new addons on and give them a thorough test. If the sim platform fails, get onto the addon provider for an update.

 

P3D is not FSX with all bugs fixed.

 

P3D is FSX with some better eye candy and some (major!) bugs fixed. LM have almost certainly introduced new bugs in the process, but that's inevitable with complex software. Treat her gently. She's an old girl with some better makeup not a 20 something nubile supermodel.

P3D is FSX with some better eye candy and some (major!) bugs fixed. LM have almost certainly introduced new bugs in the process, but that's inevitable with complex software. Treat her gently. She's an old girl with some better makeup not a 20 something nubile supermodel.

 

THIS +1

The only way to test for shut down/ CTD reasons is to un-install or disable any addons apart from aircraft (but don't load them until you've tested defaults), save your current p3d.cfg by renaming it as a back up and let P3d build a new one when it starts up. Then begin with all the sliders low, no AI and no fancy stuff like cockpit shadows or HDR etc. Run a default aircraft for a while at different scenery locations. Then gradually turn up the detail bit by bit. If still no crashes install one addon (weather/scenery etc) and try it, followed by others.

 

Sounds a pain but in the end it's quicker than taking a stab at what it might be. It also gives youo useful clues later on for the best settings/performance combinations.

So where P3D is actually better than FSX, if all extra features like shadows etc. must be either off or set for min. ?

Also VAS is not managed in significantly better way as i can read.

So what is real advantage of P3D ?

 

( i am still holding myself to jump into P3D )

I am becoming one frustrated simmer with P3D now... I can not complete a single flight with out ether P3D stopped responding error or some odd OOM error.  never had these in FSX.

 

Only you can really decide whether you are better off with P3D2, or whether you were better off with FSX.

 

What I can say is that my experience (2 weeks ago) sounded very similar to yours. I really wanted to make the (permanent) move to P3D2.5 but I also suffered constant CTDs with P3D.  When it worked, it was perhaps worth the move. But after 5 continuous flights in Orbx regions, with a light Carenado aircraft, and getting CTDs on every one of them, the scales were tipped.    I moved back to FSX and have been flying very happily ever since.   If I had not been experiencing the CTDs I may have stuck with P3D as the visuals were stunning.

 

Even then though, there were other considerations for me, such as :-

 

• being unable to use Reality XP gauges (which I value highly) in P3D.
• owning the FSX version of the F1 GTN gauges and being personally unwilling to pay for them again (at a higher price) for P3D.
• owning the PMDG NGX and 777 for FSX and being personally unwilling to pay for them again for P3D.
• owning one or two other addons that I value highly, that are not compatible with P3D.

In the end I think, even without the constant CTDs in P3D2, I doubt I would have stuck with it due to the above factors.   I also don't enjoy maintaining 2 platforms and dismissed using them side-by-side, even if the CTDs had not been a problem.

 

Your mileage and preference criteria may vary.

I have not flown in any ORBX regions todate, so I can't comment.  However, my PMDG flights were all smooth, no OOM no crash.  Did you share your CTD details on the CTD forum?  Also did you enable or disable tessellation?  If you disable it you will never able to complete a flight in ORBX region without encounter the R605 crash.  There are plenty of people who use P3Dv2 with ORBX without any problem, some keep running into issue.  My advice is same as Robert above, deactivate all your add-on sceneries, fly your aircraft if the CTD is gone, then chase after the add-on maker.  Every single add-on that I install nowaday is subject to this test, if the add-on cause problem, out it goes.  You also need to get update for your add-on that stated to be working in P3D as well.  It really depends on what you are after, if you are happy with FSX, stay with it.  If you want the update visuals and a continuously supported platform go with P3D, but be prepare to pay some money.  Good luck.

P3D requires very little tweaking if any at all.  That is the beauty of it.  You don't have to add a list a mile long into your CFG file to get the results you want.   It's really just settings management based on the aircraft you are flying.  It is why P3D (and even FSX) allow you to create multiple settings profile.   Make one for each of your airplanes you fly the most frequently and manage your settings for each.   Keep in mind as stated  above that the slider settings in P3D DO NOT equal the same settings in FSX.  P3D settings are more intense than FSX is at the same slider level.    The LOD slider for example at max is 6.5 where FSX is only 4.5 and the 6.5 is not the same as FSX manually set 6.5.    You do not need 4096 textures turned on.   This will destroy your VAS.  2048 is more than enough for the human eye and most payware airports are done in this resolution or less.  You can even get away with 1024 in most cases (this especially goes for your Clouds if you use REX HD).    Beware of Terrain Tessellation.   Ramming that slider all the way to the right adds a bajillion extra vertex points and polygons on your terrain.   Yeah it looks great up close over the Rocky mountains but a majority of the Earth will show little change between MAX and Low/Medium.   Less polys, less work for the graphics card and less drain on the VAS.    Don't RAM the AI slider to 100%.   Every AI plane eats a little bit more of your VAS lunch.   I run at 50% and use the AI Traffic Manager to ditch the planes I never see.  It's a waste of memory and FPS to have 500 planes in the area.    

 

I have NEVER OOM'd in P3D.  I did all the time in FSX which is why I dropped it like a hot potato and made the switch to P3D.   I fly PMDG 777/737, a slew of Aerosoft and Carenado aircraft.   I run with FTX Global, ASN with Maximum cloud coverage and 8 layers of clouds.   I never stutter.  I never get blurries.   P3D is my sim Heaven (although I would REALLY like to have my beautiful clouds back LM.  Thanks! *broke patch face*).

 

You must find the balance in the Force young Skywalker.   May the SIM be with you, always.

I recently made the same switch. 

 

First day i got frustrated and uninstalled it

 

After some testing and tweaking (not true P3D doesn't need that imho, you have actually  to adapt it to your system) now P3D is so better than FSX that i've never ran FSX again... and i think the times i will do that will be rare also in the future.

 

Just invest sometime to adjust settings, CFG and your hardware and you will not regret it.

 

I would try these things:

1) format you HD and go for a fresh/clean OS installation

2) optimize your system with guides that can be easily found on the web around (i used NICKN one)

3) Try P3D "ultimate settings" or Rob's ones

Try different aircraft of different producers and be sure to use latest updates, same as the scenery. And do not throw too many scenery in in the same time.

If not satisfied with perfomance try reduce the settings and/or applying the following in CFG:

FFTF: many use 0.01

AlwaysFullLoad=1 to avoid OOM

UseGlobalView=True

TBM=120

UsePools=0

Optimize Parts=1

Swap timeout=30

Affinity mask (a lot to read and learn very system specific)

 

In general a tweaked P3d vs tweaked FSX seems more smooth to me even with the same FPS and similar graphics settings (no shadows etc) + FSX shaders are really awfull and it feels really "flat" (not 3d) to me + FSX is always the same while P3d is (slowly) evolving.

I use simstarter to manage my configurations flight by flight:

 

1) I have a profile setup for each of the areas that I fly in...for instance

Texas profile: has my flightbeam KAUS , FSDreamTeam KIAH and KDFW and Xtreme Cities X - USA SouthCentral along with Orbx global and vector

 

If for the current flight, I'm going KAUS to KIAH via a tubeliner, then I disable KDFW and Xtreme cities, as I don't need GA type scenery, or that additional airport taking up VAS.

If I'm flying the same flight at FL120 or lower, then I leave Xtreme Cities enabled for GA visuals.

 

2) flight by flight, I disable in the dll.xml, all addon dlls that I'm not using....i.e. If I'm not flying PMDG, I turn off those dlls...same with captain sim, aerosoft etc.... I only leave the dlls that will be used...FSUIPC, add-on manager, coautl etc.

 

Anything you can do to reduce load on your pc, gpu and VAS usage is worth the while when the result is a smooth sim experience...

p3d sucks in the VAS management department. LM has all this resource and cant fix the VAS usage which is better in FSX SE. I dont know how some of these guys are not getting oom with these high settings when others with moderate to low settings are having problems  :rolleyes:

 

I recently did a flight from Aerosoft eham to FB KIAD with the pmdg 777. Moderate settings and I had to save and restart twice to avoid running oom. I'm using ftx global, asn, rex4, open lc eu and ftx vector.

 

I just watched rob's latest video and looking at his settings, there is no way anyone can use those settings with the pmdg 777 and not run oom with addon airports

p3d sucks in the VAS management department. LM has all this resource and cant fix the VAS usage which is better in FSX SE. I dont know how some of these guys are not getting oom with these high settings when others with moderate to low settings are having problems  :rolleyes:

 

I recently did a flight from Aerosoft eham to FB KIAD with the pmdg 777. Moderate settings and I had to save and restart twice to avoid running oom. I'm using ftx global, asn, rex4, open lc eu and ftx vector.

 

I just watched rob's latest video and looking at his settings, there is no way anyone can use those settings with the pmdg 777 and not run oom with addon airports

Well Rob did.  I don't know what you use in term of low level metrics to state that P3D sucks in VAS management?  Are you sure you are comparing the same thing.  The releasing of memory used by scenery (the claim to fame by FSX-SE) is there in P3D.  Did you enable everything under the sun in Vector?  Why would you need Open LC EU if you use the PMDG 777?  Until P3D have 64 bit support, so amount of clever VAS management technique is going to help you if you don't turn down settings.  P3D may sucks in your environment, but making a general statement without the evidences to really prove it is just qualitative, "me thinkish" to me.  I did a number of flight with the PMDG 777, HD texture livery, between CYUL and Aerosoft airport LFPG, also use vector, Rex4, FSGRW, FTXglobal and I always landed with 1 GB of VAS remaining.   My P3D setting is mid-range, so you see, no problem at all for me.

Well Rob did. I don't know what you use in term of low level metrics to state that P3D sucks in VAS management? Are you sure you are comparing the same thing. The releasing of memory used by scenery (the claim to fame by FSX-SE) is there in P3D. Did you enable everything under the sun in Vector? Why would you need Open LC EU if you use the PMDG 777? Until P3D have 64 bit support, so amount of clever VAS management technique is going to help you if you don't turn down settings. P3D may sucks in your environment, but making a general statement without the evidences to really prove it is just qualitative, "me thinkish" to me. I did a number of flight with the PMDG 777, HD texture livery, between CYUL and Aerosoft airport LFPG, also use vector, Rex4, FSGRW, FTXglobal and I always landed with 1 GB of VAS remaining. My P3D setting is mid-range, so you see, no problem at all for me.

either some of you guys are lying about setting or something else is going on. P3d does not release VAS. I monitor my VAS with process Explorer and I watch my VAS increase or stay the same. Open lc is something I purchased so I use it. I'm not going not use an addon just because and have to jump through hoops just to complete a flight. They work fine in fsx se so I thought they would be fine in p3d. My vector settings are exactly like the settings rob posted.

 

Now I don't know if you are using FlyTampa cyul or default but if it is FlyTampa cyul there is no way you can arrive at cyul with 1 gig of VAS from Aerosoft LFPG with the pmdg 777. It's impossible unless settings are all the way left. I have every ft airport and cyul, ekch and cyyz are the heaviest VAS users. If I start my flight with the 777 at cyul and look around in spot view my VAS immediately goes to about 3.5

 

Maybe rob knows something that we don't but there is no way him are anyone can complete a flight in the pmdg 777 with his settings using the addons he is using unless they are saving and restarting