10-17-2016 06:57 PM
10-17-2016 06:58 PM
10-17-2016 07:13 PM
10-18-2016 12:22 AM
For me it was similar, albeit somwhat different.
When both the HMD and the Sensor being plugged into the innateck card not only the HMD was recognized as USB 2.0 but also suffered from frequent disconnects (accompanied by this windows usb-sound and being reported as "HDMI is not connected" in Oculus home, with those messages frequently being marked as already resolved). This happened when the headset was idle and also when it was in use, hereby causing everything from nothing to backouts and application crashes.
My solution was similar to yours. Just leave the sensor plugged into the innateck card and use onboard usb 3.0 for the headset. I was lucky enough for that setup to work. Everything seen as USB 3.0 and no disconnections since. Also in between I migrated from Win 7 to Win 10 and it still seems to work ok.
From what I read and experienced so far USB problems manifest themself either as device detection problems or more or less frequent disconnenctions.
If in your case the sensor generally works on the innateck port, but tracking degrades with time, maybe there is a chance for an hardware fault with the sensor or the HMD? It is hard to test and to confirm, but you'd receive a replacement rather easily.
Greets
10-18-2016 01:40 AM
10-18-2016 02:46 AM
11-01-2016 06:35 PM