Recent Nvidia Drivers are the cause of your hitching/stuttering in games.

Any program, any service running in OS can query for a change of the timer resolution.
Utility pwrtest (https://msdn.microsoft.com/en-us/library/windows/hardware/dn613984(v=vs.85).aspx) can show what processes did query such change.

 

Reporting back to say the new nvidia drivers are okay..

I figured out the hitching and stuttering with ground zeroes. Apparently its caused because of fullscreen mode.

On borderless its perfect so far. stress tested and its okay. older drivers such as 347.25 fullscreen works. i believe this may work for the phantom pain.

will try witcher 3 soon

 

Interesting. How are you playing in fullscreen? Vsync is on in the application?

Checked another machine and the result is the same but current timer is at the maximum value.

 

Tested with vsync on and off. In application and in nvidia cp. it doesn't make a difference.

In full screen, there is frame hitching/stuttering which happens randomly. But in border less full screen with vsync on in mgs v options. It's perfect.

No frame hitching.

 

This has been a known driver issue in the past @ windows8 or even windows7.. Something with fullscreen framebuffer and how the driver grabs its buffer when it starts the game.

 

http://forums.guru3d.com/showthread.php?t=403144

 

I was testing today the new Barcelona track for Assetto Corsa and man it was stuttery, fortunately setting pre-render frames to 1 fixes most of it, not perfect but playable. I didn´t need to do this months ago when I stopped playing this game.

Also you guys remember the stuttering bug in fear 3?, devs had to work directly with nvidia in order to fix it... it seems to be a long time issue in drivers. :bang:

 

It says gsync monitor but i dont have that anymore but ill try to be optimistic and believe its to fix this also. Downloading and will test and report back.

EDIT

Issue still exists. When running mgs v in full screen mode you get very odd frame hitching/stutter. The audio never stutters, just the video.

Apparently, borderless fullscreen resolves this.

 

Well, it actually should. What if you force triple buffering in fullscreen mode as well?

I.e. what I would do is set in game vsync to off, set CP's vsync to always on and TB to on and see if that helps.

Running in a borderless window means that you're running a triple buffered (I think) vsynced to a desktop refresh rate window.

 

control panel TB is openGL only still, unless something changed that i've missed.

 

Of course is OpenGL only, there's NO "Triple Buffering" (strictly speaking) in D3D, only a way to "emulate" it.

http://www.gamedev.net/topic/649174-why-directx-doesnt-implement-triple-buffering/

 

DirectX already uses triple buffering via the read ahead queue. The only thing it lacks when compared to OpenGL's method is the ability to drop frames, resulting in a bit of input lag.

http://www.anandtech.com/show/2794/4

 

Don't know how I forgot this, sorry.

There certainly is a way to use TB in DX. There's even a way of forcing it but I'm not sure if that's possible in DX10+.

 

Tried WRC 5 now that it can work at more than 59Hz, nah, same thing, constant ugly stuttering "Soma style" in full screen. In borderless windows it´s so much better but the bugger still shows randomly. So far no word from nvidia.

 

and where is nvidia confirmation about it?

there are lots of reports that people got more stable fps in direct x/d3d games when they turned on triple buffering in nvcp also.

so it's all based on guessing, but no official confirmation.

 

not true...

older drivers on same system/OS = older games work without issues.

 

Guessing? You can say that, still "triple buffering" is an OpenGL concept.

 

You can force it through D3DOverrider in DX11 too, but not in Win10.

Still it's a frame queue management that mimics the "triple buffering" principle, sure, but it's not the original OpenGL "triple buffering".

 

Yes only in the witcher 3 but 1 frame render slove the problem

 

Don't mean anything. Newer drivers may lack some hacks/fixes introduced in the older ones for these games specifically because these hacks doesn't work anymore in Win10 or conflict with some new optimization for actual games. It's still the application issue in this case as this hack was fixing something which was broken in the game, not the driver. Lots of possibilities.

"Triple buffering" means that there are (at least) three frames stored in the frame buffer: the one shown, the one which will be shown after the current one and the one which the app is building right now. This "concept" is perfectly fine in its functioning in DX or OGL or whatever API you may think of. How it's actually called in what API don't matter.