Driver mis-match ... Texture_Bandwith_Mult ...

[dgraham1284 92]

Hi Vic,

 

Yes, still used.  Now my 40% increase was not accurate ... that was related to my driver mismatch which I have since resolved as it was causing other issues such as audio drop outs.  

 

Your suggestion (I think it was yours) to use DDU to do a complete driver clean from Safe Mode was most helpful.  I'm now running 337.88 with ALL my components the same version and no more sudden and inconsistent FPS changes.

 

I am still seeing a benefit from the 160 value, but not 40%.

 

Cheers, Rob.

 

EDIT: That reminds me, I need to update my web site showing those settings

 

Mind if I ask your reasoning for running 337.88? Just curios as it is a rather old driver.

[pincopanco 5]

This trick works well with FPS locked at 30, but with Vsync off.

[Guest]

 

 

Mind if I ask your reasoning for running 337.88? Just curios as it is a rather old driver.

 

Seems to work the best for me setup with P3D right now ... hopefully when nVidia release a driver with a P3D profile that will change.

 

Cheers, Rob. 

[Cruachan 705]

Does this make any sense or am I deluding myself?

 

Turns out I was being delusional :(

 

Stuttering soon became the order of the day. After much effort trying to circumvent the problem, in the end I reverted back to a "TEXTURE_BANDWIDTH_MULT" value of 30, recompiled the Shaders folder and all appears well once again Yes, Rich, it worked on this occasion

 

I'm guessing it may have something to do with the VRAM restriction of 2GB, but I could be wrong.

 

Ah well. sometimes it's just better to leave well alone. Really I should know by now... LOL!

 

Roll on that long awaited SLI profile from NVIDIA.

 

Mike

[hesynergy 67]

 

Guess I should have followed you advise this afternoon huh?

 

And can you tell me why Avsim killed my YouTube link... Pasted here---> <-again??

 

 

Any ideas?

 

Chas

[Guest]

NOTE TO ALL:

 

I edited this topic title as further investigation provided it inaccurate and I didn't want folks to get their hopes up of a magical P3D config setting will provide such a drastic FPS boost.

 

What lead me to an invalid conclusion was this:

 

1.  Reverted my Driver back to 337.88

2.  Added the TEXTURE_BANDWIDTH_MULT=160

 

Loaded P3D and experienced FPS increase, by as much as 40%.  I falsely assumed the TEXTURE_BANDWIDTH_MULT=160 was the reason ... not thinking that going back to a previous driver would influence my observations.  However, further testing revealed my 40% increase was inconsistent and I discovered nVidia driver components were mis-matched with some old and some new versions ... result of going back to 337.88 drivers.  I removed the TEXTURE_BANDWIDTH_MULT line and continued to get inconsistent FPS results, sometimes 40% higher, sometimes not in the same saved flight recording.  So clearly TEXTURE_BANDWIDTH_MULT had no influence on my setup.

 

The driver components version mis-match was the most likely source of this 40% gain, and it was probably because the driver was NOT implementing Tessellation and/or cloud shadows (even though they were set in P3D).

 

If TEXTURE_BANDWIDTH_MULT setting helped some, that's great, but my own post statement testing indicates no real benefit for my setup.

 

Sorry for any false hopes I may have presented.

 

Cheers, Rob.

 

 

Guess I should have followed you advise this afternoon huh?

 

No idea what this post is about other than that 4 FPS seems pretty horrible.

 

Cheers, Rob.