URGENT - does anyone use this USB 3.0?

http://www.currys.co.uk/gbuk/comput...de-4-port-usb-3-0-pcie-card-10119363-pdt.html

I am currently extremely peeved at Oculus for the whole USB 3.0 incompatibility issue. I'm especially peeved that they give NO info about which ones would work. I've bought one from maplin, no luck, neither did my mobo or the other pci-e that I had. A list or some kind of instructions would be nice, but nothing. So we either have to do pot luck, or get some out of stock "we know this works" card.

So yeah, while I add another week to my 6 months waiting, would be very nice to know if anyone has any easy-to-get PCI USB 3.0 cards, like the one above, and know for a fact they are "compatible"?

Thanks guys, I appreciate it
 
Vive user here.

I use the 3.0 USB connect from my case which goes direct to my mobo. ASUS Crosshair V Formula-Z ROG Mobo. No need for a special card.

Check your BIOS and make sure your ports are set to USB 3.0 and not 1.0 or 2.0. They may be limited by settings rather than hardware. Which mobo do you have and I can look up the tech specs.
 
Vive user here.

I use the 3.0 USB connect from my case which goes direct to my mobo. ASUS Crosshair V Formula-Z ROG Mobo. No need for a special card.

Check your BIOS and make sure your ports are set to USB 3.0 and not 1.0 or 2.0. They may be limited by settings rather than hardware. Which mobo do you have and I can look up the tech specs.


Thanks, it's the ASUS P8Z68-V LX - I will check my BIOS right away (although not sure I've seen it there)

My BIOS isn't up to date either, as last time I tried it wouldn't boot and it was a miracle I was able to even get back into the flash utility
 
Are the USB controllers listed correctly in Device Manager? That is, do you have any exclamation points on anything?
 
It was fine, but I'm about to follow this:

