How to get the DK2 working

Using 8.1 with the DK2 last night and head tracking worked without any problems. I followed the step guide posted earlier in this thread. However, quiting and starting the game again led to some real problems getting the OR display to work.

Have to say OR is damned impressive but, until the DK2 support rolls out (1.03 please :smilie:) I'll be going back to the standard display, just because there's too much to learn in the Beta right now!

Hopefully the devs will have an update soon.
 
Has anyone found a way to keep mouse control from accidentally swiching back to your other desktop? I don't see a way to lock mouse control to the Rift's desktop/window.
 
Has anyone found a way to keep mouse control from accidentally swiching back to your other desktop? I don't see a way to lock mouse control to the Rift's desktop/window.

I've not found a fix for that either. Fortunately X52 allows me to do everything apart from the galaxy map without a mouse.

Having said that I'm switching off DK2 until they patch in support for the new SDK.
 
Windows 8.1 here - I have rotational head-tracking (DK1-style) but no full positional head tracking.

I also have a ton of judder when moving my head even with all settings to low.

The combination of these two problems makes Elite rather nausea-inducing.
 
Has anyone found a way to keep mouse control from accidentally swiching back to your other desktop? I don't see a way to lock mouse control to the Rift's desktop/window.

Nope. Its extremely annoying. I don't even know if they will fix it :(

The galaxy map is nigh unusable. I spent a lot of time last night trying to setup keybinds to work the galaxy map without a mouse, but you still can't actually click on anything without losing the game.
 
Windows 8.1 here - I have rotational head-tracking (DK1-style) but no full positional head tracking.

I also have a ton of judder when moving my head even with all settings to low.

The combination of these two problems makes Elite rather nausea-inducing.

This was happening to me until I realized that my camera wasn't actually powered. You'll see a little blue light on the camera once everything is set up properly and you're in-game.
 
got it to launch in extended

no head tracking at all..

cockpit its HUGE to the point i cannot see much of it at all... mouse works to look around but that is about it.. the scale seems to be messed up.

Mine was working when the beta released earlier this week, but the update has killed the cockpit view scale and head tracking :mad:
 
Regarding having no head tracking at all, I have that sometimes, but a quick reboot always fixes it.

Make sure you have disabled the oculus service in the task scheduler and removed the oculus thing from the autostart before you reboot, of course.
 
HIGHLY recommend using this to easily start and stop the OVRservice:
http://www.reddit.com/r/oculus/comments/2c6qqc/updated_unofficial_oculus_service_manager_by/

I think a lot of people go and kill the process, thinking they are good, but don't realize it auto restarts itself after a few seconds. That app makes it easy. Just click the STOP button and it stops it for good (or until reboot). If you later want to play a game that does need it enabled, just click START :)
 
Is everything extra drak for you guys? It seems like there is high contrast and darkness in the DK2 but not on my monitor. Yeah the juddering is still there no matter how good the fps is.
 
This was happening to me until I realized that my camera wasn't actually powered. You'll see a little blue light on the camera once everything is set up properly and you're in-game.

You're right - I don't have the blue light in game. How did you resolve it? Are you on Windows 8.1?

I definitely do have tracking working (and a blue light) in all the other DK2 demos I've tried.
 
You're right - I don't have the blue light in game. How did you resolve it? Are you on Windows 8.1?

I definitely do have tracking working (and a blue light) in all the other DK2 demos I've tried.

I figured it out - I had the rift camera plugged into a USB3 port. It looks like that works fine with SDK v0.4 stuff but broke with 0.3. Plugging into a USB2 port (black instead of blue) made everything work.
 
You're right - I don't have the blue light in game. How did you resolve it? Are you on Windows 8.1?

I definitely do have tracking working (and a blue light) in all the other DK2 demos I've tried.

I don't have a blue light on mine but tracking is working. I can lean in, look left and right without any issues. Using Win7 btw.
 
FOUND THIS , I tried it and it worked..

FOUND THIS , I tried it and it worked..

