How to get the DK2 working

Brutaljuice

B
Finally figured out my issue - hopefully this helps others resolve:

Symptoms:
* DK2 demos work
* ED w/ OR services running works but has no tracking
* ED w/o OR services running crashes to desktop

Solution:
* Unplug the camera completely

Now I've got a somewhat jittery experience to fix, but at least the 100% crash to desktop is solved.
 

nick_j_bacon

nick_j_bacon
Not tried the supersampling trick yet.

I am hoping that we get an update on whats happening wrt the DK2. Would be nice to take advantage of the new features.

Guessing it will be in the next fork but Devs have been pretty quiet about what's happening recently :(
 

grimdar

G
Holy... CRAP. :eek:
Just got my DK2 this morning, and with very little fiddling got ED to run really nicely. Absolutely stunning! I've had the DK1 since the beginning, played almost every demo/game there is. But this is just a whole new level of experience especially if you like space sims.

A big thumbs up to the ED dev team who made the whole UI feel so Oculus friendly. Its just amazing to just turn your head and open a menu. The text is legible for me even without leaning forward.

Now the only small issue I found is the game looks too bright now. Is there a way to turn down the brightness?
 

Poweti

P
Brutaljuice said:
Finally figured out my issue - hopefully this helps others resolve:

Symptoms:
* DK2 demos work
* ED w/ OR services running works but has no tracking
* ED w/o OR services running crashes to desktop

Solution:
* Unplug the camera completely

Now I've got a somewhat jittery experience to fix, but at least the 100% crash to desktop is solved.
Click to expand...


This is exactly how I had to get it working for me too, but others are able to use the camera, so I'm wondering if we have any hardware in common? Are you using any MSI mobo/gpu/etc.? USB 2.0 or 3.0?
 

smoodiver

S
Poweti said:
This is exactly how I had to get it working for me too, but others are able to use the camera, so I'm wondering if we have any hardware in common? Are you using any MSI mobo/gpu/etc.? USB 2.0 or 3.0?
Click to expand...

Same experience here!

Hardware:
Gigabyte GA-990FX mobo
AMD X6 1100T CPU
Windows 7 Pro
I've tried USB2 and 3 - no change.

My CPU didn't have SSE support but no change since the 0.4.1 SDK/runtime release (removes SSE requirement).

Fingers crossed the next ED release has support for the new SDK!
 

Poweti

P
smoodiver said:
Same experience here!

Hardware:
Gigabyte GA-990FX mobo
AMD X6 1100T CPU
Windows 7 Pro
I've tried USB2 and 3 - no change.

My CPU didn't have SSE support but no change since the 0.4.1 SDK/runtime release (removes SSE requirement).

Fingers crossed the next ED release has support for the new SDK!
Click to expand...

This is indeed the case.

@OP Please note on the original post that older AMD processors without SSE 4.1 support, will have issues with the head tracking camera, the head tracking camera has to be unplugged (usb only, sync cable can stay), to allow the rotational tracking to occur.
 
Last edited:

kyoseki

K
Ok, got it working with SDK 4.1 & firmware 2.11

Yeah, wow.

Ok, short list:
From the rift toolbar icon, select "rift display mode" and switch to "extend desktop to HMD" make sure the DK1 compatibility flag is ON.

In NVidia control panel, make sure "activate all displays" (under the SLI panel) is turned ON.
Rotate the Rift display to landscape (it starts of portrait for reasons best known to itself).

