FPS judder issue

[Heavenswake]

Ever since upgrading to a 144hz/Gsync monitor I noticed that most of my games have a slight judder about them. If I were to focus on a lamp post and run side to side it won't go smoothly across the screen, it will twitch/stutter slightly every few seconds despite being 60+ and even maxing out at 144 FPS it still happens. This happens in, but not limited to: WoW, CoD BO3, Dragons Dogma: DA, Overwatch, H1Z1, Borderlands 2. During normal play I don't really notice it since it's not a strong judder/stutter but I know it's there and would like to fix it.

At first I thought it was my monitor but I think it's something within my PC. If I run a Unigine Valley benchmark everything is smooth, I don't notice any kind of judder like I do in games. Which leads me to think it might be my CPU? Or some kind of conflict.

 

PC specs:

Windows 10 Pro

Acer XB270HU 144hz/Gsync (D. Port) + Monoprice Zero G Slim 60hz/non Gsync (DVI)

4670k, normally I have it OCed to 4.4 but turned it off for testing

16GB 2133 Corsair Vengence RAM

980ti Gigabyte G1

650W EVGA SuperNova Gold+

Asus Maximus VI Hero

2 250GB SSDs, Samsung 840 EVO and Crucial M500

 

Things I have tried:

Different drivers, probably like 10+

Fresh OS install

RMAed Motherboard (was having RAM issues, replaced RAM before mobo to rule out the sticks themselves)

Different NCP settings.

Used the G-Sync monitor by itself.

 

I'm just not sure why it doesn't show up in benchmarks but it does in games. I think the only game I haven't seen it in is Tomb Raider.

[GM_Peka]

If you haven't got gsync enabled, judder is normal, it's caused by the frame rate and refresh rate not dividing into each other evenly. if your monitor is running at 120hz and your frame rate is 90, every other frame will need 2 monitor refresh cycles and the other half of frames only need 1, this causes the judder effect, it's stopped by using gsync because then each frame gets its own refresh (ie 74 fps would give 74hz), so you get perfect frame pacing.

 

