Is there any image quality difference if Rift sensor is in USB 2 instead?
- Thread starter kiario
- Start date
The sensor HAS to be USB 3
It is also inanely fussy on the chipset of USB3 too.
I bought a cheap 10 quid USB pci express card and it didn't work. Worked fine for the HMD though!
I bought the inateck oculus recommended USB3 chipset. works
At least I now have more USB3 slots than I know what to do with
It is also inanely fussy on the chipset of USB3 too.
I bought a cheap 10 quid USB pci express card and it didn't work. Worked fine for the HMD though!
I bought the inateck oculus recommended USB3 chipset. works
At least I now have more USB3 slots than I know what to do with
Some report saying it works over usb 2, but I wouldn't rely on it.
If it does work it doesn't impact in age quality per say, but you might get wobble in the tracking, which can be very disconcerting.
Best solution is to get one of the recommended cards.
I too got one that was throwing errors in the sensors but fine with the had , but after a moving the PC to a different room. For some reason it now working excellently with one of them and the hmd.
I also have an I ate inateck card somewhere but since I don't have Asmedia controllers I keep it in backup.
If it does work it doesn't impact in age quality per say, but you might get wobble in the tracking, which can be very disconcerting.
Best solution is to get one of the recommended cards.
I too got one that was throwing errors in the sensors but fine with the had , but after a moving the PC to a different room. For some reason it now working excellently with one of them and the hmd.
I also have an I ate inateck card somewhere but since I don't have Asmedia controllers I keep it in backup.
I have tested my 2 sensor setup on both my 2.0 and 3.0 ports (Intel) and see no quality or tracking differences. ymmv. If your 2.0's tracks ok, you should be fine.
X-Terminator
Banned
I only have USB2.0 and use motherboard for HMD & 1Sensor as it can only find these and non on the other Startech USB2.0 PCI card.
I have since found a 4port Startech USB3.0 PCI card (as I have no available PCIe due to Soundcard using the 2nd one). It will provide more power/bandwidth at least. I get this next week and I intend to add a 2nd Sensor with Oculus Touch so I'm not restricted to games content coming out.
Ignore the Compatibility Program they provide - it had reported both my cpu and motherboard USB Controllers are not compatible. I proved them wrong! Also since avoiding their SSE4.2 cpu check via Install Runtime 1.7 + auto-updates I have now rid all jumps/grey outs/flashes they introduced in 1.13 by liming AFFINITY for the 3 Oculus Programs to just cores 6-7 and ED is actually fine using all cores else you can also limit it to 0-5 cores.
I have since found a 4port Startech USB3.0 PCI card (as I have no available PCIe due to Soundcard using the 2nd one). It will provide more power/bandwidth at least. I get this next week and I intend to add a 2nd Sensor with Oculus Touch so I'm not restricted to games content coming out.
Ignore the Compatibility Program they provide - it had reported both my cpu and motherboard USB Controllers are not compatible. I proved them wrong! Also since avoiding their SSE4.2 cpu check via Install Runtime 1.7 + auto-updates I have now rid all jumps/grey outs/flashes they introduced in 1.13 by liming AFFINITY for the 3 Oculus Programs to just cores 6-7 and ED is actually fine using all cores else you can also limit it to 0-5 cores.
Last edited:
With 1500hrs in VR, I've only ever used usb2 for my tracking sensor (with dk2 and cv1). Always works well.