QUestions above Nvidia Inspector and adjusting FPS

I'm new to Nvidia and this program.

I tried this program several weeks ago to try and limit the frame rate in a certain game (can't remember which now) and it did not work.

Any one got any tips? I have a 120hz monitor and I want to select what fps I have in some games. I don't want to have to use the Nvidia driver if I have to as I don't want to use VSync (half refresh). I know that some games allow you to set the fps in a config.

Also I have noticed that Inspector has a number of options in the fps limiting drop down. Some in capitols.

Why does it show brackets next to some saying to limit input lag?

Do I need to leave Inspector running?

Any help at all would be great!

Thanks,

Sy.

 

Framerate limiting in inspector is separate from Vsync by different fractions.

The ones with parentheses are meant to be used in combination with the matching Vsync @the hertz it says. So with a 60hz monitor with Vsync on, limiting the framerate to 58 fps can help to prevent input lag.

Naturally if you don't plan on using Vsync then knowing this is useless.

Driver framerate limiting via inspector has worked for every game I've bothered to try it in.

Changes in inspector apply to the driver settings. So no, you do not need to leave it on.

 

Does the internal limiter work now? It used to cause driver resets and even bluescreens. Most people use Afterburner/Dxtory/Fraps to limit FPS.

 

It seems to be working. This is a different install and I may have done something noobish last time. Not sure. Great info guys.

Just having a play.

 

I use Adaptive VSync, Triple Buffering and Frame Limiter (Refresh rate minus 2). Most games run very smooth with these settings. No major framerate dips or input lags.

 

Refresh rate minus 2? Oh you mean like 120hz=118 Vsync.

 

It makes no sense to enable adaptive vsync when limiting fps below refresh rate, because vsync will always be inactive.

 

Some games have Triple Buffering settings tho.

Enabling only Framerate Limiter doesn't remove screen tearing. That's why VSync needs to be enabled.

 

Standard vsync yes, but not adaptive vsync. Vsync will always be inactive when you limit fps below refresh rate in conjunction with adaptive vsync.

 

You can just set Frame Limiter (-2) with the same result

 

Standard VSync cause Framerate dips when Framerate is not at limit.

Settings I'm using proved to work great in some games. Here's how it works:

When Frame rate is @ limit, Adaptive VSync removes tearing. Frame rate limiter (Refresh rate minus 2) is enabled to reduce input lag caused by any type of VSync. When frame rate is lower, Adaptive VSync, unlike standard VSync, doesn't cause stuttering or frame rate to lock.

 

But there is no "when". In your case fps is always below refresh rate, because you capped fps at (refresh rate - minus 2):

Hence you're always running with vsync OFF

 

Noisiv is right, you practically disabled VSync with these settings. Happened to me too, when Adaptive VSync was first available I forgot that I used BF3s internal limiter and wondered why there was tearing all the time.

 

Fair enough. Then it would seem NVIDIA's own explanation of the feature is flawed.

We also know that tearing can occur at fps below refresh rate as well. I think the "annoying stutter" they refer to was only problem in double-buffered apps where fps commonly fluctuated between 60 and 30 for example. Triple buffering already solved that.

 

How did you manager to have 100 fps in the list. I don't have that. I can't see a way to add it apart from maybe something to do with the Hex Value. Entered that into the box and nothing showing 100 fps.

 

Edit Inspector's CustomSettingNames xml file in notepad.

100 converted into hexadecimal is 64. Windows calculator can do these conversions.