Thank you for that quick rundown and settings to get you going in P3D v2

I’ve been having  hard time with the platform myself but never found the time to look deep into the issues,

 

I look at P3D as a work in progress and promising as it is;

the product is still very young and will take some time to fully mature

I think these are  birth pains that will disappear in the near future

With faster hardware and improvements from LM; we are looking at a very bright future

Richard,

 

I've just made the switch to Prepar3d V2 after reaching the end of my tether with FSX. Would you mind shedding some light on the NI Bioshock entry and what it entails?

 

All the best,

Found this on Bioshock

============================================================

 

The triple buffering setting provided by the Nvidia control panel is for OpenGL applications only. Bioshock 2, like almost every other modern 3D game, uses the DirectX code path as opposed to OpenGL. The laws of the DX API state that triple buffering shall not be forced via the drivers, but instead must be implemented by the application itself. For reasons that are unknown to everyone, most game developers do not enable triple buffering by default, although many of them do allow this via a console or configuration file. 

 

 

 

This is what makes D3DOverrider so useful. It is the only easy way to force a triple buffer when rendering DX games. 

 

Found this on Bioshock

============================================================

 

The triple buffering setting provided by the Nvidia control panel is for OpenGL applications only. Bioshock 2, like almost every other modern 3D game, uses the DirectX code path as opposed to OpenGL. The laws of the DX API state that triple buffering shall not be forced via the drivers, but instead must be implemented by the application itself. For reasons that are unknown to everyone, most game developers do not enable triple buffering by default, although many of them do allow this via a console or configuration file. 

 

 

 

This is what makes D3DOverrider so useful. It is the only easy way to force a triple buffer when rendering DX games. 

 

 

This was exellent, Richard, the missing ingredient in my soup!

My system is quite modest, and I'm walking on the contrary, AMD Phenom II X6 2.8 GHz, ATI 6950 2GB,  MOBO 990FXA-UD3 8GB.

Well the point is that using D3DOverrider, my simulator, FSX, P3D1.4, P3D V2 are smooth as butter.

I know the limitations of my equipment so I can not think of scenarios stunning third parties, but I can use good aircraft. a satisfactory manner.

Thanks for the info, it became my great Sunday.

 

João Alfredo

"This was exellent, Richard, the missing ingredient in my soup!"

 

Excellent news Joao - nice to have it working better - congrats

 

 

I tried 254 again and noticed panning in spot view it had a very slight hesitation so back to 84 for me Noel

 

It's so very hard to draw conclusions w/ universal application.  Heck, we've all had it happen where we were certain this particular discovery had this particular effect, only to discover in a different scenario something has materially changed about what you attributed a certain performance parameter, and how the setting isn't needed to accomplish the same thing.   I am describing a totally different scenario:  I run global texture maximum at 2048.  I run 2048-bit clouds.   I run all sliders inc tessellation and hard right except autogen & vegetation at Very High.  HDR on.  Scenery Detail at Extreme.   16x AF, after the toggle maneuver which I have empirically duplicated after reading about it, hence I always do it now.  Anyway, your empirical test didn't pan out, so YMMV is as I say almost always the case w/ this software.  I had great agreement between the theory and the empirical so that always lowers the level of uncertainty claim's applicability to more users.

I have turned on tessellation up to medium as I read that will put more work to the gpu I guess - and turning on water reflecions - no ill effects from it

 

"16x AF, after the toggle maneuver which I have empirically duplicated after reading about it, hence I always do it now."

 

What is the reaon for this ?

Well more to report raised my OC to 4.3 - 1.200v tried it all good - then I said hmmm is the Bojote tool website working and it was - ah lets try it and I have to report seems better P3D menus snappier - I checked my affinity mask to see if it was changed it was still at 84 - nice - ok had a few spikes panning spot view so I turned on v-sync and triple buffering and has seemed to resolve so this might be a nice thing to try - more to come but at first glance I give it a thumbs up - thanks Bojote

 

By the way aircraft look way better AWESOME in fact in P3D - DAY & NIGHT Folks

 

And the anti aliasing is incredible - superb

 

If you don't believe me look at this shot

 

http://forum.avsim.net/topic/443571-axe-p3d-style/#entry3001038

"16x AF, after the toggle maneuver which I have empirically duplicated after reading about it, hence I always do it now."

 

What is the reaon for this ?

 

If by reason you are looking for the theoretical explanation for why it's the case, that I don't quite follow.   It's acting as if when P3D initializes the existing 16x AF setting is not applied.   What I read and confirmed myself is that when I load P3D and the in-sim display setting indicates I have previously selected 16x AF, I can visually verify 16x AF has not yet been applied to the video output when the flight finally initializes.  I have to go back into display settings in-sim, change to presumably anything except 16x, and click apply or OK to have the flight continue.   However this will now display the other AF value you just selected.  Now go back and choose 16x and hit OK.  Now 16x has truly been applied.  It's easiest to see this as you are looking down runway or taxiway lines--much sharper much farther out.

 

 

Now go back and choose 16x and hit OK.  Now 16x has truly been applied.

 

I've reported this to LM and Wes indicated it's on the to be fixed list.  FYI, if you force AF 16X via nVidia Inspector, you do NOT have to do the "bug work around" to get AF 16X.

 

Cheers, Rob.

........

==========================================================================================================

 

9. This is important for all of this to work Windows AERO MUST be turned on as P3D is designed to to work with it on from what I have read and it certainly made a huge difference when it was on - no tearing or stutters

 

==========================================================================================================

................

Hi Rich,

not relevant for Windows 8 and 8.1, isn't it?

Spirit

.......

If you're seeing what I see, you'll have better results w/ it, and I have no impact from it.  I use it w/ SUPERVCAA_64x_4x + 2XSGSS to greatly reduce runway line and threshold jaggies, as well as improve texture swimming in the distance.  Dunno why, but it's the Bioshock option that allows the other settings to function.

Hi Noel,

so these settings are only effective with the BioShock parameter set?

Spirit

I've reported this to LM and Wes indicated it's on the to be fixed list.  FYI, if you force AF 16X via nVidia Inspector, you do NOT have to do the "bug work around" to get AF 16X.

 

Cheers, Rob.

Cool, will try that.   I recall early on whenever I used AF 16x in NI I got the weird moire-type patterns in water textures so I stopped doing that.  But that was miles back and even w/ different drivers so sounds like it works the same as in-sim.  Thanks!

"Hi Rich,

not relevant for Windows 8 and 8.1, isn't "

 

Sorry do not know anything about windows 8

 

=====================================

Thanks Noel for the heads up - informative

 

=====================================

 

"I've reported this to LM and Wes indicated it's on the to be fixed list. "

 

Thanks Rob appreciate the info

Hi Rich,

not relevant for Windows 8 and 8.1, isn't it?

Spirit

Hi Noel,

so these settings are only effective with the BioShock parameter set?

Spirit

That's right, or was when I checked this out quite awhile back.  I did the requisite testing and confirmed that was the case.  Some people insist you have you must also use an AA type at Enhanced, but I don't see that.  I use Override and all's happy.

Hey Rich , I finally bought p3d and its AWESOME . but i still haven't started to tweak it yet . i have seen another thread in p3d's forum about adaptive vsync . have you tried it . if so then what do you think about it ? 

also I dont have Hyper threading on my 3570k so which Affinity mask should i use ? 

cheers