Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
Its not the same as Gsync at all though...
It will work at the monitor refresh rate eg. 60hz, 144hz or whatever it is....
And your FPS will have to be higher than the monitor refresh rate...
Gsync will sync the monitor to whatever your FPS is from 30-144hz with no tearing or lag.
But yes fast sync looks good if you play CS:GO or something at 300fps and want no tearing or lag, or it might still be better to run at 300fps Vsync off for the lowest possible lag.
But not a replacement for Gsync at all.
From what I read it replaces gsync
Tom peterson said specifically do NOT use fastsync if its above 60fps on a 60hz monitor. So i dunno where people are getting that you need to drive your fps up past what your monitor can do. He said its good for when its under 60fps but not at or over 60. He said this on pcper stream the other day.
This doesn't replace GSync. FastSync is used to eliminate screen tearing in situations where the game's framerate is far greater than the monitor's refresh rate, but without the input lag of VSync. The feature is built into the card and does not require a monitor with special hardware. Unlike Gsync, you cannot use FastSync in situations where the framerate dips below the refresh rate, as that will only lead to stuttering, just like Vsync.
No. No, you are not allowed to do that.![]()



GSYNC ceases to function at 60FPS (monitor cap) and VSYNC functionality kicks in IF enabled (which it is by default, there is an option in NVCP). You can just turn this off so once you exceed your refresh rate it runs VSYNC off.
If you turn FASTSYNC on then its like VSYNC off so you can exceed your refresh rate and then you will get the VSYNC benefits (no tearing) but without the associated input lag.
GSYNC users have tried to get around this problem previously by capping their framerate below their monitor refresh rate but this has its own problems.
To be clear, G-SYNC is STILL preferable to no G-SYNC if you get low frame rates (below refresh rate) but as we already know, G-SYNC is useless if you are always at maximum refresh rate, and this is where FASTSYNC comes in. Hence why some may find that they are useful together.
Because Linus is an idiot.
In the video he talks about turning vsync on and off in-game. With gsync you ALWAYS have vsync off in game, you then use control panel to control gsync's vsync behaviour. If he was turning it on/off in game and not doing anything in control panel, we cant be sure what settings he was actually using.
The other thing is that nvidia have updated their drivers as to how gsync's "vsync" behaviour works, so even if he did the testing right (which based on his video he didnt), the results would now be different anyway.
At 45fps vsync would be having no effect, its purely Gsync working (unless he turned on vsync in game which would revert to traditional vsync and gsync wouldnt be operational)
I don't know if it does but the last time I had stuttering, I scratched my head for a bit, checked the game settings and V-Sync was on in game and turning it off fixed it. Not sure if the newer drivers have more control but possibly. probably best just to make sure V-Sync is off in game settings but on in the NCP.
I had direct confirmation from Nvidia engineers earlier this year that G-SYNC does nothing special whatsoever to 'cap frame rates'. It simply reverts to VSync on if the framerate exceeds the refresh rate cap and VSync is enabled in NVCP or otherwise. The reason you're not seeing any confirmation otherwise is because the 'traditional behaviour' still applies here.