Low-Lag Vsync ON - and how it can screw with your head

[Vayra86]

A little story from my end, a day in the life of a PC gamer, call it what you will - this just happened.

So, not too long ago, I adopted a brilliant way to avoid tearing + achieve low input lag; taken from
https://www.blurbusters.com/howto-low-lag-vsync-on/

Used the method below: do note the bolded part there...

We found that only one frame-rate capping software, called RTSS (RivaTuner Statistics Server) was able to reduce VSYNC ON lag without adding visible stutters. Other frame rate limiter software (in-game, NVInspector, etc) were not as accurate.

1. Download and install RTSS.
2. Go to TestUFO Refresh Rate and measure your exact refresh rate to at least 3 decimal digits.
3. Subtract 0.01 from this number.
4. Use that as your RTSS frame rate cap for that specific game.
   For fractional caps, you need to edit two lines in the RTSS config file. Remove the decimal point for the “Limit” line, and configure a divisor in the “LimitDenominator” line. Example of 59.935fps cap:[Framerate]
   Limit=59935
   LimitDenominator=1000
5. IMPORTANT: Replace “59935” with TestUFO Refresh Rate, subtract 0.01, and remove the decimal point.

Last week, built my new rig and just like many people would, I had to do some simple overclocking, and also touched on overclocking my GPU again (its in a new, much cooler case) because who knows, an extra 13-26mhz may be up for grabs! And lo and behold, it actually did clock higher, and remained a lot cooler doing so. Happy Vayra86! Next step: stress/test the OC... Weeee new 3DMark high scores, and my recent Valley and Heaven benchies that I posted here with nice scores.

Next evening, end of a days' work, I fire up the rig for some gaming, I mean, its about time to try those settings for real. I go into RTSS, and change the framerate cap from 0 (unlimited, because stresstests) to 120 like I've done for the past five years. Fire up Overwatch... black screen. RTSS pops up, shows 'D3D11': 0 FPS / 83333ms frametime. I check my GPU clock and load: stuck at 0-1%, 139mhz Core. I try other games, 3DMark, same thing.

I panic. Did I bork my GPU??? Did my CPU OC fall apart? Did my cat piss on something?

To be continued - or rather... WHO KNOWS WHAT HAPPENED? Small spoiler: I did fix it

 

[jboydgolfer]

most of the stuff in my life that screws with my head isnt inside my computer ,

 

[FordGT90Concept]

I'm guessing you screwed up the Limit/LimitDenominator. To be perfectly honest, that's really slopping coding on the developers' behalf.

 

[Vayra86]

10 points to @FordGT90Concept ... or one 'Like', at least

LimitDenominator turned 120 into 0.120 FPS...

Had to rewrite the file again and replace it in the RTSS directory to get my 119970 back

 

[FordGT90Concept]

Should be:
Limit=119970
LimitDenominator=1000

Like I said, sloppy coding. It should just ask for 119.970 and do the math it needs to do internally. Breaking it apart is begging for the exact user error you ran into. If there's some reason why they have to be provided separately, it should check the inputs for mistakes and say something about it. Bad program design.

 

[RejZoR]

Frame limiting doesn't work. I've tried everything and it just makes image tearing absolutely horrendous on my 144Hz screen no matter what I set it to. 60, 100, 120 or 144Hz, it always starts to tear like insane. Only options that work are Fast V-Sync and Adaptive V-Sync. Low input lag to a point you basically don't feel it with zero tearing.

 

[Vya Domus]

Frame limiting doesn't work. I've tried everything and it just makes image tearing absolutely horrendous on my 144Hz screen no matter what I set it to. 60, 100, 120 or 144Hz, it always starts to tear like insane. Only options that work are Fast V-Sync and Adaptive V-Sync. Low input lag to a point you basically don't feel it with zero tearing.

Because if you limit the frames they are still not synchronized with the refresh rate in any way.

 

[Vayra86]

Frame limiting doesn't work. I've tried everything and it just makes image tearing absolutely horrendous on my 144Hz screen no matter what I set it to. 60, 100, 120 or 144Hz, it always starts to tear like insane. Only options that work are Fast V-Sync and Adaptive V-Sync. Low input lag to a point you basically don't feel it with zero tearing.

That is what this way of implementing Vsync does, in fact. You should really try it. Use the website to measure your real refresh rate, and put it in the global file, run RTSS + Fast Sync.

