Oculus DK2, Windows 10 Question

[Anonymous]

Hi everyone, 

I'm very excited to join and be part of the Oculus experience. My situation is as follows: I cannot afford a CV1 or the PC to go with it, but I have been looking into a DK2 on eBay while I can save up for the retail version. I'm a flight sim enthusiast and have been looking at FlyInside Plug-in, my questions are:

1. Is the Oculus DK2 still being supported where I can download the necessary files to make it run under Windows 10 Pro?

2. Will the DK2 work with the Asynchronous Spacewarp technology? (I have an i7 laptop HP which I use for FSX, works very well)

3. Will the Oculus store work with the DK2?

Thanks to all, wishing you a blessed day!
Raul

[jmp909]

I can answer some of that

1) . https://www3.oculus.com/en-us/setup/  . officially not supported (also see 3). During setup it probably won't be able to find your HDMI/USB inputs... so Skip setup. it mostly works though.

2) don't know sorry

3) Officially no...as in it's not supported, and there's a warning as such. All the free titles I have downloaded have worked though. I guess the point is, if you actually buy games/apps off there and they don't work with your DK2 then they're not responsible for that. Store is essentially for consumer release hardware.

--

Also if anyone else can answer, I'd like to know if VorpX works with this setup, as I'd like to play some older games. I've tried Vireio Perception and Runtime Switcher for older drivers but I couldn't get anything to work so far. 

[jmp909]

p.s. worth noting...

"We have our own little warning too: because the consumer Rift has a proximity sensor Oculus Home is ‘always on’. It makes it easier for consumer Rift users to pop in and out easily. Not so with the DK2 though, so make sure to physically shut off the screen with the power button the top right of the headset, otherwise it may suffer catastrophic burn-in."

http://www.roadtovr.com/can-access-oculus-home-dk2-play-free-paid-content-right-now/

[vama89]

I was just looking through the forums to see if anyone was having problems with DK2 and I saw this post. Just wanted to throw-in my thoughts as a warning.

I have been developing for dk2 for the past year. I was literally playing landfall a day or 2 ago from today's date (2/8/17). Everything was working fine with the dk2 for home. When I'd boot up home for oculus and my dk2 there was always that warning sign saying that it would not support dk2 anymore but it would render images to my headset just fine. I mean I'd get judder everyone now and then but it was bearable.

However tonight as I was going to test out more game ideas dk2 seems to no longer work and I haven't updated my computer at all. I did notice that home seems to auto update itself. I can't tell what version of home I am on anymore but I downloaded the home setup from a few months back. This is the home for the cv1 version.

I just wanted to report as of just today it seems to not work. I don't have any official word from oculus. I'm still searching on the forums, but for any other developer out there thinking of using the dk2, it seems to look like home doesn't support it anymore. 

I'm going to try asking support if I can revert some older version of home. Sucks. I don't have enough to get the Cv1. I guess I'd just prototype visualizing what it'd look like until I can save up for a new cv1 kit. 

Bummer....

Oh yeah and I'm on Windows 10 as well. I'm not sure if my version is pro. 

Be warned!

[sbdykes]

While I'm not on Win10 (I'm running Windows 7), I also initially had some problems with the DK2 and Oculus Home (or just working in general) after the update.  Although it's somewhat anecdotal, I seem to be able to get it working by ensuring the HMD is turned on and within view of the sensor before starting Home.  Previous to doing that, the HMD would activate (blue light on), but nothing went to the display, even when it is in view of the sensor.  Once I got it to activate once things seem to be working normally.

Just thought I'd chime in with that in case it helps.

[vama89]

Thanks for the reply sbdykes. 

Yeah, at this point I gave up after having talked to support. They tried suggesting some troubleshooting solutions but for me it wasn't worth it anymore to try and fix.

I may give one last ditch effort to do what had worked for you by launching Home with the HMD within view of the sensor. I can't remember if I had it in view or not when I was testing things out. Regardless, before the update, during Landfall, it didn't matter if my HMD was in view or not.

And just in case this might be helpful in this discussion, I did find that oculus has this developer hardware application form. I haven't gotten the chance to thoroughly look it over, but here is the link:

https://developer.oculus.com/hardware-request-form/

Support said that they don't handle that application. My development is dead for VR cause I can't afford a CV1 at this point in time, but maybe to anyone out there whose DK2 just bricked but still needs to develop, you can try asking for hardware. I'm not sure what kinda of companies or individuals they'd grant it to, but its worth a shot. I'll try their application process sometime in the future. Just haven't gotten around to it yet.

Anyways, I'll post if placing the HMD in front of the sensor works for me (on Win10) and if there was any luck with the hardware request.

Good luck deving guys! And thanks for the replies. It helps giving me some sense of what happened and that my particular dk2 didn't just brick.

Best.

[jmp909]

I also noticed SteamVR demo room would not display unless the HMD was in view of the sensor 

[vama89]

jmp909 said:

I also noticed SteamVR demo room would not display unless the HMD was in view of the sensor 

Aright. I tried this method one last time. I downloaded the oculus setup one more time on my machine. Windows 10. I have the DK2. Again, this happened after the Landfall Beta updates.

So I tried placing my dk2 in-front of my sensor when I launch the Oculus Home app and I still get nothing. It reads my sensor but it can't detect the HDMI output. I talked with support and tried every possible type of configuration with swapping HDMI cables and usb ports etc etc.

My DK2 is dead with the current Oculus Home setup even if the HMD was in front of my sensor.

I also tried the setup up and during the process it can detect my sensor but not the USB for the headset or the hdmi connection though it is clearly plugged in. Again, I had no such problem before Landfall. Post Landfall beta everything stopped working.

Be warned DK2 legacy users!

[vama89]

https://forums.oculus.com/community/discussion/49513/dk2-broken-after-landfall-beta#latest

So as an update, I found a fix to the DK2 problem! It works!

I posted the details on how to fix it and what had happened in the link above.

Cliff's Notes: Update your Nvidia driver!

[richard_harwood]

I have had a similar issue, I have been using the DK2 with minimal issues on windows 7, but thought it would work better with Windows 10 so upgraded. I couldn't get it going at all so I downgraded to Windows 7, reinstalled Oculus and it worked again. I am interested in getting this working on W10 as I play Project Cars 2, and I just can't play it in 2D after playing it in VR. I am planning on saving for the new S but I only have $100 / week for gaming and I have just upgraded to a GTX1080 FTW2 and the DK2 so need to save up again! since the CV1 is $574 NZD the S will be about $650NZD