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

Didn't get anytime to play with the SDK this morning although in the tool menu there is the options to pause service, tried with ED and worked, bar the usual juddering, even on low, must be my pants card!

Also what's the effect where when moving your head, you get a really obvious double image? As if the image is separated apart by a few pixels?
 

SlackR

Banned
Yeah, you're missing the fact he's running the game without positional tracking, because he has a CPU without SSE4.1 instructions.

Doesnt this new SDK patch solve this problem?

# in Bruges for a few days with the missus so no DK2 to try this new patch on :(
 
Last edited:
Didn't get anytime to play with the SDK this morning although in the tool menu there is the options to pause service, tried with ED and worked, bar the usual juddering, even on low, must be my pants card!

Also what's the effect where when moving your head, you get a really obvious double image? As if the image is separated apart by a few pixels?

I think it is just a really extreme example of the juddering. I had it last night when my FR tanked for some unknown reason. Restarted ED and it was fine.
 
So It's just a matter of waiting for FD to recompile Elite for the new SDK to (hopefully) eliminate juddering..? :smilie:

That and improving performance in stations and ring systems to remove juddering due to droopy frame rates.
Not sure how much Direct mode and timewarping are going to alleviate the judder.
 

Sir.Tj

The Moderator who shall not be Blamed....
Volunteer Moderator
Not going to get the chance to download the SDK update for a while (Thanks to you lot keeping us poor mods so busy. :D) I'll be interested in knowing if it makes any improvments to the game.
 
I think it is just a really extreme example of the juddering. I had it last night when my FR tanked for some unknown reason. Restarted ED and it was fine.

ah no probs =]
Will keep an eye out for a more affordable graphics card, and wait for an update, (Or sit really still!)
 
Not going to get the chance to download the SDK update for a while (Thanks to you lot keeping us poor mods so busy. :D) I'll be interested in knowing if it makes any improvments to the game.

I'll be trying it tonight after work.
Will report back if no one else does.
 
Didn't get anytime to play with the SDK this morning although in the tool menu there is the options to pause service, tried with ED and worked, bar the usual juddering, even on low, must be my pants card!

Also what's the effect where when moving your head, you get a really obvious double image? As if the image is separated apart by a few pixels?

Sounds a bit like screen tearing. On the rift, screen tearing presents itself as a vertical line, not horizontal, as the screen scans from left to right, not top to bottom. This happens when Vsync isn't enabled.

Make sure you've disabled Aero as a first port of call (choose a basic theme for windows). Other than that you may have to try various other options to force vsync in the game (radeonpro, nvidia control panel, etc).
 
Ive tested the new update, as far as I can see there are no improvements in fps. The Direct to HMD game demos still show stuttering and or vertical screen tears on my system. Extend to Desktop ALL demos run fine. So no big improvement I can spot at all.

i5 Haswell@4.4
RoG Maximus Vii
780Ti
Avexir Blitz 2133C9 Ram
HyperX SSD's
 
No head tracking with processes running, so you still need to shut down wscript.exe and OVRService_x64.exe or Use the pause services option in the Oculus Config Utility.
 
Last edited:
I hear that the OR config utility is a bit of a CPU hog.
Someone said it was taking up a full core so it's probably worth closing it down when running E: D. Not tested it myself so can't say for sure.
Not sure if the new runtime is any better either.
 
Dont be too quick to upgrade to a new graphics card.

From reading everyone's posts, its seems that people are having the same problems (low fps and judder in stations / asteroid fields) whatever system specs they have.

I have a (Mid range?) AMD R9 270x and an I5 processor and it seems I am getting similar frame rates to the people with I7 and GTX780. In space I get no judder (and for some reason the colour aberration seems to have almost gone, must recheck the changes I made in the graphics settings)

My point is, I think its best to wait for Oculus and Frontier to optimise their software before trying to solve any problems with hardware upgrades (unless of course you are running a very under powered system)
 
Last night till well after bed time tired to setup rift.
Downloaded config utility camera responds till sees headset. Process closes and it repeats that. The demo button is grayed out. Do I need the sdk too. Will ED run with tracking as you have to kill this process. Sorry bit garbled as on phone.
Anyone else having camera problems. Any help greatly appreciated.
 
Last night till well after bed time tired to setup rift.
Downloaded config utility camera responds till sees headset. Process closes and it repeats that. The demo button is grayed out. Do I need the sdk too. Will ED run with tracking as you have to kill this process. Sorry bit garbled as on phone.
Anyone else having camera problems. Any help greatly appreciated.

Follow these steps.
Unplug the rift and camera.
Uninstall everything OR related you've installed so far.
Download and install the new OR runtime (you don't need the SDK unless you're developing).
Once it's installed plug the OR and camera back in
Open the config tool.
Hopefully you will see that the DK2 is detected (if not make sure the orange light on top of it is on, if not try turning it on).
If you still don't see it's detected try swapping which USB port it goes into. Make sure you've plugged the HDMI cable into your GPU and not your onboard iGPU (should be lower down at the back of your PC if you have a desktop not near the top where most of the connections are located, you've no choice I think with laptops).
Update the fireware of the rift, I think it's an option in tools.
Once updated make sure you setup a profile for yourself in the bottom section of the config tool.
Run through the IPD measurement process with the green bars to set your IPD.
Once all this is done then run the room test demo from the config tool.
You should see a desk with stuff on it etc..

Check everything works AOK in there. Things should look solid, not blurry and no chromatic aberration (colour halos around stuff).
If you don't get positional tracking double check that you've plugged the camera into the PC (via the usb cable into a USB 2.0 socket (should be black not blue) ) and the headphone esque cable is plugged into the signal box (small box near the end of the cables that come from the headset).
If it doesn't seem solid or it's blurry or you see a ton of chromatic aberration then you've messed up your IPD settings so redo them.

Once everything is hunky dory diddly ory in the desk demo then you should be good to go.

Go into the display options in the config tool and select Extended rather than Direct. You'll know this is working as you will see two monitors in your Windows/Nividia/AMD display settings and you should be seeing your desktop on the rift. If you don't see this then it must still be on Direct mode or turned off.

Go into your Nvidia/AMD display settings and if needs be rotate the display, check that the desktop is the right way round. Ensure it's set to the correct resolution and refresh rate (75hz).

Download and install this
http://www.theriftarcade.com/1-click-tool-released-for-running-sdk-0-3-games-on-the-oculus-rift-dk2/

Open it and Click stop service and stop Aero.
The config tool should shut down.

Open Elite Dangerous

Go to graphics settings

Select display 2 from the drop down menu, check that the res is 1080p and the refresh rate is 75hz. Select the Oculus headphones or speakers option depending on your sound setup, Select low settings in the graphic options.
Click apply and you should now see E: D on the DK2.

Load in Single player and check everything is working OK.
If you get a lot of Judder then try flying out to open space and checking it there.

Took me about 10 minutes from receiving the DK2 to playing E: D on it.
 
Last edited:
Thanks rift fine its camera. Will follow these steps. Didn't realise it was a new runtime thought just sdk....ok thanks again

If the desk demo works ok then it's not the actual camera at fault.
If it's just not working in Elite then I think it's that you are not stopping the service properly.
Use the tool, it's easier.

p.s. if you've never run the config tool at all it's worth following the steps from that point
 
Back
Top Bottom