Blur Busters Forums

Should I trust FPS cap software that ALSO does overclocking? Thinking it may bug and leave me unhappy. I.e., MSI Afterburner and/or "NVidia" Inspector.

What about DXTory?

Simply, what do you use and trust to cap framerate consistently with low CPU load?

I'm just stupidly assuming that NVidia doesn't have the option in their software.

This is for doing lower FPS while running at the highest Hz, in games that don't have a built in setting for it.

Nvidia Inspector!

Sorry gtg

The best one is RTSS (comes with Afterburner), hands down.

The capper that's built-in into the nvidia driver and configurable through inspector is completely broken. It doesn't even cap to what you set it to if you use vsync. To eliminate input lag, I use 0.05hz more in my modes (60.05, 85.05, 90.05, 120.05). The nvidia capper will refuse to cap to 60/85/90/120. Instead, and because it was written by idiots, it will cap to 60.05/85.05/etc automatically and you can't do anything about it, thus no good input lag reduction is possible.

And in OpenGL games it's even more broken, as it caps to a wrong value altogether, thus introducing micro-stutter. That thing is just broken and good for nothing.

TL;DR: Use RTSS, avoid nvidia's capper.

I used Nvidia Inspector for Fallout 3 at 90fps~ with G-Sync and it worked really well. The game it's self is broken if you push it past 90ish fps so this helped immensely.

The reason i suggested Nvidia Inspector is because I tried RTSS (Afterburner) at first but it was causing screen tears on G-Sync mode so it didn't really help me. I haven't tried doing the framerate caps to prevent input lag before so i haven't really ran into that before.

RealNC wrote:The capper that's built-in into the nvidia driver and configurable through inspector is completely broken.

Having different desired outcomes does not mean that it is "broken" or "written by idiots".
If your framerate cap is not in sync with the refresh rate, then you're going to get stuttering.

Your desired outcome is decreased latency with no regard for smoothness, that's not NVIDIA's desired outcome for their framerate limiter.

Glide wrote:

RealNC wrote:The capper that's built-in into the nvidia driver and configurable through inspector is completely broken.

Having different desired outcomes does not mean that it is "broken" or "written by idiots".
If your framerate cap is not in sync with the refresh rate, then you're going to get stuttering.

No, you're not. For example, I use 60.05Hz and a 60FPS cap in RTSS. No input lag, no stuttering.

And besides, when I tell a frame limiter I want 55FPS but then it goes ahead and caps to 60FPS instead, it's broken. And nvidia's limiter does exactly that. If I wanted 60, I would have told it to do 60. I told it to do 55, not 60, so why on earth does it not allow for that.

I'm sorry, the nvidia limiter is complete and utter crap As a bonus, and as already mentioned, it's even more broken in OpenGL and Vulkan.

RTSS is the best fps limiter. I've tried using the limiter in the Nvidia drivers once, but it was inaccurate.

The only new thing I want from RTSS is a decimal fps limiter . I would like to experiment with Ys II, using G-Sync and ULMB. There is a certain framerate where the running speed synchronizes perfectly, and it's around 90.1fps (it probably needs a second decimal, because I got tiny sutters after a few seconds). But with my current monitor I can't create custom refresh rates. Probably the scroll speed movement in pixels/second becomes an exact multiple of the refresh rate.

masterotaku wrote:RTSS is the best fps limiter. I've tried using the limiter in the Nvidia drivers once, but it was inaccurate.

The only new thing I want from RTSS is a decimal fps limiter . I would like to experiment with Ys II, using G-Sync and ULMB. There is a certain framerate where the running speed synchronizes perfectly, and it's around 90.1fps (it probably needs a second decimal, because I got tiny sutters after a few seconds). But with my current monitor I can't create custom refresh rates. Probably the scroll speed movement in pixels/second becomes an exact multiple of the refresh rate.

Yeah. I posted a suggestion for this a while ago here:

http://forums.guru3d.com/showthread.php?t=410079

But it got exactly zero traction

Also, the "Global" option does nothing. Not even if the game isn't on the list. Not saying there's a bug exactly, but really the option shouldn't be there as you think you're setting an override for all DX/OGL games.

RealNC wrote:

Glide wrote:

RealNC wrote:The capper that's built-in into the nvidia driver and configurable through inspector is completely broken.

Having different desired outcomes does not mean that it is "broken" or "written by idiots".
If your framerate cap is not in sync with the refresh rate, then you're going to get stuttering.

No, you're not. For example, I use 60.05Hz and a 60FPS cap in RTSS. No input lag, no stuttering.

Assuming that the timing was perfect - and it certainly is not - the game would be stuttering every 20s when presenting 60 FPS at 60.05Hz.

RealNC wrote:And besides, when I tell a frame limiter I want 55FPS but then it goes ahead and caps to 60FPS instead, it's broken. And nvidia's limiter does exactly that. If I wanted 60, I would have told it to do 60. I told it to do 55, not 60, so why on earth does it not allow for that.

Can't say I've ever seen that, but it's not like I would ever want to cap at 55 FPS on a 60Hz display when V-Sync is enabled.