Gsync not a pleasant experience below 55fps

[Phixsator]

Ive been through 3 Gsync monitors on 2 different nvidia cards and the experience is the same below around 55ish fps the image starts to look stuttery. if i force fps to 35 it looks more like 10 fps.. Granted no tearing and the inputs seems fairly responsive spite of this but it does my head in. Now heres the weirdest part. It seems to be related to or revealed when mouse panning. Let me explain(happens in all games)

example one:
FPS locked to 45, mouse looking around = image looking stuttery, controls are not stuttery though.

example two:
FPS Locked to 45, moving around using keyboard(slower changes in image) smooth as butter although alittle extra blurry compared to 60fps but thats to be expected.

Ived tried 3 different monitors, the ROG Swift(on nvidia 780 lightning), Acer XB270HU(on nvidia 980ti) and Dell S2716DG(on nvidia 980ti). Ived also tried several different settings, vsync off and on spite it shouldnt have any impact at all just to name 1, and loads of different drivers. I dont know if this is just normal or if im missing something? At first i was dissappointed at how blurry gsync was at lower fps but after getting an explanation on blur busters forum it made sense(image persistence) but the stuttering image i cannot find a reasonable explanation for. I would appreciate if someone could give me a hint to what is going on.

 

[Mauller]

did you try a different mouse?

 

[Phixsator]

did you try a different mouse?

Yes i have. I use a Razer Deathadder 2013 edition daily but also tried a Razer Taipan. Ive tried uninstalling Synapse(always disliked that app). Currently running without it.

 

[Mauller]

how about different display port cables?

 

[Phixsator]

how about different display port cables?

tried and done, no effect. Should say though that im more convinced it has something to do with using a mouse as ive just tested with an xbox controller and while the image is blurry at 45fps it is not stuttering one bit even when panning around extremely fast. Makes it a very weird issue.

 

[drunkenmaster]

I've never understood why people think it fixes everything at low frame rates. If you stand still in a point in game and spin around 360 degrees, what *-sync does is try to split the 360 degree into equal sized slices rather than very different size slices.

You can get a stuttering feel two ways in this scenario, where the slices are very different sizes, and where there are simply not enough slices. *-sync helps fix out the first type of stutter, it does absolutely nothing for the second type. The higher the framerate the more slices, the smoother the turn feels. Low framerate is itself a source of stutter. *-sync works best, IMHO, in the 70-144fps range.

 

[Kaapstad]

I've never understood why people think it fixes everything at low frame rates. If you stand still in a point in game and spin around 360 degrees, what *-sync does is try to split the 360 degree into equal sized slices rather than very different size slices.

You can get a stuttering feel two ways in this scenario, where the slices are very different sizes, and where there are simply not enough slices. *-sync helps fix out the first type of stutter, it does absolutely nothing for the second type. The higher the framerate the more slices, the smoother the turn feels. Low framerate is itself a source of stutter. *-sync works best, IMHO, in the 70-144fps range.

Interesting

That's a lot of money I have just saved by not getting an *-sync monitor.

 

[tommybhoy]

As above, low fps is low fps, but if I lock fps out with NV vsync I was getting the same thing your describing on FO4 and secondary non GS display connected, but luckily FO4 was sorted with a patch and don't use dual displays(TV is for vids/light gaming only), everything else is smooth as long as I run in game vsync off, nvcp vsync on without any 3rd party fps limiters.

 

[Mauller]

I've never understood why people think it fixes everything at low frame rates. If you stand still in a point in game and spin around 360 degrees, what *-sync does is try to split the 360 degree into equal sized slices rather than very different size slices.

You can get a stuttering feel two ways in this scenario, where the slices are very different sizes, and where there are simply not enough slices. *-sync helps fix out the first type of stutter, it does absolutely nothing for the second type. The higher the framerate the more slices, the smoother the turn feels. Low framerate is itself a source of stutter. *-sync works best, IMHO, in the 70-144fps range.

Not saying that you said it. But in the past a lot of people were bigging up gsync and how it would help at bellow 60 fps. And how their gaming was now butter smooth when it dipped bellow 60.

Just amused me that you said the decent range for syncng monitors is over 70fps when it was made to reduce stutter and screen tear bellow 60.

 

[Phixsator]

I've never understood why people think it fixes everything at low frame rates. If you stand still in a point in game and spin around 360 degrees, what *-sync does is try to split the 360 degree into equal sized slices rather than very different size slices.

You can get a stuttering feel two ways in this scenario, where the slices are very different sizes, and where there are simply not enough slices. *-sync helps fix out the first type of stutter, it does absolutely nothing for the second type. The higher the framerate the more slices, the smoother the turn feels. Low framerate is itself a source of stutter. *-sync works best, IMHO, in the 70-144fps range.

For once i totally disagree with you. It seems to me you just read gsync and went on a smaller, although harmless, offensive. You completely missed the point of this post. Let me clarify, panning extremely fast with an xbox controller at 45 fps yields no stuttering at all but ofcourse the image is extremely blurred due to image persistence. Panning much slower with a mouse gives me stuttering at 45 or 54 fps anything really under 55. So i hope you can see that your point is invalid here. Please dont mistake me for another nvidia fanboy, g-sync has surely been hyped more than its worth but this isn't about g-syncs shortcomings but about a technical error im experiencing and one that i would like resolved and it has nothing to do with g-syncs features or lack there off.

 

