...nVidia drivers are now live. Version 344.60.

Anyone can confirm that the new driver is working? Any improvements maybe?

Still no Prepar3d profile...

 

http://de.download.nvidia.com/Windows/344.60/344.60-win8-win7-winvista-desktop-release-notes.pdf

 

I have really lost the faith that we will ever get a dedicated profile from nVidia. They are making profiles for all types of stupid games but seem to have no interest in Prepar3d at all...

New driver working fine with P3D2.4

Anyone finding a benefit over the last driver would appreciate the info as I am using that laptop hack driver still as it is the best so far for me - thanks

Works fine for me also on 2.4. I can't say there was a performance boost but no degradation either.

Works fine for me also on 2.4. I can't say there was a performance boost but no degradation either.

 

Thanks

Still no Prepar3d profile...

 

 

Forgive my ignorance but why is a profile from nvidia required? Is it different from creating your own with NVInspector?

 

Thanks

This driver was not listed for my 550-Ti. Still listing the 344.48 as current.

 

Are all cards supposed to get this v344.60?

Works okay, no issues in FSX or P3D

nVidia will often include specific flags and settings for a particular product that the drivers will read/use when it comes to implementation of the rendering the image.  These values are not usually visible via nVidia Control panel, but can be seen when using nVidia Inspector (which is NOT an nVidia application).

 

These flags can be used to govern how AA is performed, SLI implementations, etc. etc. etc.  Most of the time they are used to cleanup application specific issues and especially SLI related issues.

 

When using nVidia Inspector it will work with either the existing profile (that nVidia provide) or you can create a new profile ... be warned having multiple profiles triggered by the same Prepar3d.exe can cause issues.

 

nVidia do apparently respond when they break an application ... as in the case when they broke tessellation for P3D, they did eventually fix it (took a few months).  But yes, P3D is low on nVidia's priority list, Goat Simulator is however high on their priority list ... a sad reality of the state of this industry.

 

I think nVidia has done "a little" on the P3D profile ... specifically around FXAA and MSAA which seem to have improved a little as has time between frame consistency.  As for SLI, I'm not seeing anything new - sad because I have 3 Titan Blacks and only one is actually doing anything.  In my setup SLI has moved a step backwards in support/compatibility with these more recent nVidia drivers ... hence why I have SLI disabled for P3D.  

 

Unfortunately I can't visualize efficient multi-GPU support in P3D until we go to DX12 where the application developers will have more control of multi-GPU processing.  It takes "some" (not all) of the dependency away from nVidia which is a good thing since nVidia do seem rather busy with other applications and priorities.  But don't expect P3D DX12 any time soon.

 

Cheers, Rob.

Im seeing quite an improvement.

 

 

When I play World of Warcraft.

Rob, quick question for you.

 

When you say 2 profiles as an issue, does this also mean as an example NI as wells and the Nivida control panel and it's 3d settings? I am wondering what effect if any if one chooses to use the default or base settings on one but a specific profile on another? Just curious as I often wondered how this would affect the application and which one may or may not take precedence. I would love to only use one but curious if the Nvidia default or base may affect this also.

 

Regards

Bob

Hi Rob, if you have disabled SLI with 3 cards, are you some how using them in some way to utilize even 1 extra card or is this not possible in any way, shape or form?

 

I have 2 x GTX670 in SLI but if P3D isnt using it even with the AFR friendly .exe hack exe, then i might as well go back to disabling SLI and reducing my settings?

 

What do you think mate?

 

Thanks for your help

 

Doug

If we go into the NCP and choose a profile, then choose Restore -> Apply, then run up NI we see the profile is gone. If we close NI, make any single change in the NCP, let's say set 4xSSAA, and Apply, then when we go back into NI there is a new profile. We can make changes to that safely.