It would be AF=15 to use all cores

Ah, thanks. I'm going to try that now.

AF=15 made textures run much quicker here. Now everything is crispy.

It would be AF=15 to use all cores

 

Thanks for the tip... I thought it was AF=14, but you are right. I just did a quick test and good just got better. Huge wow factor. Now the first core is maxed and the remaining three are about 60%, but it is smooth.

 

 

 

AF=15 made textures run much quicker here. Now everything is crispy.

 

Yes :dance:

 

 

So, AF=15 might help some people. Otherwise, I agree with the OP, P3D v2.2 is a great release that works without endless tweaking. (The only other tweak I add is to remove red text. LM should add this as a GUI option. It is not very realistic to train with red text reminding you of your aircraft's status).

Great thread...  In (P3D)  v2.1 changed my NV profil through NI to settings that I had read here that were helpful.  Now that I have v2.2 installed, I'm sure that same NV profile is being invoked.  How do I set it so that v2.2 works with no special (i.e. default) settings?  I'm not at my PC right now, so the answer may be obvious if I was in NI.

 

Thanks,  Bruce.

How do I set it so that v2.2 works with no special (i.e. default) settings?  I'm not at my PC right now, so the answer may be obvious if I was in NI.

 

Thanks,  Bruce.

 

In NI, once you bring up the Prepar3d profile, there is a button along the top that looks like the Nvidia symbol. If you hover your cursor over that it should say something along the lines of "Use Default Settings" or something similar. Press that and it should revert the Prepar3d profile to default, which is to use the Global Settings for all modifiers. Make sure you hit save just to be sure before closing NI.

 

I'm not at my PC either, otherwise I'd take a screengrab and post it up.

I hope someone is collecting a tweaks guide for P3D. 

 

 

World's shortest flight sim book: The P3d Tweaking Guide

 

Seriously, LM just did with P3d 2.2 is what LR did with XP10. Everything that you need to adjust is built into the user interface for the app. There is really no need to fiddle about with nVidia Inspector or the cfg files. Of course, if you like that kind of thing ...

World's shortest flight sim book: The P3d Tweaking Guide

 

Seriously, LM just did with P3d 2.2 is what LR did with XP10. Everything that you need to adjust is built into the user interface for the app. There is really no need to fiddle about with nVidia Inspector or the cfg files. Of course, if you like that kind of thing ...

 

I agree with the exception of super sampling for glass gauges. If/when they allow the SSAA switch to actually apply SSAA without the need to force it externally, then I'd not even bother profiling it in RP. 

 

Until then I will at minimum force it via RP. In a few VCs out there, some gauges are barely legible without it, if you are trying to read them at an angle. The Q400 CDU is one example.

I've done more testing. Dawn or DUsk + Cloud Shadow = 8 Fps here. When there's normal daylight, the fps goes back to 21. So this is the main issue LM should work on IMO. But even at 21, Cloud Shadow at BKN or OVC condition makes the sim Stutter a LOT here, it really looses all the smoothness, it's unflyable in my POV. Turning it off makes it butter smooth again.

LM is already working on it.  Here is the link:

http://www.prepar3d.com/forum-5/?mingleforumaction=viewtopic&t=6363

 

This is what Beau stated in regards to the issue:

We can can put some kind of sun angle check in the shaders or c++ and early out of cloud rendering into the shadow maps. The trick would be doing it without a glaring visual pop when the shadows turn on/off.

 

It is such a benefit to have a team dedicated to improving the platform and adding new features every release.

In NI, once you bring up the Prepar3d profile, there is a button along the top that looks like the Nvidia symbol. If you hover your cursor over that it should say something along the lines of "Use Default Settings" or something similar. Press that and it should revert the Prepar3d profile to default, which is to use the Global Settings for all modifiers. Make sure you hit save just to be sure before closing NI.

 

I'm not at my PC either, otherwise I'd take a screengrab and post it up.

Thanks, much appreciated.

I think the most important thing that needs to be realized by the community, is the two reasons we don't need "tweaks" anymore.

 

...

 

The future is bright!

I am amazed at the realism the cloud shadows impart! So much so I blew the Pilotedge I-3 test looking at the eye candy instead of my instruments...

 

Seriously...the best thing for P3d is Lockheed Martin's and our community storing data and variables for later review and discovery....in what appears to be a really cogently designed error, user database

 

Keep up the good work y'all.

 

C

 

 

Jeroen, sorry to say, but this is definitely not an aircraft which has a strong impact on performance. Totally different story with PMDG NGX or Aerosoft Airbus and the likes...

 

Runs on my 3 yr old PC 30.9FPS locked at 31  One of the planes you mentioned above. Please stop stating things you don't know.

Runs on my 3 yr old PC 30.9FPS locked at 31 One of the planes you mentioned above. Please stop stating things you don't know.

What kind of useless comment is this? Nobody said that you cannot get 30 fps with a complex aircraft. But a complex tubeliner definitely has a stronger negative impact on the sim's performance than the A2A Cessna. And believe me: You are not the only one who runs these airplanes in P3D2. So you should please stop spamming forums with useless comments (and yes, this comment is also useless, but I just had to answer... Sorry).

But what is with the tweaks described in the P3D v2.2 handbook? I guess that not all tweaks are already implemented in P3D v2.2

Spirit

It's interesting that you advise not to use tweaks, while myself and many others are now swearing by AF set to all logical cores to eliminate blurries and slow texture load. No other tweaks necessary and no NI in my case.

 

Your post made me look again and I think the 'mistake' I made was removing AF and changing the fps settings in P3D at the same time. I just did a longer flight with AF=15 again in the cfg and it does indeed seem to help with preventing some blurries. Fps is still stellar so the thing that really made the difference for me, compared to 2.1, was setting fps to unlimited and disabling Vsync (and triple buffering). Fps is around 45 average with the settings I posted in the OP (autogen still Extremely dense and terrain cast on!). It's really AMAZING!

 

One thing I noticed though: as soon as I enter a cloud, so there is mist all around me, fps drops to low 20's, even without any NI settings. I solved this by raising the altitude of the lowest cloud layer. ^_^ (I don't use a real weather engine right now: I rather set the weather I like myself! If I would buy ASN I would probably only use historic weather and so I'd still be picking the weather I want anyway, so well... that makes buying ASN a bit useless.)

 

All in all I am still happy and more and more amazed with 2.2!!! I mean, really... I am flying in the north of FTX NCA where there are LOTS of trees and I have autogen at Extremely dense: it looks absolutely awesome with all those cloud and terrain shadows and fps is still above 40...!!! I must be dreaming!!! It can't be true! But it is! :lol:

 

EDIT

I mean look at this! Look at ALL those trees! Look at those shadows! Look at the fps on my 3 year old 2500K and GTX580!!!

 

I mean look at this! Look at ALL those trees! Look at those shadows! Look at the fps on my 3 year old 2500K and GTX580!!!

 

So what we all need to do is flood the screenshot sub-forum with what we are seeing in P3Dv2 to make sure all the negative nancys have a reason to change their opinions.

 

Sure, we're bound to have people still complaining that the HDR is too dark, that it isn't as good as X-Plane 10 because 64-bit is FTW, etc. etc.

 

You never know what you'll find when taking a flight, as a test flight I was doing around Seattle of the P3Dv2 beta ended up as promotional shots that LM used when announcing the update.