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

Just wanted to remind some of you to update your Rift's firmware in Oculus Configuration utility to 2.11 if you haven't already.
 
IF YOUR HAVING PROBLEM WITH DK2 try this

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.


best wishes
CMDR CHRISTINA JADE
 
I think it unlikely that the SDK will be implemented before Beta drops today, although Frontier have surprised us before... But that is no reason to not be able to jump straight in with the DK2 and have it working perfectly. Here are the step by step instructions to getting it to run Elite dangerous correctly...
* NOTE... This "fix" also works with a good few other demos, but requires that you set the rift monitor to primary. This is not necessary with Elite however.

fix for DK2 until SDK is updated...

1. Download the runtime and (optional) SDK
2. Set up the Rift by following the instructions ...

http://static.oculusvr.com/sdk-downl...ion_Manual.pdf

3. Make sure you update the firmware.
4. Test using the small room demo and / or oculus world using direct mode.
5. If they work, calibrate your IPD and tracking zone using the config app and small room. I find putting the camera on the back wall and moving the desk forward allows for more wiggle room.
6. If everything is cool, switch to extended mode inside the config app. For the moment keep the monitor set to primary.
7. Not sure about AMD, but for NVIDIA cards you will need to change the orientation of the screen, so that it appears the correct way round. This can be done in the NVIDIA control panel. Whilst you are in there, create a 3d settings profile for ED and set antialiasing and triple buffering to on.
8. Lastly in the NVIDIA control panel, set the Rift refresh rate to 75 hz.
9. Ok now open up the oculus config file again and hit Ctrl , Alt and Del. in task manager, close wscrip.exe and ovservice.exe in processes.
10. If its NOT Elite Dangerous you are wanting to play at this point, you will need to set the rift now as the primary monitor. If its Elite Dangerous you want, just open the game.
11. In options / graphics make sure the refresh rate is set to 75 hz and v sync is on. Switch to oculus mode and set display to secondary monitor.
12. Once in game, lean back in your chair and hit F12 to reset the rift and avoid clipping. If you are still not happy, move your desk away from the wall and reset again. (Assuming you have the camera mounted in the wall behind the desk.)
13. Done


*If you are getting a message saying oculus service not available, go to your oculus folder and open the inside the services folderovrservice_x86 or x64. Then open the config.exe inside the tools folder.

* it's also worth mentioning that its worth spending some time setting up your IPD and playing with the lens distance (via the screws on the sides of the rift)... Especially if things seems overly blurry.

Sorry to keep posting this, but people are asking the same questions and having the same issues. Id be panicking right now if my DK2 wasn't set up and ready to go for the Beta drop, so just want to share the love :p


Grrr.... I can get Elite to show up on the DK this way, but I have absolutely no tracking. (tracking works fine in the config tool)

As soon as I kill the OVR process, the config tool reports that there is no device attached and the tracking camera will not activate. To get the config tool to see the rift again I have to reboot.

This is maddening.
 
It seems that latency on the USB bus is causing some issues for some folks (causing stutter, crashes, etc).

My Rift isn't here yet, but it's the same for USB audio devices.

This post might be useful in diagnosing & solving them.
 
So I'm running low persistence now with a mixture of high, medium and low settings, it seems shadows and game AA settings are the biggest killers. Textures on high, planets and other things like that on high rest is medium or low, bloom off.

Have low persistence! But still the judder occasionally. No blur, just judder.
I suspect this is the 'forced' v-sync.

Has anyone overriden v-sync to turn if off and see if it improves?


Incidentally I upgraded to a Hauler last night and it's amazing how the Sidewinder felt like a cockpit and the Hauler feels like an actual cabin. the whole thing feels cavernous, 4 more feet away from you and a good 6 feet wider in all directions (sides and roof and behind the chair). It actually makes you pucker up when you try to dock through the slot the first few times. God knows what an Lakon and then an Anaconda is going to feel like! I can't wait :D