irst, relocate anything important to USB 2.0 ports. This is likely your mouse and keyboard, but may include an external drive or something. Most 3.0 drives can run slowly in a 2.0 mode.Second, download copies of your ASMedia (Asus's name for mobo software) drivers in case things don't work out. Always good to be prepared.
Next, open your Device Manager. On every recent version of windows this can be done from the System dialog (windows key + pause | break key) and is usually found on the top-right of that. On Windows 8.1 and newer, right-clicking the start menu should also have an option to open Device Manager.
Now, I'll admit I don't know the names of everything here exactly and am going off memory so you may have to guess a bit. Under Universal Serial Bus controllers should be something like 'ASMedia USB 3.0 eXtend know Host Comtroller'. If it's the Windows copy it will say (Microsoft) after the name I believe. If it doesn't, there's your problem.
If your driver is provided by Microsoft, ignore the rest here. The Oculus utility is likely complaining about Asus USB devices in general (my capture card has a utility that does this too) by name alone, but your driver will make your controller behave as a standards-compliant 3.0 controller.
So, if you have Asus drivers do this. Right-click the device / driver and click Uninstall. When one of the dialogs asks if you'd also like to delete the driver, check that option so it will. Without deleting the old driver, upon rebooting it will just reinstall automatically which we don't want.
Next is a tricky voodoo magic part. Even with the windows drivers, the AI Suite software that comes with Asus drivers can still screw things up. In particular, look for anything related to USB 'boost' or 'quick charge' and disable it.
Reboot once you're done.
Once back into Windows, let the Device Installer try to install the Windows driver. If it doesn't do it (usually the case, but not always oddly) then we'll need to go back to Device Manager and do it manually. In any case, check the driver again to see if it is the Microsoft provided one. If it is, you should be good to go. Move your devices back to their previous USB ports.
If the controller didn't install, we need to look for a device with a yellow alert placard symbol next to it. It can go by all sorts of names (generic micro controller, unknown USB hub, etc) but it'll have that yellow triangle with an exclamation point in it.
Right click that device and find the option to install a driver. This varies by version of Windows. However once you find it, you can let Windows try to search your drives for a proper driver. Usually a Windows version driver shows up in the list. If not, click Choose a Driver or similar. Here you can choose by manufacturer (Asus, ASMedia) and then pick a matching driver. Look for the closest match. If nothing matches the ASMedia 3.0 controller, check under Microsoft as the company for a generic USB 3.0 controller driver. Once found, select the driver and click Next. A few confirmations later and you should be good.
For good measure, I recommend rebooting again. Most of the time it isn't necessary, but with micro controllers there's sometimes issues without reboots.
Personally, I ran the Microsoft ASMedia controller driver a while with no real issues. I forgot why, though I seem to remember it being software related, but I had to swap to the Generic USB 3.0 Host Controller driver from Microsoft. It worked flawlessly as well, so that's always a viable option.
If by chance things go south, just reboot and reinstall the Asus provided ASMedia drivers. There's a chance it'll still work (sadly, a low one) with Rift as some of their mobos worked properly. If not, buy a decent USB 3.0 expansion card. A PCIe card will likely work fine (x4 lane ones may top out at 2 ports used though, which is fine for Rift) but if you have one laying around try a front-panel header expansion. Some cases come with 3.0 front panel header plugs. I mention these because in a lot of Asus mobos, the rear USB ports use a cheap controller while the expansion headers are straight Intel brand. Ditto SATA ports as well, where if you have them usually ports 3-8 are Intel controlled, just FYI.
I hope that helps in a little more detail. When I get home I might update this to be a little more accurate, as my Asus PC was converted into a media PC but otherwise left untouched. I'll check how it's configured and see if I missed anything.
 
All right. While in Device Manager, select USB Hubs, Properties, Power Saving tab and unclick "Allow the computer to turn off this device to save power". Repeat for all USB hubs. May help.

No such option I'm afraid, and the other thing didn't work. I'll head to the mobo now.

Just out of interest - the Oculus Home isnt' detecting the CV1 at all, even with HDMI plugged in and the USB in an "incompatible" port. Will it detect once I get a proper port...?
 
If nothing works I found this Oculus Rift forum post that recommends the below card.

https://forums.oculus.com/vip/discussion/28509/incompatible-usb3-0-ports

https://www.amazon.com/Inateck-Supe...dp/B00FPIMICA?ie=UTF8&*Version*=1&*entries*=0

- - - - - Additional Content Posted / Auto Merge - - - - -

Just out of interest - the Oculus Home isnt' detecting the CV1 at all, even with HDMI plugged in and the USB in an "incompatible" port. Will it detect once I get a proper port...?
I should think so, though why it is incompatible in the first place is amazing.
 
Your MB uses the ASMedia 3.0 USB Controller. ASUS releases updated firmware for this controller a couple of months back to improve Rift compatibility - at least they did for my MB. There was also a separate update to the drivers. I will have a look for your MB.

EDIT: oh and according to the Oculus support website it should work in USB 2.
 
Last edited:
Your MB uses the ASMedia 3.0 USB Controller. ASUS releases updated firmware for this controller a couple of months back to improve Rift compatibility - at least they did for my MB. There was also a separate update to the drivers. I will have a look for your MB.

EDIT: oh and according to the Oculus support website it should work in USB 2.
(He has the LX version which has the Intel controller.)

Strike that. He has both.

https://www.asus.com/Motherboards/P8Z68V_LX/specifications/
 
Last edited:
Your MB uses the ASMedia 3.0 USB Controller. ASUS releases updated firmware for this controller a couple of months back to improve Rift compatibility - at least they did for my MB. There was also a separate update to the drivers. I will have a look for your MB.

EDIT: oh and according to the Oculus support website it should work in USB 2.
What should work in USB 2.0????

It's not! Is it broken????
It was giving me the Rift Audio devices yesterday, it was plugged in to an "incompatible" USB. Now it's not. I'm going mad here



Also I saw that ASUS update, didn't apply to my mobo tho, and mine hasn't had an update since win8
 
The Rift:

If you do not have any other USB 3.0 ports available, you may try USB 2.0 ports. Note: using USB 2.0 ports degrades tracking reliability between the headset and sensor.

https://support.oculus.com/help/oculus/551128041715108/?ref=hc_fnav

The most recent ASMedia USB 3 driver for your MB is Nov 2013 - still worth trying though if you are not running that version. Unfortunately I couldn't see a firmware update though. Would also suggest trying to get your BIOS to the latest version if possible.

Have you unplugged all other USB devices?
 
Last edited:
The Rift:



https://support.oculus.com/help/oculus/551128041715108/?ref=hc_fnav

The most recent ASMedia USB 3 driver for your MB is Nov 2013 - still worth trying though if you are not running that version. Unfortunately I couldn't see a firmware update though. Would also suggest trying to get your BIOS to the latest version if possible.

Have you unplugged all other USB devices?

I don't know. I don't know anymore. It makes a noise when I plug it in, but nothing seems to be detected, not in Oculus Home, not in Device Manager, no sound devices...

I can't update my BIOS, it just doesn't work. Not risking more problems. Looks like I have to just wait until Friday and hope the Oculus detects then too

EDIT: That article was talking about the sensor and that is indeed "connected" in USB2. Not detecting the rift alas.
 
I had mine plugged in to USB 2 ports and it all worked fine before I got my new MB with USB 3. I see absolutely no difference in using usb 3 over 2 now either.

If the headset is not detected or not displaying a picture check your HDMI cable does not have any bent pins - apparently that is common and Oculus are replacing the cables FOC.

Edit: usb 3.0 supposedly ONLY gives BETTER tracking that is all, eveything should still work - Again, I have seen no difference in mine since switching though.
 
Last edited:
I had mine plugged in to USB 2 ports and it all worked fine before I got my new MB with USB 3. I see absolutely no difference in using usb 3 over 2 now either.

If the headset is not detected or not displaying a picture check your HDMI cable does not have any bent pins - apparently that is common and Oculus are replacing the cables FOC.

Edit: usb 3.0 supposedly ONLY gives BETTER tracking that is all, eveything should still work - Again, I have seen no difference in mine since switching though.

Wait so it should be working via USB2? Well then it's broken....

No bent pins. I wonder if I somehow ruined the software. It would be so good if I could magically fix this and get playing tonight :)
 
I run my rift with USB 2, with no issues. If it's not working at all, something is borked.

Running a system restore. I had it plugged in for a week and ive done a lot of tweaking. It could be related.

Wondering if I disabled it when I was messing around with devcon
 
Running a system restore. I had it plugged in for a week and ive done a lot of tweaking. It could be related.

Wondering if I disabled it when I was messing around with devcon

GOT IT WORKING!!!!! WOOOOOOOOO!!!!!!! THANKS GUYS!
 
Back
Top Bottom