ED and the Oculus Rift Developers Kit 2 (DK2) Discussion Thread

Negligee-able.

Hey rifters, I have a question: I'm mostly getting judder in asteroid fields, is this a general problem like the station judder or would a hardware update help here?

Right now I have an overclocked i5 3570k, a GTX 680 and 8gb RAM and am running the game on a SSD. I'm basically thinking to get a 970 or two with my next paycheck, but I'm not sure if it would help in this case or if it's more Elite's fault and will be improved. Elite and the rift is pretty much the only reason to get an upgrade right now, so it would be nice to hear some other experiences with similar PCs.

I've got a Titan Z and still see some judder in the asteroid tutorial...I've tried about 60 different configs and nothing seems to make a whole lot of improvement, but a lot make it worse. 3D mode is pretty terrible and nothing I do can get the fps over 50 (settings on low, AA off). This is with the latest 'optimized' drivers.
 
Head tracking help please

Hi.

Just got my DK2 today. Everything seems fine except for head tracking. I'll try and be brief. Basically in direct mode I have an orange light on the rift and a blue one on the camera. During the config demo I can see the image on the main monitor and when i move the rift around in my hand you can clearly see the head tracking is working. However there is no display in the rift.

So onto extended mode, basically the opposite! Image works great in the rift but NO head tracking. Now I have a blue light on both the rift and the camera.

I can run ED in the rift though in extended mode I get no head tracking. Same for Assetto Corsa.

I've tried pretty much everything I can find through google. Has anyone else had a similar problem or is there a possibility that some part of the hardware is broken?

I've tried both HDMI and DVI. More worryingly I tried it on my sons PC who has very little installed on it and the same problem occurs. So I'm pretty sure I don't have any conflicts.

Actually I don't have a clue! Must say though that even without head tracking the experience is mind blowing. I spent nearly an hour flying around a platform marveling at the 3D and giggling like a 5 year old.

Any help here would be much appreciated.
 
When you mention direct mode is that using ED? ED has to be in extended mode, at the moment, so concentrate on that. Edit - Don't know why I missed that you said it was the Demo. Sorry. Adam is right, of course. Have you tried simply restarting? It's all pretty rough software so it's not unusual for it to work second time you try or after a restart.

What run time and firmware version are you using? You can see both in the config tool.
 
Last edited:
Get the demo working with blue lights first. See above poster. Then follow this:-


Install the 0.4.2 runtime from the OVR website.
Run the config tool.
Click tools, click advanced, click update firmware.
Update it to 2.12

Setup yourself as a user
Click advanced
Set your IPD.

Check the desk demo.

If OK change the rift to extended (Tools, Rift display mode, extended).

Go into either Nvidia control panel or Catalyst control panel and set the rift to portrait flipped and make sure it's set to 1080p and 75hz refresh rate.

Check that the desktop you can kinda see on the rift is the right way up and left is left and right is right.

Open E: D
Go into Graphics options.
Set the display to secondary, 1080p, 75hz.
Go to the 3D separation settings and select Oculus rift Speakers or headphones.
If you can't see these options try restarting the game.
Once you've set this option set everything to low settings and turn blur off.

Start the game, be amazed.
 
Last edited:
when beta 2.05 came out I found that occasionally head position tracking would stop working and I would have to restart the oculus service before it would work again. I now restart the service before I start playing.
 
I don't really understand, why the difference between oculus and non oculus is that big. Ok, for oculus the scene maybe has to be rendered twice, but the resolution per scene is only half the size. A shader for the image distortion and chromatic aberration should not be that slow.

It's because you're rendering 1182x1461 per eye, even though the display is 960 x 1080 per eye. You are rendering a larger distortion for the pixel image density and the lenses. So it's more intense than you thought. Also all that overdraw and draw calls have to be processed twice, once for each view. If you take the game CPU calculations out of the picture. Your GPU is rendering your game twice. That's why Ice and Asteroid fields are so bad, because there is so much overdraw, and draw calls that have to be processed by the GPU. If it's taxed with a normal monitor, it's twice with VR.
 
Who says constant checking never helps...

Just paid confirmed. No ship date, but verified full payment. 4 weeks and counting. Happy happy joy joy.
 
