Sign in to follow this  
do_denver2

New NVIDIA Drivers

Recommended Posts

I just installed the new drivers, and everything basically seems the same.  I'm going to delete my shaders and see if I get any magical improvements.  In the release notes it mentioned that it will help in CPU bottlenecked situations.  We'll see... So far my CPU seems to bottleneck the same as before.

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

Interested to know how it turns out.

 

Gregg

Share this post


Link to post

I haven't noticed any difference in performance, the 337.88 seems a little worse (2 fps) than the 337.50 Beta but barely noticeable.  

 

There is now a "Shader Cache" On/Off option that I think is new, or I just never noticed it before.

 

The water in P3D looks very good at any sun angle now ... testing with SGSS.  Will do some testing using standard MSAA and see.

 

I'd like to know how to get FXAA + HBOA+ ... seems very application specific.

 

Cheers, Rob.

Share this post


Link to post

I'm interested in people's experiences as well.  For now, I'll hold on to 337.50 unless there's anything groundbreaking. 

Share this post


Link to post

Well after a few hours buzzing around this evening I'll give the driver a thumbs up.  Perhaps it was just a lucky session I had, but performance was outstanding pretty much everywhere outside of of ORBX PNW Seattle.  Certainly the driver doesn't do anything that would have a negative effect.

Share this post


Link to post

I installed them (clean), deleted the shader cache, reapplied my NI settings and rebooted.

 

Anti-aliasing:  Might be seeing a slight improvement.

Performance:  Might be a slight bit worse.

 

Gregg

Share this post


Link to post

Mumbo Jumbo.

 

Is there a note from nVidia to the effect that Prepared3D is supported much less improved?

Have they included specific support for SLI or Crossfire?

 

Methinks its placebo effect.  However if it makes you feel good ...  :rolleyes:

Share this post


Link to post

Any improvement over last WHQL ?(335.23)

 

I am also with DX10 FSX and P3Dv2.2

 

Michael

Share this post


Link to post

I haven't noticed any difference in performance, the 337.88 seems a little worse (2 fps) than the 337.50 Beta but barely noticeable.  

 

There is now a "Shader Cache" On/Off option that I think is new, or I just never noticed it before.

 

The water in P3D looks very good at any sun angle now ... testing with SGSS.  Will do some testing using standard MSAA and see.

 

I'd like to know how to get FXAA + HBOA+ ... seems very application specific.

 

Cheers, Rob.

 

Just had a quick flight with the new drivers and the water seems a lot better with standard settings.

 

Daz

Share this post


Link to post

I can't say P3D is either better or worse with the new drivers. I also have not been using NVidia Inspector for a good 2 months now and can't say I see a real difference with that either.

Share this post


Link to post

 

 


Just had a quick flight with the new drivers and the water seems a lot better with standard settings.

 

Agree, tested with standard MSAA and water does indeed look better.  When using SGSS AA the water looks positively fantastic in any light condition (even at lower water detail settings) ... the only down side I've noticed with using SGSS AA via nVidia Inspector is that I'll frequently get the dreaded:

 

Faulting application path: V:\Lockheed Martin\Prepar3D v2\Prepar3D.exe
Faulting module path: C:\Windows\system32\d3dcsx_43.dll
 
at Prepar3D startup.  When I stop using NI, I never see this error.
 
But as far as I can tell there is NO change to the base Prepar3D profile that nVidia provide on driver install ... it does still say verison 2.0 in base profile but it's hard to determine exactly what that reference really means.
 
Keeping my fingers crossed that we'll see SLi/Crossfire (I'm actually now more interested in Crossfire support given the R9 295X2 outperforms two Titan Blacks in SLi for $500 less) ... AMD might be more responsive to working with LM than nVidia.  SLi support from nVidia may take some time and I doubt LM would hold up releasing v2.3 just for nVidia.  And now that the Titan Z seems to be vaporware (delayed for some unspecified reason), I'm leaning towards camp AMD for my next GPUs.
 
Cheers, Rob.

Share this post


Link to post

Mumbo Jumbo.

 

Is there a note from nVidia to the effect that Prepared3D is supported much less improved?

Have they included specific support for SLI or Crossfire?

 

Methinks its placebo effect.  However if it makes you feel good ...  :rolleyes:

