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

 

++1

 

I always use this when changing drivers and then rebooting in safe mode to clear any remaining files.

 

Using the 337.88 drivers. Very pleased.

 

That tweak of Rob's DOES improve my texture loading when flying fast and high then descending quickly to circuit altitude. Will try it with some photoscenery tonight.

 

Regards

Adam

 

 

Does TBM=160 effect VAS ?

 

TBM doesn't effect anything anymore.

It is disabled since version 2.0

 

Regardless what value you enter, the performance remains the same and it effects nothing.

TBM is a remaining relic from the older FSX times when very different DX9 methods were used to 'pump' textures to the video board.

With DX11 it does nothing.

There's little use to calculate it or expecting performance miracles.

 

Potroh

 

 

TBM doesn't effect anything anymore.
It is disabled since version 2.0

 

Try dropping the TBM value to 3 - notice any difference?

 

 

Try dropping the TBM value to 3 - notice any difference?

 

An easy answer to your similarly easy (but slightly provocative) question:

 

I notice NO difference and nobody will ever notice ANY difference.

Very easy to test and if you claim you are able to see any difference then your sense organs are misguiding you.

Neither the framerate-counter would differ nor any other available method would show any difference.

 

The TBM entry is non-functional after 2.0 and if you are still in doubt, please read the corresponding forum message by Beau (dated back in February) in the LM forum.

 

Potroh

The TBM entry is non-functional after 2.0 and if you are still in doubt, please read the corresponding forum message by Beau (dated back in February) in the LM forum.

Searched for it but no luck - have a link?

 

Vic

Set it like this: TBM=snake oil.

Spirit

Just set my TBM to 16 million ... 16000000.

 

Result:-  1,000 fps ... no wait ... I lied.  :unsure:  Actually there was a reduction of 3fps on my default flight.

 

Happy New Year. 

Previously I had reported no fps increase in 3 test runs using Rob's original suggestions, but left in the config change just to see how it would work on a day to day basis. I have been flying in ORBX NZ NI for the last two weeks, and when I returned today, the fps did jump at least by 10 compared to my last several NZ flights without the config change. Today's flight was within a hundred miles of the others, with similar terrain and weather. I've got several more flights to go in NZNI and will report back in a few days to see if the fps change is consistent.

And Happy New year to all !!!

An easy answer to your similarly easy (but slightly provocative) question:

 

I notice NO difference and nobody will ever notice ANY difference.

Very easy to test and if you claim you are able to see any difference then your sense organs are misguiding you.

Neither the framerate-counter would differ nor any other available method would show any difference.

 

The TBM entry is non-functional after 2.0 and if you are still in doubt, please read the corresponding forum message by Beau (dated back in February) in the LM forum.

 

Potroh

If it does nothing, why is it in the .cfg file?

 

 

The TBM entry is non-functional after 2.0 and if you are still in doubt, please read the corresponding forum message by Beau (dated back in February) in the LM forum.

 

Just to clarify, the entry is still used ... I inquired with LM and Beau's response as follows:

 

Rob,

 

Yes.  The texture bandwidth mult value is used but only takes effect when framerate limiter is enabled.  It is set up to define the underlying framerate used to calculate texture load and allocation limits.  If you lock to a lower framerate than the value of the texture bandwidth mult, then the texture load allowance will be increased to accommodate for the longer than necessary GPU frames.

 

The algorithm is basically this:

TextureMaxLoad = max(TextureMaxLoad, TextureMaxLoad*TextureBandwidthMult/LimitedFramerate).

 

Thanks

Beau

 

Cheers, Rob.

Thanx for that Rob - I KNEW it wasn't disabled as some insist but it's difficult to prove a negative.  IIRC, this is the same algorithm that Phil Taylor mentioned years ago.

 

So, bottom line, it HAS an effect but only if you limit frames IN the sim.

 

Vic

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

 

 

Just to clarify, the entry is still used ... I inquired with LM and Beau's response as follows:

 

Rob,

 

Good information. Thanks. And good to know that I'm neither crazy or blind, as "of course" I never tested TBM with the limiter enabled.

 

Potroh

Just for clarification. The limiter is the internal p3d limiter not an external i.e. Nividia inspector?

 

Thanks

Bob

Yes, Bob - the INTERNAL limiter must be set. NVI controls the FPS outside of P3D. SO, if you had NVI set to 30 and P3D set unlimited - TBM function would not work.

 

 

Vic