cancel
Showing results for 
Search instead for 
Did you mean: 

Inateck why?

Yasl
Honored Guest
Purchased a 4 port Inateck and It doesn't work.  Perhaps it's just my system but it doesn't work.  I can't plug both the sensor and the headset into it at the same time.  Ended up using my existing usb 3 port with the headset and the headset on the great Inateck card.  The more I play with the rift the more the sensor loses tracking and I find myself facing backwards.  I have less problems using my 'doesn't work' Renesas usb ports.  Shouldn't Oculus have put some sort of caveat on this?  Like - "if you have a system which has great usb support it will work, but if your system sucks this card will make it suck much worse!".

I mean, just giving Oculus a bad time for fun but seriously, I want this to work as best it can with my system and thought whatever upgrade I can give it (next to purchasing a brand new system) I'll do it.  Why would they recommend a card which only works on their 'certified' systems?

Just wondering.
- Yasl
6 REPLIES 6

Yasl
Honored Guest
Pardon - plugged the headset into my existing usb 3 and the SENSOR into the Inateck card.  🙂

Mr_Wilde
Heroic Explorer
I have similar issues on my second PC. For some reason, even when plugged into the Inateck card, sometimes the sensors will appear in the the list with a green dot, but if I click on it, no USB connection is detected, and I have no tracking. Oh, and the HMD is recognized as USB 2.0. 😐

Hornet_F4C
Adventurer

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

Thijssss
Explorer
My Inateck card was doing strange stuff as well. HMD said it was using USB 2.0 and such.. then I downloaded the newer Frescologic drivers and that solved everything:

https://support.zoho.com/portal/frescologic/home#Downloads

At the right, download the USB3.0 Host Driver


(FL1000, FL1009, FL1100) 


...



v3.6.9.0a



VRoaaar
Protege
Try this:
use Microsoft's drivers instead of the Fresco drivers
download the Oculus setup here, run it, choose "Repair" and reboot afterwards
if you still have problems, try this
if you still have problems: clamp a ferrite bead near the USB plug of the sensor

Yasl
Honored Guest
Inateck sent me a new card to try.  Seemed to work but I did get a 'not found' error now and then and also had a warning to update my drivers.  On the fresco site there is a 3.6.9 driver which seems to work great and removes the 'update driver warning'.  Inateck only has a 3.6.8 driver.