Chill never worked right for me, I always found an FPS cap a better solution (or just having them the same value) as the minimum would activate when i didnt want it to, or it wouldnt apply to some parts of games i DID want it to.
To be fair i've only used it since an RX580, but that was recently.
I could have been waiting to click on a headshot, for example and now the framerates halved and i missed the shot
Chill can achieve the same thing any FPS limiter can, in that a cap below Vsync refresh rate can drastically reduce Vsync related input latency
i have used it to limit the framerate to below the freesync limit on my 4k60 monitor…
in some games easy in parts to get 70 fps, but then the frame rate dips to 45… (freesync range is 40-60, but 45-60 is a good ramge)
I need to limit the up range because the monitor “stutters” or desyncs when it goes above 60.
vsync does not work, because it sometimes gets locked at 30. so turing off vsync fixes it... then the above 60fps problem…
happens in GTAV 4k, start at the “eye” or ferris wheel, going north, above 60fps, then when in the “country” below 60. (i use GTAV, because that is my goto benchmark for Useability… because the max settings still max out GPU, without msaa… but are they useful eye candy?, only for driving around)
on a 6750xt setting display to 3200x1800 and using FSR, (and really does look like 4k or 2160, or close enought, of course 1440p is fine if you are pla6ing the game and not looks at the scenery…)
try 58. stops the stutters… (on a freesync monitor)
Games render frames ahead, usually 2.
Capping 2 FPS below the refresh rate ensures your frames fit within the monitors timing window at all times, instead of hitting that buffer and waiting on an old frame to be sent.
If the GPU is maxed out, you get input latency because the CPU had data ready and waiting, that is now stalled out waiting on the monitor.
If the CPU is maxed out, you get stutter as no data arrives in time.
The 1-2 frames ahead is designed to buffer that out for a smooth experience, but 16.6ms x2 = 33ms, and that's not exactly great on modern displays that can shoot content out so much faster, so being "on time" feels a hell of a lot nicer especially when it doesnt vary that latency value around wildly.
48-60 is a common Vsync range, because then it can double 24FPS content from bluray to 48Hz.
Vsync without triple buffering (old titles, especially openGL ones) can only work in multiples of the refresh rate - 60Hz at 60/30/15FPS. That's a driver or game setting to fix.