People who think a DK2 is 'too expensive' just have no idea what they're missing out on. One 5 minute sortie in a DK2 will have them all converted in a heartbeat.
 
Last edited:
When in starmap view i can't select the left pane, when i click there it minimizes to windows.
Also can't seem to find the buttons to navigate in that window.
Can anyone tell me how to get that working?
 
As SlackR suggests, turn off Aero in Windows. Right-click your desktop and choose Personalization, and select a Windows Basic theme. That weird "blip" should be gone.

I'll try that. :) I didn't specifically follow SlackR's intructions, I just played about with things myself - I like to do that so I should have a better idea of how things work then. I have no freaking idea why my PC suddenly won't boot into Windows after using the Rift and I have to so a system restore - that is a bit messed up! :(

Maybe it's fate's way of telling me to build a new PC. ;)

Oh, Frontier, please implement the slider/OFF switch for camera motion effects in the next release! :p
 

Sir.Tj

The Moderator who shall not be Blamed....
Volunteer Moderator
Finally managed to get mine up and running last night tanks to the help from you guys in this thread.

I'm getting some judder and text is a bit hard to read at the moment but I'll work on that and see what setting I can change to improve it.

Stunning is an understatement. :cool:

What I'm going to do is create a seperate thread with all the advice to help getting DK2 up and running in the off topic section a FAQ so to speak.

There's quite a few posts on this from you guys Slackr/KING5TON etc. Could anyone who sees a post that would be good to be included in a faq PM a copy to me and I'll compile a faq.

Thanks for the help in getting my DK2 running. :D
 
I Just wanted to say thanks to everyone posting here, i ordered my DK2 on the 16th June and at the time of order the website said August delivery so whenever my order arrives it will be much easier to set it up becuase of the all the helpful posts here. :)
 
Finally managed to get mine up and running last night tanks to the help from you guys in this thread.

I'm getting some judder and text is a bit hard to read at the moment but I'll work on that and see what setting I can change to improve it.

Stunning is an understatement. :cool:

What I'm going to do is create a seperate thread with all the advice to help getting DK2 up and running in the off topic section a FAQ so to speak.

There's quite a few posts on this from you guys Slackr/KING5TON etc. Could anyone who sees a post that would be good to be included in a faq PM a copy to me and I'll compile a faq.

Thanks for the help in getting my DK2 running. :D

If you make another thread please link to this one or try and lock it down some way. I hate when several threads start in a forum on the same topic.
 
I Just wanted to say thanks to everyone posting here, i ordered my DK2 on the 16th June and at the time of order the website said August delivery so whenever my order arrives it will be much easier to set it up becuase of the all the helpful posts here. :)

I expect that by the time yours arrives ED will fully support the new SDK and non of this will be necessary
 
Oh, another thing... I'm down in some serious uncanny valley with the pilot body! With the increase in fidelity in DK2 the feeling of presence (don't think I've experienced it 100% yet, but close) is stronger and the difference between the pilot and me is pretty jarring. For example, the simple fact that on-screen guy uses a full range throttle and I don't feels well odd! I've made my issues with self-bodies in VR plain in many threads but I'm trying to come to terms with it so I won't go into that again... but if you use a HOTAS and don't use a full range throttle setup I'd ask you to have a look at it and see how you feel. When I press my reverse button and push the throttle forward and my avatar's hand goes backward it's really quite disconcerting! :eek:
 
Oh, another thing... I'm down in some serious uncanny valley with the pilot body! With the increase in fidelity in DK2 the feeling of presence (don't think I've experienced it 100% yet, but close) is stronger and the difference between the pilot and me is pretty jarring. For example, the simple fact that on-screen guy uses a full range throttle and I don't feels well odd! I've made my issues with self-bodies in VR plain in many threads but I'm trying to come to terms with it so I won't go into that again... but if you use a HOTAS and don't use a full range throttle setup I'd ask you to have a look at it and see how you feel. When I press my reverse button and push the throttle forward and my avatar's hand goes backward it's really quite disconcerting! :eek:

