Usually, it's the frame rate cap which the game uses at engine level, not the refresh, which dictates the speed. For example, RAGE is capped at 60 fps, and therefore will run at 60hz because of g-sync. But you wouldn't want to run it in 60hz mode, if you know what I mean? It wants to be capped under the refresh because of the vsync type input lag that seems to occur when the hz maxes out, within a particular refresh rate. So you want to be capped under it. It wouldn't matter if you were running in 85hz, 100hz, 120hz or 144hz, just as long as it's over 60hz, even though it will be running in 60hz mode because of the frame rate.TSM wrote:I was confused because there are games that run at 60 hz but are still in full 144 hz G-Sync mode (Diablo 3 for example). I checked one of the Sonic the Hedgehog games and you are correct. Using application controlled causes the maximum refresh rate to lock to whatever the program dictates. Luckily application controlled is only necessary when a game's speed is dictated by the refresh rate.
Are you talking about sonic transformed? because I know how to get this game running perfectly with G-sync, but you need to switch vsync on in the config, force highest refresh from driver level, then cap the frame rate at 60 fps with dxtory or rivatuner statistics server (rivatuner is better, it's more accurate and precisely timed). This case of sonic transformed, will run over 60 fps and stutter like crazy. it doesn't speed up, but it's only meant to be run at 60fps or 30 fps capped. Any other frame rate and it stutters. Funnily enough, they did engine cap at 59 if you disable vsync in the config, and it's pretty stuttery even then, because even though g-sync will start running the monitor at 59hz to match it, the physics is somehow out of key.
Anyway, sorry If I've rambled, or misinterpreted anything you've said...