For example, I noticed Nvidia defaults their FPS limiter in the driver to 58. I expect because with G-Sync you want to cap 2 FPS beneath monitor refresh as shown here by BlurBusters: https://blurbusters.com/gsync/gsync101-input-lag-tests-and-settings/5/ To be on the safe side they recommend -3 FPS but note they're using a 60 Hz G-Sync panel for this test. Now I also noticed Nvidia caps FPS to about 138 or 139 when using Ultra Low Latency mode in conjunction with G-Sync on my 144 Hz monitor -- they do this automatically. I don't own a 60 Hz G-Sync panel but I suspect they'd cap that one automatically to the 58 value so they seem to be increasing the number of frames beneath monitor refresh as the monitor refresh value gets higher. So, notice 2 frames out of 60 is about 3.333% and 6 frames over 144 is 4.17%. 4.17% would be equivalent percentage-wise to capping 2.5 frames beneath 60 which would fall inline with BlurBuster's recommendation above seems to me. Could this be because the higher refresh you go the smaller frametimes become so at 60 Hz 2 frames is quite a bit frametime wise compared with 2 frames at 144 Hz? Could the G-Sync module need a bit of frametime buffer time to work right? I could be misremembering but I thought I remembered BattleNonSense at one point saying his 165 Hz G-Sync monitor he had to cap 5 frames beneath or some such in his own testing to avoid the g-sync ceiling, something like that, but I'd have to go dig that video up again, I could be misremembering precisely what he'd said. Basically I'm wondering if with higher and higher refresh rate G-Sync monitors if you need to progressively cap more and more frames beneath refresh to avoid additional input latency. Thanks!