The funny thing is, the judder is actually more noticeable the lower your frame rate and refresh rate (again, assuming there's no gsync involved) so it's funny you only just are noticing it at 144hz

[App4that]

It might be your CPU, sorry.

[GM_Peka]

The only thing I can think, is do you actually have gsync enabled, cause this behavior is standard when no gsync is around.

 

I get the feeling you're using regular vsync.

[PlayStation 2]

1 minute ago, App4that said:

It might be your CPU, sorry.

I agree but I don't think it would really affect Borderlands 2.

[App4that]

Just now, Dan Castellaneta said:

I agree but I don't think it would really affect Borderlands 2.

That games a wild card because Windows 10 doesn't like it. But you could set a fps limit while playing it to see.

[GM_Peka]

I have no idea why people think this could be a CPU issue, what you described is normal behavior when using no frame sync or regular vsync.

[App4that]

Just now, Pvt. 8Ball said:

I have no idea why people think this could be a CPU issue, what you described is normal behavior when using no frame sync or regular vsync.

I suffer no such issue.

[GM_Peka]

2 minutes ago, App4that said:

I suffer no such issue.

Probably because you don't notice it, it's LITERALLY how vsync works OP said it was minor and only noticing when he's specifically looking for it, which is about right. If you want you can watch Tom Peterson's 40 minute long video on gsync, where he explains why the judder effect happens. Or you could just take my word for it.

 

The only way to remove the judder effect is to play your games at a perfect locked 60/120/144 fps (depending on refresh rate) with vsync on, or use gsync/freesync.

[GM_Peka]

4 minutes ago, App4that said:

I suffer no such issue.

Look at this:

http://www.testufo.com/#test=stutter

Kinda simulates what the judder effect is like, and what gsync is like.

Just cycle through the demos

[App4that]

Just now, Pvt. 8Ball said:

Probably because you don't notice it, it's LITERALLY how vsync works OP said it was minor and only noticing when he's specifically looking for it, which is about right. If you want you can watch Tom Peterson's 40 minute long video on gsync, where he explains why the judder effect happens. Or you could just take my word for it.

I'm familiar with it. I called my 390 Michal J. And a i5 will make the problem MUCH worse. Which is why I said cap the fps. If it's the CPU, nothing will work but lightening the load, if its something else it will minimize.

[GM_Peka]

9 minutes ago, App4that said:

I'm familiar with it. I called my 390 Michal J. And a i5 will make the problem MUCH worse. Which is why I said cap the fps. If it's the CPU, nothing will work but lightening the load, if its something else it will minimize.

You are literally giving me a brain aneurysm, I'm just going to go now.

[App4that]

1 minute ago, Pvt. 8Ball said:

You are literally hurting my head, I'm just going to go now.

I did no such thing. I wrote about the i5 causing a disparity in their system. Good day sir.

 

 

I said good day!

[Heavenswake]

The way I have Gsync set up in the NCP is as follows:

 

Max Pre0rendered frames: 1

Monitor Tech: G Sync

Preferred refresh rate: Highest Available

Vsync: On

 

Ingame I disable Vsync and make sure to uncap FPS if there is a limiter. 

 

I have tried turning Vsync off in the NCP (even though they say it needs to be on there) and all it does is introduce tearing which makes me think it disables gsync entirely.

 

I feel (though I'm unsure) like it's a PC issue.  I can feel gsync working in GPU benchmarks and everything works as advertised.  But in actual games it's juddery.  I've even turned on the "Gsync indicator overlay" so that I could see if Gsync was infact on during games.  If gsync off was the problem wouldn't I see the judders in benchmarks as well?

[App4that]

6 minutes ago, Heavenswake said:

The way I have Gsync set up in the NCP is as follows:

 

Max Pre0rendered frames: 1

Monitor Tech: G Sync

Preferred refresh rate: Highest Available

Vsync: On

 

Ingame I disable Vsync and make sure to uncap FPS if there is a limiter. 

 

I have tried turning Vsync off in the NCP (even though they say it needs to be on there) and all it does is introduce tearing which makes me think it disables gsync entirely.

 

I feel (though I'm unsure) like it's a PC issue.  I can feel gsync working in GPU benchmarks and everything works as advertised.  But in actual games it's juddery.  I've even turned on the "Gsync indicator overlay" so that I could see if Gsync was infact on during games.  If gsync off was the problem wouldn't I see the judders in benchmarks as well?

Try capping your fps to 30. If it goes away then the CPU is likely the cause.

[Heavenswake]

Did a quick little test in WoW.  Flying around with my FPS bouncing between 140-144 it's pretty noticeable.  Capping my FPS to 120 (and staying at max 120 FPS the whole time) it's less noticeable but still here.  Capping at 60 feels like it does on 120.  And capping at 30 is a stuttterfest, but I heard that's what gsync does when fps gets that low.

[App4that]

46 minutes ago, Heavenswake said:

Did a quick little test in WoW.  Flying around with my FPS bouncing between 140-144 it's pretty noticeable.  Capping my FPS to 120 (and staying at max 120 FPS the whole time) it's less noticeable but still here.  Capping at 60 feels like it does on 120.  And capping at 30 is a stuttterfest, but I heard that's what gsync does when fps gets that low.

OK, good information. So the CPU shouldn't be the issue. If you're running PrecisionX, don't use the graph. If you were, try again without it open.

[Heavenswake]

MSI afterburner and Rivia tuner to cap fps

[App4that]

2 minutes ago, Heavenswake said:

MSI afterburner and Rivia tuner to cap fps

I've never personally experienced an issue with Rivia, but Jay advises against it as it can cause issues. You don't have to uninstall it to see if it's causing an issue. Just turn it off in the settings. How to do so is covered here.

 

 

 

[GM_Peka]

I'm back now, so, from what you've said, I highly doubt gsync is working/enabled, I noticed you have two monitors so maybe that's the issue, also if you're playing borderless windowed, that can cause gsync not to enable even if you set it to work on windowed games. So try making sure your games are on proper fullscreen, and not just fullscreen windowed.

An easy way to check if gsync is working is when your are at a low FPS, your cursor should update at a slower rate, since your cursor position updates with your refresh rate, regardless of your fps (assuming you aren't using a software cursor).

 

Sometimes, gsync will not active at all even when it's enabled, so you gotta tick it off, press apply, then tick it back on, then press apply.

[GM_Peka]

Just making sure but,

https://i.imgur.com/rHcjj9x.png

is that enabled?

 

And is Monitor Technology set to gsync aswell?

http://i.imgur.com/ccCYrgB.jpg

[Heavenswake]

Been busy with a lot of stuff.  I can confirm monitor tech is set to g-sync and it is enabled for fullscreen + borderless (though having fullscreen by it makes no difference in my situation).

 

I feel like it has to be PC related though, like I said I can run Valley Benchmark with no stuttering whatsoever even down to 45FPS.  But games stutter, getting worse the lower the FPS is. 

 

Just speculation on my end, but it seems more CPU intensive areas get more stuttering.

 

Edit: Also disabling/uninstalling afterburner and RT made no difference.

 

Edit 2: Can also confirm the stuttering is worse if I disable gsync entirely.  So it's doing something but there is still slight stuttering.