It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
I'm never sure if GOG is a good place for questions like these but I'm too lazy at the moment to make a new account on Tom's Hardware or something, so here goes...

I got a new monitor today. It's pretty amazing. It has AMD FreeSync but I read a lot about it first and everything said it worked perfectly as a Gsync monitor as well. I have an nVidia 1060. I turned Gsync on and Vsync off and everything was great, super fluid, but I did notice tearing when the game went above 144fps, my monitor's refresh rate. I googled and people said you should actually have Gsync and Vsync on together, and then nVidia will use Vsync to stop the game from going above your refresh. So I turned them both on and went back to gaming.

Unfortunately this introduced stutter. Walking around I now have little hiccups, worse than I ever had with normal Vsync, which obviously ruins the whole point of Gsync. It's not even happening at above 144fps either, I noticed it with the framerate bouncing around between 80 and 100fps.

tl:dr Any tips for Gsync on a FreeSync monitor when it comes to Vsync settings and killing BOTH tearing AND stutter? Thanks techies!
This question / problem has been solved by matrixdllimage
...
Post edited June 21, 2019 by falster
Does the game have any frame cap settings in the options? Are you trying to use v-sync from the game or the nVidia control panel?
What you can try is set your in game frame cap to the closest it will allow to your monitors refresh (usually they round to 10's so 140fps cap for your monitor), turn off V-sync and turn G-sync on. Problem is that not all games have frame caps settings and even then they don't always work properly. I've found that v-sync (at least from the application itself) doesn't always work well with variable refresh- you end up with the game waiting for what it believes to be your monitors next refresh cycle because it doesn't know that the monitor will adjust- that is what can cause the stutter. I'd assume using v-sync from the nVidia control panel(instead of in game) should get around it, maybe.
Post edited June 20, 2019 by CMOT70
What game are you trying to play? Have you had these issues with this specific game before or remember such? I would play around with the settings to see what stops the stuttering and the screen tearing but recently when I had screen tearing issues V-Sync fixed and I was playing the first Witcher game. I think some old games just have issues with newer GPUs and CPUs in general.
I'm testing several games, not just one. Dishonored, Alien: Isolation, Mega Man 11 and a couple other things. They worked butter smooth with Vsync off in both control panel and game, but when I would look at a wall or something and get above 144fps I would see tearing. I googled about it and saw people say to turn Vsync on in the control panel and off in the games, so I did that, and now I have stutter.
Variable refresh rate stops working as soon as framerate exceeds monitor's max refresh rate.
Turn off vsync (in game and/or in GPU driver control panel) and use external framerate limiter (for example, RIvatuner Statistics Server)

Try to limit FPS 2-5 frames below your monitor's refresh rate, if tearing persists.
Enjoy tear-free image with no input delay (provided that vsync was turned off and game runs at exclusive fullscreen mode)
avatar
matrixdll: Variable refresh rate stops working as soon as framerate exceeds monitor's max refresh rate.
Turn off vsync (in game and/or in GPU driver control panel) and use external framerate limiter (for example, RIvatuner Statistics Server)
Yeah, I'm trying to avoid yet another program running but it seems like this is the solution. I'll mark it as such once I try it out. Thanks.
You can technically limit framerate globally for all applications via Nvidia Inspector program (i.e. the fps cap is done on a driver level - as soon as the setting is changed you don't need to run the Inspector application), but I've heard that method is somehow worse than RTSS by introducing slightly higher input delay.
Besides, RTSS has a footprint of merely 10MB of RAM and zero cycles used by CPU (you can go extra mile and block any incoming and outgoing traffic for it in firewall, just in case)