Ok. How low below my monitor's refresh rate of 165 Hz should I set the frame rate cap?Sparky wrote:There *should* be no difference in that situation, but the outliers in frame time could introduce one. Say you have a normal frame, a long frame and a short frame in that sequence, both will display the normal frame twice, and fast sync will drop the long frame in favor of the short one, while v-sync will display all 3. So the median latency is identical, fast sync recovers from hitches faster, but v-sync recovers from hitches more smoothly.lukeman3000 wrote:Furthermore, if I'm using an FPS limiter to stay below my monitor's refresh rate, then it really doesn't matter whether or not I have V-Sync or Fast selected, because I should always stay within G-Sync range, which is preferable... right?jorimt wrote:@lukeman3000, G-SYNC + Fast Sync acts exactly like G-SYNC + v-sync on within the G-SYNC range (inside max refresh rate of display). There is only a difference between those scenarios when you exceed the G-SYNC range, at which point (with G-SYNC + Fast Sync + no fps limiter), G-SYNC disables, and Fast Sync enables.
You can see the chart here, if you haven't already (Fast Sync input latency numbers will be updated once I'm finished with my input latency re-tests, which are currently in progress):
http://www.blurbusters.com/gsync/gsync101-range/
For a variety of reasons, there is zero benefit to using G-SYNC with Fast Sync in my opinion.
Also, how many FPS below the monitor's refresh rate do you recommend to cap at? And is RTSS still recommended, or is there a better option?
In game cap is always preferable if it's available, other than that, RTSS is fine.
Also, what happens if I have an in-game cap and RTSS active at the same time? Which one takes priority? And does having RTSS active in this case hurt me in any way?