check out and thanks to Andy Mayer @

https://www.youtube.com/watch?v=zhxtN0W3fXA

Dk 2 to print out

If you have also received the DK2 and want to give Elite: Dangerous a try you should follow these steps:
o) Make sure that you have the Oculus Rift SDK 4.0 Runtime installed
o) run the Firmware-Update for the DK2 to v2.11 (refer to the Manual for the necessary steps)
o) if you screen is tilted in the Rift, right click your Desktop, select "Screen resolution", select the Rift and then change the orientation
o) when the tracking does not work, open the Task Manager and kill the Tasks "wscript.exe" and "OVRservice_x64.exe"
o) make sure that the Rift is set to "Extend Desktop to the HMD" in "Rift Display Mode" via the Oculus VR configuration icon next to the clock in your taskbar
o) start up Elite and in the Graphics options enable the Oculus Rift

After these steps the Oculus Rift DK2 was working correctly in Elite: Dangerous.
 
Text in Elite

Tip for text legibility:

When I start Elite lately I back up my chair, hit F12 to reset the Rift view, and then slide back to normal position. This makes the game think I am leaning forward all the time and enlarges all the text menus throughout the game.

Though it sure would be nice if the game itself let you increase font size throughout the game.
 
If someone is still having trouble getting the DK2 to work fully with elite, the following could be attempted, as it's the only way I got elite to work:

Use Bilago's utility and click "stop"

For me it wasn't enough to turn off wscript.exe and OVRservice_x64.exe, as I also had to turn off the OculusConfigUtil.exe
Bilago's tool does all of this with one button.
 
Last edited:
Unfortunately, I can't get the method described in this thread to work at all. Whenever I kill OVRservice_x64.exe, Windows stops recognizing the DK2 as a display and the status light on the kit turns off. When I launch Elite after that, status light turns on (in amber, not blue), Windows plays the "device found" sound in the background, and my main screen turns black for half a second as usually happens when the GPU driver accomodates a new display. But just a second later, Windows plays "device lost" signal, status light turns off, and the screen blinks again, with Elite window reappearing on the desktop. Then the device is found again and window disappears again. This repeats indefinitely, never stopping.

All I can deduce from that is that OVRservice_x64 should not be stopped as otherwise Windows is unable to complete the setup of the kit and drops the device. Is there anything I can do to work around that?

If that's relevant, I'm using Windows 8.1 x64 and GTX680. I have tried any and all combinations of disabling services with and without the aforementioned tool, made sure to set Rift to External mode, checked the hardware to work in the standard demo (everything works flawlessly), and tried to set DK2 as primary and secondary display in the Windows display preferences. Nothing helps. I either get no tracking and distorted image if Oculus config tool and services are kept running, or I get infinite display lost/found loop if the service is not running.
 
Last edited:
Unfortunately, I can't get the method described in this thread to work at all. Whenever I kill OVRservice_x64.exe, Windows stops recognizing the DK2 as a display and the status light on the kit turns off. When I launch Elite after that, status light turns on (in amber, not blue), Windows plays the "device found" sound in the background, and my main screen turns black for half a second as usually happens when the GPU driver accomodates a new display. But just a second later, Windows plays "device lost" signal, status light turns off, and the screen blinks again, with Elite window reappearing on the desktop. Then the device is found again and window disappears again. This repeats indefinitely, never stopping.

All I can deduce from that is that OVRservice_x64 should not be stopped as otherwise Windows is unable to complete the setup of the kit and drops the device. Is there anything I can do to work around that?

If that's relevant, I'm using Windows 8.1 x64 and GTX680. I have tried any and all combinations of disabling services with and without the aforementioned tool, made sure to set Rift to External mode, checked the hardware to work in the standard demo (everything works flawlessly), and tried to set DK2 as primary and secondary display in the Windows display preferences. Nothing helps. I either get no tracking and distorted image if Oculus config tool and services are kept running, or I get infinite display lost/found loop if the service is not running.
 
Last edited:
Back
Top Bottom