Frame limiting on its own was never intended to be a tear-free experience. It was meant to reduce GPU temps/loads (so it can boost when FPS dips to maintain FPS cap more readily, as well) in the way Vsync does, but without the input lag penalty.

 

[RejZoR]

Because if you limit the frames they are still not synchronized with the refresh rate in any way.

It's not that, it actually makes tearing unbearably awful. Not using V-Sync is just mildly annoying, this made it unplayably annoying. I'm talking about massive tears. It's better to just not use V-Sync then.

 

[Vayra86]

It's not that, it actually makes tearing unbearably awful. Not using V-Sync is just mildly annoying, this made it unplayably annoying. I'm talking about massive tears. It's better to just not use V-Sync then.

The old way of fiddling with fps caps was to set it -1 below or above refresh rate, or other values. But yes, the problem never used to go away entirely.

 

[RejZoR]

I've tried all of that, nothing worked.

 

[bat33]

hi,

got similar issue on my 60hz display in battlefield 1 , i usually cap fps to 61 for 60hz, i get the best inputlag, but got tearing and frame spacing.

i see the rtss technic, and it work for me, i measured my exact refresh rate which was 60.003, I SUBSTRACT 0.006, so, it give me 59.997, i cap at this value with riva turner.
in nvidiacontrol panel, i enable vsync for the specific game, set maximum pre rendered frame to 1 (for less input lag), i launch my game and it actually work.
note: i tried first with fast sync but give me anoying random stutter, only classic vsync seems work.

i gonna push my test, i will tell you how it goes, but you should try substract 0.006 it work for majority, but depend of rig and game

 

[RejZoR]

It's easier to just use one of latest new V-Sync modes. Zero input lag, zero tearing.

 

[bat33]

It's easier to just use one of latest new V-Sync modes. Zero input lag, zero tearing.

LOL? can you explain? new v sync mode? you mean fast sync? it need 2x refresh rate and bring random stutter, do you know what you talk about?

 

[RejZoR]

You know what, just keep on fruitlessly testing framerate limiting...

 

[bat33]

i got some stutter issues with fast sync and rtss cap while regular vsync / prerender frame : 1 + rtss cap work perfectly with no stutter.

 

[DRDNA]

The old way of fiddling with fps caps was to set it -1 below or above refresh rate, or other values. But yes, the problem never used to go away entirely.

Is my crystal-ball detecting you are going to provide a nice how to with words , pictures , trouble shooting steps, and results to expect with yay's and nay's? Well I hope so and would be a blessing to the forums even though there are other sites with this info it would be nice to see TPU do their own....Here is me wishing this happens.

 

[qubit]

Did my cat piss on something?

There's you're answer right there. I'm sure your cat "helped" every step of the way.

 

[cucker tarlson]

It's easier to just use one of latest new V-Sync modes. Zero input lag, zero tearing.

Fast sync is the absolute opposite of v-sync mode.

 

[Vayra86]

Is my crystal-ball detecting you are going to provide a nice how to with words , pictures , trouble shooting steps, and results to expect with yay's and nay's? Well I hope so and would be a blessing to the forums even though there are other sites with this info it would be nice to see TPU do their own....Here is me wishing this happens.

I might but not on a phone from pubs over here in Dublin last day of an awesome week fly drive in Ireland ATM

Also... funny how this topic got necrod

 

[Vario]

You can apply Vsync or apply a frame rate limiter, among other options, with Nvidia Profile Inspector, would that give an easier result?

 

[las]

Regular Vsync is garbage. Tons of input lag. Sadly some games depend on it.. Physics linked to fps etc (better to limit fps here)

 

[Vya Domus]

Fast-sync does not drop frames , only some of the completed frames end up being shown and the input lag is pretty similar to having no synchronization because it imposes no restriction on the game engine.

 

[bat33]

fast sync cause random stutter exept if you have 2x the refesh rate it use 3 buffer and select the better and good input lag but in practice you get stutter so its not a solution exept if you have 2x the refresh rate

So finally, for a refresh rate of 60.003, ive good result when capping to 59.903 with rtss, with vsync on and pre render frame set to 1, i can play battlefield 1 et battlefield 5 alpha very well, without tearing anymore and a very little input lag, a little more than vsync off, but it worth the avoid of tearing and dont affect the gameplay, so im happy, goood alternative of g-sync

 

[las]

Well, capping your fps also increases input lag.