I'd really like to see LM pick up the pace with nVidia regarding drivers/inspector.

 

I just don't need anymore features at this point.

 

Mark

Share this post


Link to post

Faulting application path: V:\Lockheed Martin\Prepar3D v2\Prepar3D.exe

Faulting module path: C:\Windows\system32\d3dcsx_43.dll

 

I tend to get this error when I alter the tessellation settings. Usually a shader rebuild clears it up.

 

Are your NI SGSS settings causing any performance issues?

How do you configure NI for P3D?

 

Regards,

Daz

Share this post


Link to post

My sentiments exactly! What the heck is taking so long for proper Nvidia support! I mean this a major defense contractor with a lot of weight! Send some goons over to Nvidia and demand support by the next version please. Thanks.

  • Upvote 1

Share this post


Link to post

 

 


I'd really like to see LM pick up the pace with nVidia regarding drivers/inspector.

 

The ball is not in LM's court and they really have no control over nVidia's developer support priority.   nVidia probably don't consider P3D to be a major title (and it's not) when compared to other game titles that can sell as much as 6-8 Million copies in just first day of launch.  nVidia's priority is most likely based on volume sales .. I'm just keeping my fingers crossed it'll be sometime this year.

 

 

 


heck is taking so long for proper Nvidia support! I mean this a major defense contractor with a lot of weight!

 

Lots of weight, but not lots of volume sales of software that requires good GPUs.

 

 

 


Are your NI SGSS settings causing any performance issues?

 

4X SGSS AA will drop performance significantly (2560 x 1600), but that's not specific to P3D ... that's across the board in any 3D based software.

 

 

 


How do you configure NI for P3D?

 

You first need to make sure you delete the "base profile" for Prepar3D (any time a new driver install is initiated the Prepar3D base profile will come back to life).  Once that is deleted you add a new profile and associate it to the Prepar3d.exe.

 

I have come up with some settings here for using NI and SGSS:

 

High (SGSS)

http://www.robainscough.com/Prepar3D_Settings_2.php

 

Medium (SGSS)

http://www.robainscough.com/Prepar3D_Settings_Medium.php

 

Both have no shimmers, no jaggies, no shingles, no bangles ... but be aware any close proximity to clouds and performance will really drop.  Also suggest turning off Road traffic with SGSS, especially if you have Orbx Vector 1.15 installed.

 

I wrote a tip on how to recover from these d3dcsx.dll crashes here: http://forum.avsim.net/topic/441704-recovering-from-g3ddll-crashes-and-tips-to-diagnose/

 

Like I said earlier, I only seem to get these d3dcsx.dll crashes when I'm running NI with SGSS AA.

 

Cheers, Rob.

Share this post


Link to post

 

 


I have come up with some settings here for using NI and SGSS:
 
High (SGSS)
http://www.robainsco..._Settings_2.php
 
Medium (SGSS)
http://www.robainsco...ings_Medium.php
 
Both have no shimmers, no jaggies, no shingles, no bangles ... but be aware any close proximity to clouds and performance will really drop.  Also suggest turning off Road traffic with SGSS, especially if you have Orbx Vector 1.15 installed.

Well, I tried Rob's NI suggestions and I actually got very good performance.  The jaggies were gone for the most part and for some reason, stutters went away for me too. (This is not with the new drivers by the way.)  Often when I have the sim set to unlimited frames, I get stutters, but adding the NI settings seemed to task my system sufficiently to a point that I did not have high framerate spikes.  Rather the frames stayed more even.  By this I mean that without the NI settings, and on unlimited frames, my system would have a frame rate range of 20-50.  Often when it hit the high end of that range, the frames would hit the low end right after that and I would see stutters.  Perhaps what is going on is the increased work load on the system keeps the frame rate range narrower as I was seeing a range between 20 and 29, so when it hit in the high twenty range, it did not have too far to drop to the low twenty range, thus seeming to maintain a more consistent frame rate.

Anyway, it is late and I find myself babbling, but perhaps this might help someone.  I will try the new drivers soon and hope to see the effects.  I am looking forward to the potential of some better looking water as others have noted.

Share this post


Link to post

 

 


The jaggies were gone for the most part and for some reason, stutters went away for me too.

 

