Status of SDK, judder fixes, direct to rift fixes etc...?

Hi

So what is the official Occulus answer to this judder issue that spreads on more and more demos please ?
thanks

cyril

Its mainly due to setup issues if you aren't getting 75 FPS you're going to get judder. Make sure you have Vsync on and you have your rift set to primary moniter and then check your FPS in the game. If you are getting 60 than its not picking up with rift as your main display and matching your main screen's display refresh. There are some problems yes but on my own projects judder is non existent.

Run the tuscany demo and push space bar and look at your FPS. any less than 75 and your machine is too slow and you'll get judder.

Thanks

According to you what is the low level for the graphics board to reach these 75 fps ?

Is it more CPU related or 3d board related?

I have a GTX 650 Ti which is not the fastest 3d board !

cyril

There is no definitive answer to that question.... On the exact same hardware, You can render a 3d spinning cube in an empty scene at 1000 fps or something complex like Star Citizen (or any other modern game) at 20 fps... It all depends on how complex the scene is...

You'll be hard pressed to run much at 75fps with your video card. I had a gtx 650 and was able to get very little to run at 75FPS so I bought a GTX 770. That and a lot of the games people are trying to play aren't necessarily well optimized to VR.
Also depending on your CPU you may consider upgrading that was well. There in lies your problem though it's not the problem with the DK2 SDK

Hi

it really has something to do with the way you programm. Take for example DREADHALLS 1.3 that has this judder even in the first room with almost no geometry in front of you (unless there is no occlusion culling which I doubt).

if you take timeRifter DK2 the geometry is much more complex and... no judder !

Cyril

How you program and what exactly you are loading in.

At the end of the day you are either drawing twice for each eye or drawing in one program and it being copied into a "connector" that splits the draw for the eyes.

So effectively whatever normal framerate you get is cut by normally a third or in extreme cases by half.

I'm getting the judder issue too. When I first got the rift I was able to play the battle of endor demo perfectly. Since messing around with various demos, extended mode etc I now get the annoying judder problem.
It's definitely not an FPS problem as it is perfect if I look straight ahead or move my head and up and down.

As soon as I look left and right it's really bad. I uninstalled all Nvidia drivers, Oculus runtime with reboots between each one, deleting the Nvidia folders left but still no luck.

I get that some people say you need to change the settings for Vsync, and yeah thats fine for extended mode stuff where you can make changes in the Nvidia setup but direct stuff doesn't seem to want to play ball, although some stuff is fine like the red of paw demo, then again elite which works on extended which runs fine at 75fps has the issue also.

With the cyberspace demo when you run it you get to tell it which display to run on which for me is display 2 to the right of my main screen, I get really bad juddering then, if I make the rift my main screen before launching and still use the display 2 it works ok.

With the main screen running at 60Hz some people have said it will make the rift run at 60 also? But then some demos work perfectly. Meh beta hardware :D

I think most of the judder problem is in the devs hands. In some games I get judder even on low settings, even if I get a solid 75 FPS on higher settings. I also found a thread on Reddit where they are trying to rule out what's causing judder.

http://www.reddit.com/r/oculus/comments/2csbxg/lets_get_to_the_bottom_of_this_judder_problem/

Everyone, including myself, gets judder in DX11, so it's possible that DX11 is one of many reasons to why we get judder. Some are also speculating that the camera is what's causing the judder, since it only appears when you're moving your head. A syncing problem perhaps?

I'm sure whatever it is that we'll get to the bottom of it sooner or later. The DK2 has only been out for nearly 2 months and some games are working better already compared to a month ago. Hopefully most games will have direct mode support soon, and that might also bring this annoying judder to an end.