I don't think there's a problem with the drivers or in the bios because the headset and the camera are plugged in the same controler card. The weird point is: oculus home detects the dk2 on usb3 and the camera on usb2. This issue is present on windows 7 and 10. Before 1.3.2 update, they were both detected on usb3.
For me, plugged into the Inateck port, as recommended on here.. I get the DK2 as USB 3.0 with a warning and the sensor showing as USB 2.0.
If I plug it into an unsupported USB 3.0 slot from my MB (ASMedia) then USB 3.0 shows as working fine (no warning) but the sensor still shows as USB 2.0
I don't recall what happened with previous versions (usb 2/3) but I do know one of the updates forced me to change usb slot I was originally using when 1.3 first came out because the DK2 would no longer turn on, so clearly something changed in the software.
Since I now checked (because of this thread) I now I have to figure out why the supposedly supported Inateck card is throwing an error.. "Your headset is plugged in correctly, if you encounter tracking issues updating your driver (Fresco Logic) may improve performance" hmmm I could swear it is the most recent driver.. hmmm.
Edit: Seems windows changed the Fresco Logic driver back to MS one.. but it still shows sensor as usb 2.0, the rift doesnt show any USB 2 or 3, but says its connected ok.
CV1: Ordered 6th Jan 2016 - Est Delivery Some time in May...
DK2: Ordered: 8th of Aug 2014 - Delivered: 14 Oct 2014
same here, says its usb20 with every port i try even tough windows tells me its usb30 ports, just igonre, tracking works flawless even with the warning..
Get Help
Did this answer your question? If it didn’t, use our search to find other topics or create your own and other members of the community will help out.