Causes of Judder

memory over commitment, if at any time you are close to a limit, the OS is happy to insert big stalls to defrag memory, paging stuff, unpaging stuff, etc.

How much vram is a GTX 760 ?

galopin said:

memory over commitment, if at any time you are close to a limit, the OS is happy to insert big stalls to defrag memory, paging stuff, unpaging stuff, etc.

How much vram is a GTX 760 ?

2GB
is there anything that can be done about this?

2GB
is there anything that can be done about this?

Of course : http://www.amazon.com/EVGA-GeForce-GAMING-Graphics-12G-P4-2992-KR/dp/B00UXTN5P0/ref=sr_1_2?s=pc&ie=UTF8&qid=1459304325&sr=1-2&keywords=gtx+titan+x

Seriously, 2GB is very short for a game that need something slighty above 1080p in term of memory, unless there is drastic graphic options to reduce the memory load, like texture quality, resolution, etc.

galopin said:

2GB
is there anything that can be done about this?

Of course : http://www.amazon.com/EVGA-GeForce-GAMING-Graphics-12G-P4-2992-KR/dp/B00UXTN5P0/ref=sr_1_2?s=pc&ie=UTF8&qid=1459304325&sr=1-2&keywords=gtx+titan+x

Seriously, 2GB is very short for a game that need something slighty above 1080p in term of memory, unless there is drastic graphic options to reduce the memory load, like texture quality, resolution, etc.

I was planning on upgrading once my shipping notification for the CV1 came in, I was hoping my 760 would suffice with the DK2 until then. I was thinking 980 or 980Ti but I was hoping the next generation of cards would come out before I upgraded. 

Some more information about the juddering. It only occurs with head movement, when I was testing, I was basically sweeping my head in a figure 8.
I'm completely judder free in lucky's tale
it was juddering earlier in dreamdeck, but it wasn't just now in my last test.
trying to watch one of my movies in the video app judders pretty bad, which is weird since that shouldn't really be that strenuous no?

I overclocked my GPU and my skydiver score went from 16500 to 17800 in the sky diver benchmark in 3Dmark. a rift spec pc is listed as 22000. 

When in rift apps and games my GPU usage still maxes out in the lower 80% range, my memory usage is pretty close to the 2gb max of my card in some apps so that may be the issue. I'll do some more testing tomorrow and keep a closer eye on the GPU memory usage as I haven't been watching it closely until now. 

Alright I don't believe GPU memory to be the issue.
I just ran through a couple apps quick testing for judder.
dreamdeck, was pretty smooth with the odd judder
lucky's tale, no judder at all
oculus video, watching a movie from my drive, judder like crazy in all theaters except the Void theater which ran smooth.

Throughout the entire test my GPU memory usage maxed out at 1670Mb which is obviously below 2Gb, so this is not the issue causing the judder. 

Anybody have any ideas or things I should look for?

Judder is caused when the compositor ends up not completing it's work in time before the next v-sync.  ATW functions because the new nVidia drivers are able to set a higher priority to the compositor context than to other rendering contexts.  That means that if the compositor has work to do it takes priority over any other rendering, but with caveats.  

First off, the GPU can't simply suspend a draw call, so if you have long running draw calls, these can cause the compositor to be late, thus causing judder.  If you're using enough texture memory that the GPU needs to do page swapping on each frame, transferring memory in from the CPU, then that will also cause judder.  If the GPU is running hot (close to 100%) then this will also cause the compositor to be late.  Note that it doesn't necessarily show as 100% in a monitor because it might be running at 60% with occasional spikes to 100%, and most monitors will only show you the aggregate usage over a number of frames, so they'll show some number between 60 and 100 percent.  

jherico said:

Judder is caused when the compositor ends up not completing it's work in time before the next v-sync.  ATW functions because the new nVidia drivers are able to set a higher priority to the compositor context than to other rendering contexts.  That means that if the compositor has work to do it takes priority over any other rendering, but with caveats.  

First off, the GPU can't simply suspend a draw call, so if you have long running draw calls, these can cause the compositor to be late, thus causing judder.  If you're using enough texture memory that the GPU needs to do page swapping on each frame, transferring memory in from the CPU, then that will also cause judder.  If the GPU is running hot (close to 100%) then this will also cause the compositor to be late.  Note that it doesn't necessarily show as 100% in a monitor because it might be running at 60% with occasional spikes to 100%, and most monitors will only show you the aggregate usage over a number of frames, so they'll show some number between 60 and 100 percent.  

Thanks for the response

So this basically means that even though the GPU may not be showing 100% usage or memory usage it could still be the issue?
Are there any tests that can be done to confirm the issue?
Also any settings or optimization a that can be done to eliminate/ reduce the judder? Or is the only solution a new more powerful GPU?

why would the same program run smooth some times and judder consistently other times?

Judders are some of the most frustrating things to diagnosis. You are in the dev forum, how skillful are you ? Because the only real way to decipher is to use gpuview ( a microsoft tool ), but it is far from simple.

galopin said:

Judders are some of the most frustrating things to diagnosis. You are in the dev forum, how skillful are you ? Because the only real way to decipher is to use gpuview ( a microsoft tool ), but it is far from simple.

I'm nowhere near a dev skill level but I'm not useless and I'm a fairly quick learner.