I've just come up with a slightly modified set of settings as per Beau's suggestion (found that gem of info over on LM's forum) AffinityMask = 4081 seems to be the way to go for my setup (i7 3960X) ... extremely smooth, no blurries and no major hit in fps with Fraps recording and TrackIR working well with it also.  I'll post my new settings in a separate thread along with settings changes I made in FTX Vector Configuration program that seemed to have improved my experience with SGSS AA considerably.

 

Uploading my video now and will post new settings in a separate thread.

 

It has taken me some time to "find the balance" with display settings and all my add-ons (FTX Vector was a big source of stutters, it was really capping out CPU/GPU bandwidth).

 

Cheers, Rob.

  • Upvote 2

Share this post


Link to post

Hi Rob,

Can you explain a bit about why this value works.

4081=0100000010000001

 

so this means only 3 threads are being used by P3D ? including core 0.

 

I have a 4770K and am currenty using AM 61, it works really well, with no stutters and no blurries. Even though I am not sure exactly why this value works this well, I just came across it while experimenting.

 

61 = 01100001 which is  similar to 4081 in the sense that its using core 0 and a total of three threads as well.

Share this post


Link to post

.....

Can you explain a bit about why this value works.

4081=0100000010000001

.....

AM 4081 = 111111110001 and not what you wrote.

Spirit

Share this post


Link to post

I have been using this new driver suite for the last couple of days.  No better, no worse...and quite stable. Makes all the sims looks good, crisp and clear textures throughout all.

Share this post


Link to post

I haven't updated since 334.89 and I dare say I would see very little, if any difference from what I see now.

 

I gave up chasing the nvidia driver train.  I'll wait until the next significant update.

Share this post


Link to post

I haven't updated since 334.89 and I dare say I would see very little, if any difference from what I see now.

 

I gave up chasing the nvidia driver train.  I'll wait until the next significant update.

I dunno...I'd try it out Dean....it makes all my sims, look very clean and clear.  

Share this post


Link to post

The ball is not in LM's court and they really have no control over nVidia's developer support priority.   nVidia probably don't consider P3D to be a major title (and it's not) when compared to other game titles that can sell as much as 6-8 Million copies in just first day of launch.  nVidia's priority is most likely based on volume sales .. I'm just keeping my fingers crossed it'll be sometime this year.

 

 

 

 

Lots of weight, but not lots of volume sales of software that requires good GPUs.

 

 

 

 

4X SGSS AA will drop performance significantly (2560 x 1600), but that's not specific to P3D ... that's across the board in any 3D based software.

 

 

 

 

You first need to make sure you delete the "base profile" for Prepar3D (any time a new driver install is initiated the Prepar3D base profile will come back to life).  Once that is deleted you add a new profile and associate it to the Prepar3d.exe.

 

I have come up with some settings here for using NI and SGSS:

 

High (SGSS)

http://www.robainscough.com/Prepar3D_Settings_2.php

 

Medium (SGSS)

http://www.robainscough.com/Prepar3D_Settings_Medium.php

 

Both have no shimmers, no jaggies, no shingles, no bangles ... but be aware any close proximity to clouds and performance will really drop.  Also suggest turning off Road traffic with SGSS, especially if you have Orbx Vector 1.15 installed.

 

I wrote a tip on how to recover from these d3dcsx.dll crashes here: http://forum.avsim.net/topic/441704-recovering-from-g3ddll-crashes-and-tips-to-diagnose/

 

Like I said earlier, I only seem to get these d3dcsx.dll crashes when I'm running NI with SGSS AA.

 

Cheers, Rob.

Hi Rob.

Good stuff here.

 

Tried out your settings and performance seems very good - but I am still getting shimmering with the reflections of terrain/vegetation on water - Do you have none of that?

 

I'm on a 780ti w/ i7 4930k.

Thanks for any thoughts!

Share this post


Link to post

 

 


Tried out your settings and performance seems very good - but I am still getting shimmering with the reflections of terrain/vegetation on water - Do you have none of that?

I tried the high settings and it worked like a charm.  Did you try the high or medium settings?

Share this post


Link to post

AM 4081 = 111111110001 and not what you wrote.

Spirit

Right you are.. used the wrong calculator ...  :P

so 61 is 111101.

 

So just please ignore my msg.. but would still be interested to know why 4081 is working out so well for Rob.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this