In the windows task manager, kill the process "wscript.exe" and the process "OVRService.exe" (this reenables motion tracking, but it disables the little camera on your monitor, so it's a little jittery).

In Elite, you may have to faff about with which display the client should display on (mine was "tertiary" despite the fact that the rift identifies as display 1 in the NVidia control panel), but you want fullscreen and obviously turn on the rift in the 3d stereo settings.

That seems to be it, it gets it working here, the only real issues are a lack of resolution (that's apparently fixed by supersampling) and the black smearing issue that's apparently caused by using values too close to true black in the display.

It's pretty incredible.
 
Last edited:

kuraikami

kuraikami
I got one problem. I put the Rift in extended mode, put it in potrait mode with 75hz in nvidia system panel, killed the two processes in the taskmanager, forced V-Sync in Nvidia system panel and used the right preferences in the ED options (second monitor, Oculus Rift Headphones, V-Sinc on, 1920x1080).
On another PC I can play perfectly fine with this settings.
But on my mobile Gaming machine
(i7 2670qm; gtx 570m; 6gb ram) I got this strange stuttering and flickering with the positional tracking. Even if I hold completely still the image I'm seeing (cockpit in ED or menu) is flickering as if I would my head a little. The head tracking itself is working flawlessly but it seems that the camera is interfering with the tracking. If I'm inside the cockpit I'm always seeing the same flickering you see if you are out of camera range.
When I'm leaning in and out to the camera the uttering increases.

Here is a video of the issue. I removed the left lens to film it.

https://www.youtube.com/watch?list=UUBMM5FxQsptooBWAQHP7aEA&feature=player_detailpage&v=pD46f7ZXiZo



Any ideas?
 

Wolfox

Wolfox
This my way

(All this is done after updating, configurating,testing the Oculus Rift DK2 with the configuration tool ;) )

To make it work from that day till now.
[System i5 4430 with third party Nvidia GTX 770 2gb on Win7]
- Connect everything and PC on:D
- Activate multiscreen on Nvidia control panel
- Turned Rift orientation on Nvidia control panel
- Set Rift screen at 75hz on Nvidia control panel
- [Optional but done]Created a Elite Dangerous profile on Nvidia control panel
- Extended Desktop on Windows
- Extended option on Oculus rift configuration tool in Display Mode.
- Download Oculus Service Manager and press STOP SERVICE
- Start Elite dangerous
- go to Options\Graphic and set resolution and 3D experimental- APPLY
- If nothing happens EXIT and restart the Game.
- If the stereoscopic view is on your main screen; Go to Options\Graphic (you should be having some voices in red)and set Screen as SECONDARY

[Note] On your desktop nothing will happen all the magic is in the RIFT :D.

Once everything is ok the only thing to do when you want to start ED from now on is:
- Start Oculus Service Manager and press STOP SERVICE(is possible to see if the service is stopped on the top left of the window)
- Start Elite Dangerous:)

For now it works:S
 

Serpentstar

S
I can tell you have I get mine to work every time.

ED only sees 2 of my 3 monitors (4 if you count the DK2)

So what I have to do is pause the services from the configuration utility, launch ED and wait past the intro screens. Once I get to the first gray screen where I can see my friends list, I wiggle the headset.

Typically, the video will likewise wiggle.

Then I take the whole screen and drag it over to Monitor 4 to where I can barely see the left edge and keep it as high as possible and I drop it there.

I cannot get ED to just go to the correct display no matter how many I remove or change.

I will be so glad when the get it to work in the default mode where I only have my 3 displays and the DK2.
 

stevesideas

stevesideas
Am I correct in thinking that once ED supports the latest SDK we should be able to run ED as direct to rift ? This would also sort all the judder issues out as well yes ?
 

Adam Lusardi

A
Welcome to the forums.
I've not had head tracking since release so not bothered updating either.
Lets hope there is a Beta 1.04 for rift users to test.
 

Faile

F
For all you who dont have headtracking working with DK2, _turn off/pause the service_ , ie. right click on your oculus icon in the tasktray, select 'configuration utility' , then 'tools' -> 'advanced' -> 'pause service'

Then launch E:D , headtracking will now work. This is because DK2 needs to emulate being DK1 to work with E:D, the newer SDKs do not work (no headtracking).
 

tnxgalaxy

tnxgalaxy
Micronomic said:
Didn´t have any problems before firmware update to 4.2 for rift and beta update for ED today to play ED with the rift.

Have no headtracking now and anything is wrong now.

Can anyone help please ?`


:eek:
Click to expand...

I guess ED needs to be compiled with the version of the SDK, so we probably have to roll back down to 0.4.1 and to wait for the next ED release before upgrading.
 
You must log in or register to reply here.
Back
Top Bottom