Ah, one of those myths:
Combine vsync/TB with fps limit just below refresh rate FTW
This is from Riva Tuner creator:
http://forums.guru3d.com/showpost.php?p=4227080&postcount=184
I don't think he understands it either, 59 fps into 60 will display as 1 repeated frame every second, which will result in 58 frames at even 16.6 ms intervals and one frame at 33.3 ms, making the average feel like a frame every 16.95 ms, which is pretty friggen close to how 60 fps feels. What he's saying is that if you're limiting below the refresh rate, you obviously need a factor (not a multiple like Mr. Alexey is saying) to obtain perfect intervals. No shit sherlock.
What Oubadah is saying in that post is perfectly valid, capping at 60 fps will give him even intervals at 120Hz if his games aren't capable of sustaining 120 fps. But what he wants to do isn't really advantageous at all. If he can't render 120 fps, and say he can only sustain 80 fps, any frame that cannot be rendered in under 8.3ms (120Hz), will simply result in the previous frame repeating for another refresh and lasting 16.6ms, which is the exact same perceived interval at 60 fps. By capping at 60 he's really just choosing to lose information, because any additional frame that might have arrived withing 8.3ms, now will not.
There's a way I've found that reduces image lag greatly with vsync + triple buffering. It's a program called Dxtory. I set a fps limit of 74, just a digit under my refresh rate (being 75hz), turned on vsync+tb, and now I'm able to enjoy competitive games a LOT better! I recommend everyone who has a fiery hate for image lag AND tearing like me to give this method a try. It's like the equivalent of "max_fps" in Source games and "GameTime.MaxVariableFps" in BF3, except that it works pretty much universally, even in later Source games that had max_fps taken out. I can't believe Nvidia doesn't have this Dxtory feature! Adaptive vsync can go F itself! xD
It must be bliss to do this on a 120hz monitor. I'll know soon enough.
Maximum Pre-rendered Frames set to 0 might have something to do with the results too... not totally sure. I keep mine on 0 anyway. No problems.
They do have it. I didn't know this either until not too long ago, but there's a frame rate limiter within the nvidia drivers that can be turned on with nvidia inspector and now with evga precision x (frame rate target feature)