[Mauller]

here is a thought, what is the polling rate set to on your mice? maybe if you try 500hz instead of 1000 or 250?

does this happen in every game or just a specific one?

 

[Phixsator]

here is a thought, what is the polling rate set to on your mice? maybe if you try 500hz instead of 1000 or 250?

does this happen in every game or just a specific one?

Its a good thought, i have been messing with polling rate and it does have an affect but no settings removes the issue, it seems the lower the rate the worse the problem. It happens in all games.

 

[Mauller]

how about outside of games? do you notice the cursor jittering as it moves? it could be the surface you are using your mice on. maybe try something else? i would also disable and mouse acceleration in the razer synapse.

 

[Phixsator]

how about outside of games? do you notice the cursor jittering as it moves? it could be the surface you are using your mice on. maybe try something else? i would also disable and mouse acceleration in the razer synapse.

all 3 mouse ive tried, razer taipan - deathadder 2013 - ms explorer 3.0, works perfectly outside of games. They also works perfectly inside games when the games run than 55-60 fps. All mouse accelleration is turned off everywhere as i hate that.

 

[Perfect_Chaos]

Am currently stuck on my laptop at the mo, but going back to a 60hz screen and 40-60fps in medium/fast paced games like FPS's i noticed a big difference over my 120hz 1080p screen.. Really wouldn't go back to 60hz myself now. Seems I'm not missing out on much without Gsync/Freesync either, just need to drive the high frame rates with a high refresh screen.

The hertz jump seems to be the biggest thing rather than the sync technologies i guess.

 

[smogsy]

I've never understood why people think it fixes everything at low frame rates. If you stand still in a point in game and spin around 360 degrees, what *-sync does is try to split the 360 degree into equal sized slices rather than very different size slices.

You can get a stuttering feel two ways in this scenario, where the slices are very different sizes, and where there are simply not enough slices. *-sync helps fix out the first type of stutter, it does absolutely nothing for the second type. The higher the framerate the more slices, the smoother the turn feels. Low framerate is itself a source of stutter. *-sync works best, IMHO, in the 70-144fps range.

Gsync works best 50+. In my experience testing on 1440p and 4K.
Low framerate does lessen the experience that's why gsync doubles frames to give a smoother experience.

 

[andybird123]

Just one thing, have you checked vsync is OFF in game? It should always be set to off in game.

 

[Phixsator]

Gsync works best 50+. In my experience testing on 1440p and 4K.
Low framerate does lessen the experience that's why gsync doubles frames to give a smoother experience.

Frame doubling on my current monitor doesnt happen until you go below 30-32 to the best of my knowledge(its the same panel as the ROG swift which was tested by pcper to double at 31-32). Also the thing is the experience is smooth when using a controller even during fast panning where as its stuttery as **** when using a mouse even during slow pannings.

Just one thing, have you checked vsync is OFF in game? It should always be set to off in game.

Yes vsync is set to off in all games. Thanks for the idea though.

 

[Panos]

Just one thing, have you checked vsync is OFF in game? It should always be set to off in game.

+1

Same applies to Freesync.
VSYNC always off.

The 2730Z Freesync band starts are 40 fps, while atm barely any game goes bellow 65 on max settings, I do not remember ever having the issue drunkenmaster described when Freesync is working.
And given the tech is exactly the same, a Gsync monitor shouldn't have that issue either.

Also I tried it tonight on TESO. lowered the fps to 45 cap and tried to turn around the mouse. Nothing. Everything is smooth. At 120fps is even smoother.
But you have to rotate many times and look very closely to see any difference at all with Freesync ON.

With Freesync OFF whole world breaks loose at 45fps or at 60fps for that matter. Even simple straight move feels crap bellow ~70fps

 

[Panos]

Ive been through 3 Gsync monitors on 2 different nvidia cards and the experience is the same below around 55ish fps the image starts to look stuttery. if i force fps to 35 it looks more like 10 fps.. Granted no tearing and the inputs seems fairly responsive spite of this but it does my head in. Now heres the weirdest part. It seems to be related to or revealed when mouse panning. Let me explain(happens in all games)

example one:
FPS locked to 45, mouse looking around = image looking stuttery, controls are not stuttery though.

example two:
FPS Locked to 45, moving around using keyboard(slower changes in image) smooth as butter although alittle extra blurry compared to 60fps but thats to be expected.

Ived tried 3 different monitors, the ROG Swift(on nvidia 780 lightning), Acer XB270HU(on nvidia 980ti) and Dell S2716DG(on nvidia 980ti). Ived also tried several different settings, vsync off and on spite it shouldnt have any impact at all just to name 1, and loads of different drivers. I dont know if this is just normal or if im missing something? At first i was dissappointed at how blurry gsync was at lower fps but after getting an explanation on blur busters forum it made sense(image persistence) but the stuttering image i cannot find a reasonable explanation for. I would appreciate if someone could give me a hint to what is going on.

You have a GTX980Ti and you force the fps to 55 at 2560x1440? Why?
Let it run free.
Also, I do not know if it automatic or manual for Nvidia, but on the drivers have you checked if Gsync is ON?
AMD pops up a message when sees a Freesync monitor and you have to activate it. It doesn't work by default.