I've tried TBM values from 10 to 400 (the min-max range) in both FSX and P3D over the years, and have not seen so much as one frame per second change up or down, nor does it change my scenery loading, or anything else as far as I can see. Its an odd one, as from the sound of it (Phil Taylor's description) it should have a huge impact, but it seems to do nothing

Here is an interesting read. It's for fs9, but it's clearly the same rendering process so should also work. It also states that anything above 120 is effectively a waste of time.

http://www.mycockpit.org/forums/showthread.php?t=11106

 

So Rob is on the right track.

 

PS in my cfg I have-

UPPER_FRAMERATE_LIMIT=35
TEXTURE_BANDWIDTH_MULT=120
TextureMaxLoad=30

This does produce the occasional stutter when panning but absolutely gets rid of blurries. Which to me are more annoying than the odd stutter here and there.

 

PPS another point it mentions is to adjust your zoom. Nowadays with almost everybody using a widescreen monitor it's essential anyway. For a16:9 view set 85 zoom and for 15:9 set 81. Otherwise the field of view is totally unrealistic.
 

Or, you have SSDs across the board making video card capability much less a factor.

 

I have ZERO SSD drives in my PC.  I wish I did.  It would speed up the load times on loading MegaSceneryEarth textures.    When I turn on 4 or 5 states, it takes up to a good 2 minutes to get in the simulator.    My main flight sim drive is a 10k Raptor though.  

I've done a lot more testing and unfortunately my results are inconsistent.  I've been testing with 337.88 drivers (NOT using nVidia Inspector).

 

I need to dig into this further ... I found what I think is a driver version mis-match.  Is there is anyone that has NOT installed (ever) any nVidia drivers beyond 337.88?  If so, can you tell me what version of nvGameSR.DLL you have?   You can find this in the nVidia Control Panel | Help | System Info ... click on the Components tab.

 

My mis-match maybe a result of me going back from 347.09 to 337.88.

 

So as of right now, I'm going to retract this 40% claim from the TBM=160 until I can figure out exactly why it's not consistently a 40% gain.

 

Sorry if I got anyone's hopes up and I'll try to find a consistent solution.

 

Cheers, Rob.

 

Rob - Not sure if this is going to help or not but I am running 337.88 once again. I always do a clean wipe of all drivers before I install or reinstall new or legacy drivers as I did with the 337.88 going from 340.65.

My nvGamerSR.dll is 6.14.13.4465

Gentlemen see below the link for a interesting read ;-)

 

While it's dated it still holds some useful insights...

 

http://www.simforums.com/forums/fsx-tweaks-demystified_topic37948.html

 

Also the calculation math is useful even for P3D...

 

Cheers,

 

 

My nvGamerSR.dll is 6.14.13.4465

 

That's left over from the 344.65 driver.

Gentlemen see below the link for a interesting read ;-)

 

While it's dated it still holds some useful insights...

 

http://www.simforums.com/forums/fsx-tweaks-demystified_topic37948.html

 

Also the calculation math is useful even for P3D...

 

Cheers,

Note Nick N's comments in red. He basically says that none of those calculations have any bearing in reality.

At any rate the way I see it if your GPU is already maxed out you would probably see no benefit from this setting. If your GPU is being artificially held back due to this setting then you may get a benefit from it.

 

That's most likely it - for those systems with headroom, this should theoretically open the taps for the GPU. In FSX, a high TBM (e.g. 120) coupled with a low FFTF (e.g. 0.10) and unlimited frames seemed to work best on my rig.

 

Will have to try this with P3D when I get back...though I doubt it'll do much on my current GPU.

Thanks for all the feedback, much appreciated.

 

It looks like I have some sort of driver mis-match (see below) ... however, I'm not sure it's relevant, tried to get more info on what nVidia 3D Settings Server (nvGameSR.dll) does in relationship to setting nVidia profiles ... if there is indeed any relationship.

 

 

 

I'll keep digging.

 

Cheers, Rob.

 

EDIT: the odd thing is that 344.75 was NOT the last driver install I had on my system prior to reverting back to 337.88 ... my prior driver was 347.09

That's left over from the 344.65 driver.

OOPS.... I never caught that, thanks for letting me know

That's left over from the 344.65 driver.

Note Nick N's comments in red. He basically says that none of those calculations have any bearing in reality.

That's the point lol ;-)

Just opened my prepar3d.cfg after a very long time and... ooops...what do I see?

TEXTURE_BANDWIDTH_MULT=1800 :huh:

I will return to a value of around 200 (GTX970)

Maybe I've finally found the source of those annoying micro stutters on my rig, so thanks anyway!

Thanks for all the feedback, much appreciated.

 

It looks like I have some sort of driver mis-match (see below) ... however, I'm not sure it's relevant, tried to get more info on what nVidia 3D Settings Server (nvGameSR.dll) does in relationship to setting nVidia profiles ... if there is indeed any relationship.

 

 

 

I'll keep digging.

 

Cheers, Rob.

 

EDIT: the odd thing is that 344.75 was NOT the last driver install I had on my system prior to reverting back to 337.88 ... my prior driver was 347.09

 

 

I highly recommend using this handy program when changing out drivers.

 

http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

 

I deletes all traces of the drivers, allowing a complete fresh install. 

 

 

I highly recommend using this handy program when changing out drivers.

 

Indeed, its a handy tool to use once in a while, though I don't bother with it every driver change. I would then reinstall using only the components within the driver package you need (using a 'Custom' install) which in my case is the Display Driver and PhysX (for a couple of games)... all the rest (3D, HD Audio etc) is baggage I don't need.

 

 

I highly recommend using this handy program when changing out drivers.

 

I second this motion. It's particularly handy when swapping back and forth between regular, Quadro and laptop driver versions. Make sure that you run it in Windows Safe mode to get the best results.

Hi,

 

Does TBM=160 effect VAS ?

 

Michael Moe