On the same topic I think the pilot avatar is a little on the small side. Anyone else think his arms are too thin?
 
So I'm running low persistence now with a mixture of high, medium and low settings, it seems shadows and game AA settings are the biggest killers. Textures on high, planets and other things like that on high rest is medium or low, bloom off.

Have low persistence! But still the judder occasionally. No blur, just judder.
I suspect this is the 'forced' v-sync.

Has anyone overriden v-sync to turn if off and see if it improves?

The occasional judder is always going to be there. No game these days provides every frame on time, especially when you're looking at the incredibly low motion-to-photon time that's required by the rift.

To get anything remotely like comfortable viewing from the rift, you need vsync on and as close to a nailed down 75fps as you can.

A lot of games these days use double and triple buffering to kill tearing and provide framerate that's less erratic when a screen is missed. You can't do that with the rift, as when you double and triple buffer, you add a significant delay between input an display.

You move your head in the rift, it sends a signal to ED, ed updates the view and renders it to your rift. If the time between movement and rendering exceeds 20ms, you start to notice. One frame at 75fps takes around 14 of those 20ms, and it takes the oled panel another couple to turn the pixels on, leaving a few ms of wiggle room or anything else.

If you triple-buffered, you'd see the frame at least 45ms after you moved your head. It'd be like you were drunk.

If you kill vsync, you'll get tearing, and unlike normal displays, the rift display is a portait screen that's been rotated 90 degrees. It scans from left to right, not top to bottom, so you'd see the traditional "tearing" as a vertical misalignment. Even worse, it'll only affect one eye, and you'll eventually go mad and catch space rabies.

What the timewarp does is in the rift (I think, I'm hazy on the exact specifics of this) is to create "interim" data based on motion prediction and the contents of the last couple of frames. When ED misses a frame, timewarp gets invovled and shows you something that's good enough to fool your brain. When ED misses a ton of them, timewarp simply can't function properly and you get judder.

The fact that you're seeing judder isn't an indication that low-persistence mode isn't working, it's more likely an indication that you're framerate went south for just a moment.
 

SlackR

Banned
Grrr.... I can get Elite to show up on the DK this way, but I have absolutely no tracking. (tracking works fine in the config tool)

As soon as I kill the OVR process, the config tool reports that there is no device attached and the tracking camera will not activate. To get the config tool to see the rift again I have to reboot.

This is maddening.

The config tool should grey out once you kill the two process and tracking should work in elite in extended mode. Do not touch the config app once you've closed the processes and launch Elite.. Let me know what you see...
 

SlackR

Banned
So I'm running low persistence now with a mixture of high, medium and low settings, it seems shadows and game AA settings are the biggest killers. Textures on high, planets and other things like that on high rest is medium or low, bloom off.

Have low persistence! But still the judder occasionally. No blur, just judder.
I suspect this is the 'forced' v-sync.

Has anyone overriden v-sync to turn if off and see if it improves?


Incidentally I upgraded to a Hauler last night and it's amazing how the Sidewinder felt like a cockpit and the Hauler feels like an actual cabin. the whole thing feels cavernous, 4 more feet away from you and a good 6 feet wider in all directions (sides and roof and behind the chair). It actually makes you pucker up when you try to dock through the slot the first few times. God knows what an Lakon and then an Anaconda is going to feel like! I can't wait :D

People who think a DK2 is 'too expensive' just have no idea what they're missing out on. One 5 minute sortie in a DK2 will have them all converted in a heartbeat.

Are you running windows BASIC colour scheme?
 
Does anyone else get a, hard to explain, colour washout when you lean to far left or right? When I examine the cockpit and lean to far in one direction there is a very obvious ....lightening.... of colours
 
Back
Top Bottom