I've got a Titan Z and still see some judder in the asteroid tutorial...I've tried about 60 different configs and nothing seems to make a whole lot of improvement, but a lot make it worse. 3D mode is pretty terrible and nothing I do can get the fps over 50 (settings on low, AA off). This is with the latest 'optimized' drivers.
Ah thanks, I probably won't upgrade then for now.
 
It's not just me that gets that gauze effect over everything is it? I'm presuming its the pixels of the screen.

It's called the Screen Door Effect, and it is indeed the gaps between the pixels. It's basically because you've got a screen right in front of your face and you're looking at it through lenses which "zooms" in even more. There are things they can do to improve it (it's already way better than the DK1). CV1 should be another big step.
 
It's because you're rendering 1182x1461 per eye, even though the display is 960 x 1080 per eye. You are rendering a larger distortion for the pixel image density and the lenses. So it's more intense than you thought. Also all that overdraw and draw calls have to be processed twice, once for each view. If you take the game CPU calculations out of the picture. Your GPU is rendering your game twice. That's why Ice and Asteroid fields are so bad, because there is so much overdraw, and draw calls that have to be processed by the GPU. If it's taxed with a normal monitor, it's twice with VR.

Correct, but you may underestimate the overhead on the CPU when doing the second pass. All polys need to get sorted through their space partitioning algorithm before being passed on to the GPU again.

That's why we get people with "780 OC" doing bad on low, cause they run it with some god awful AMD CPU on 3.5Ghz and think it's enough.

It is not, please understand it already. People who recommend AMD CPUs for E : D with VR should shut up and not mislead other people.
 
Correct, but you may underestimate the overhead on the CPU when doing the second pass. All polys need to get sorted through their space partitioning algorithm before being passed on to the GPU again.

That's why we get people with "780 OC" doing bad on low, cause they run it with some god awful AMD CPU on 3.5Ghz and think it's enough.

It is not, please understand it already. People who recommend AMD CPUs for E : D with VR should shut up and not mislead other people.

The CPU'S aren't being taxed. There is very little load on the CPU's. MR INTEL.

I'm running a Zotac 980 Extreme Edition at 1545mhz and I get judder on anything other than low settings. Or maybe it's my god awful AMD 8350 Black Edition O/C to 5 ghz on all 8 cores.
 
Last edited:
Correct, but you may underestimate the overhead on the CPU when doing the second pass. All polys need to get sorted through their space partitioning algorithm before being passed on to the GPU again. That's why we get people with "780 OC" doing bad on low, cause they run it with some god awful AMD CPU on 3.5Ghz and think it's enough.It is not, please understand it already. People who recommend AMD CPUs for E : D with VR should shut up and not mislead other people.
Please explain (in detail) why you think AMD CPUs are in any way deficient for E: D compared to Intel ones? I'm willing to bet you can't. My AMD twin 7870s and 3.5Ghz AMD CPU runs E: D fine in the Rift. Others with AMD are also getting similarly good results. You should shut up and not try to turn this helpful thread into a pointless AMD vs Intel war. Both chips are good enough for VR if they are fast enough.
 
I have a single quad core i5 4460 @ 3.4Mhz and doesn't matter if everything is on max or low- I get the same results on 3d. It has a consistent 50% usage. I'm not sure that upgrading the CPU will make a whole lot of difference? My laptop has an 8-core i7 and I see the exact same stutter on it.
 
It's called the Screen Door Effect, and it is indeed the gaps between the pixels. It's basically because you've got a screen right in front of your face and you're looking at it through lenses which "zooms" in even more. There are things they can do to improve it (it's already way better than the DK1). CV1 should be another big step.

Ah k. I think it's possibly that causing the most nausea to me, that and straining my eyes trying to see any half decent detail out of the ship window.
 
Please explain (in detail) why you think AMD CPUs are in any way deficient for E: D compared to Intel ones? I'm willing to bet you can't. My AMD twin 7870s and 3.5Ghz AMD CPU runs E: D fine in the Rift. Others with AMD are also getting similarly good results. You should shut up and not try to turn this helpful thread into a pointless AMD vs Intel war. Both chips are good enough for VR if they are fast enough.

... this ;)
 
Does anyone have any idea how much work it would be for Frontier to get ED working in Direct to rift mode? Has it ever been mentioned?
 
Back
Top Bottom