Skip to main content
VinceS
Up and Coming
April 24, 2016

DK2 compatible with current Runtime and GTX960 STRIX cards?

I bought the DK2 over a year ago when it released. I struggled to make it do what I wanted to - user skill / knowledge issues, so put it down for a while. Just picked it up again to have another go and checked - all worked OK - was on 0.7 runtime. First thing update, right? Well that stuffed it!!! Removed the old runtime and get as far as "Update your Graphics Card Driver" and can't get the thing to run, despite that being no issue. The DK2 is happily being Monitor 5, no VR of course.

I have current nVidia drivers (364.72) and a pair of ASUS
GeForce GTX 960 Strix DirectCU II OC 4GB which I only bought a month ago and am pretty annoyed the base setup for the Rift is now said to be GTX 970 when I will be astonished if the 960's aren't up to the task as it was running perfectly well on a pair of Inno3D
GF GTX 460's before that. Could this "970+ policy" be what is stopping the install from completing? Anyone know why 970's were picked - is this a sales partnering thing or are there real reasons for it?

I have a pair of ASUS VG278H
27inch Nvidia 3D monitors and two other ancillary Viewsonics for email and miscellaneous hack-work - hasn't been an issue so far whether the DK2 is being used or not.

Searching here didn't find discussion on this topic so I am guessing it is just me - any clue what the problem might be? Thank you.



    5 replies

    VinceSAuthor
    Up and Coming
    April 24, 2016
    OK, so I can answer part of my own q. Searching may have produced nothing useful but simply looking around quickly finds this https://support.oculus.com/1267582579925778 where it seems the Rift Runtime is not the answer but SDK 1.3 is needed. So I am downloading that and will see how we go. But what a poor effort that the runtime trips on a phantom driver issue when the actual issue is likely to be it was a DK2 it detected that allowed it to proceed to the installation phase...!

    Also I now see a GTX600 is minimum spec for DK2, wonder why it worked fine on 460's? Perhaps because there were two - on an ASUS Maximus Extreme X38 mb + QX9650 - both of which in a few day's time when they turn up will get shoved out in favour of the latest Maximus Extreme VIII Assembly and i7 6700K.

    VinceSAuthor
    Up and Coming
    April 24, 2016
    OK for people with the same issue my initial problem turned out to be that GeForce Experience is faulty at some level. It happily reports I have 647.2 installed, but go to device mgr and it reports the driver version as 10.18.5906 - ie version 590.6. Click Update automatically and hey presto (after a while) driver updated to 10.18.6472 and the Oculus setup doesn't stop at the driver screen anymore. The "help" from Oculus says to go install the driver that first worked with the Rift, which I saw as pointless as I was already a version or 2 past that. However uninstalling current nVidia drivers and replacing with the older one would have solved the problem too. Updating the driver was definitely easier!

    Then as I go through set-up it checks I am on usb3 ports, but if I connect to them (via an Orico aftermarket card) the DK2 won't turn on and the sensor also. Yet connect them to a usb2 and they both start. The DK2 has a couple of warning messages about setup incomplete / PC under spec and the setup software detects sensor on usb2 but it never gets a result for hdmi test or rift usb. So I know it is on HDMI and shows up as a monitor in Windows if I let it so I skip that. Then get asked what controller I have, of which I have neither XBox or Oculus - there is a few PS3's lying around but I guess a deal wasn't struck with Sony so shafted and I seemingly need to buy a new controller...

    With all this bs I am rather tempted to uninstall everything and go back to 0.7 when everything worked just fine. However I note the Unity engine installed with no issues (using the installation helper), but the SDK 1.3 is just sitting there as it didn't come with executables, so wondering what I missed there. Sure would appreciate tips / a link to some info that would help me navigate through this mire of discombobulation. Thank you.

    VinceSAuthor
    Up and Coming
    April 24, 2016
    Hmm, OK I "get" the controller issue now. I hadn't looked when writing the last post but the DK2 is happily sitting in Oculus home and I can't select / do anything! Must be a way to get mouse controller in there...?

    Edit: OK, ordered a Rift - despatch in August apparently so eventually there will be an answer. Feel a bit shafted by the whole "DK2 who?" arrogant way this roll-out has occurred. Sure compatibility with early adopter rigs won't be seen as a biggie in the scheme of things, but we are now dealing with a company that has magically moved to Ireland so it can pay bugger all tax and has nearly doubled the shipping price to get a bit more of a return. No discounts of any kind for DK2 owners / early supporters. Smacks of arrogant corporate greed, but sadly will be gotten away with.
    VinceSAuthor
    Up and Coming
    April 25, 2016
    As far as runtime compatibility is concerned the runtime switcher seems to be the answer; see here https://www.reddit.com/r/oculus/comments/4ckm38/oculus_runtime_switcher_0506070813_with_gui/

    Re GTX960 card compatibility / consequences / reasons remains a topic I would like to explore further. As well as the non-working usb3 port connections.

    VinceSAuthor
    Up and Coming
    April 25, 2016
    sigh, turns out there are various types of usb3 cards and not all are Rift compatible. The compatibility detector from here https://support.oculus.com/help/oculus/1633938460220125/?ref=hc_fnav explains mine is not a winner. Also I have read up a fair bit on 960 .vs. 970 and I can see how the 960 could fall the wrong side of the line since there is a fair step between them. I would have to suspect that a pair of 4GB 960 cards in SLi would be a different animal to a single 2GB 960 - especially considering how readily the STRIX version can be overclocked. All my job to do eh; to muddle through the subtleties of this...

    Terms & ConditionsAccessibility statement