Oculus software detecting usb 3.0 as usb 2.0

[IceCreeper909]

The title should be self-explanatory; My oculus software is detecting my USB 3.0 cable(the Anker one that was recommended before the official link cable) and USB 3.0 port as USB 2.0. I've gone and tried to update my drivers, including uninstall/reinstall, to no avail. Any suggestions for a fix? For reference, both my Quest and PC are running the latest versions, and my PC is link compatible. 

[yosemVR]

Quest 2, MSFS, Link - Having some success lately after trying this and that. I have actually been able to fly for a few hours at a time, stable connection, stable frame rate, smooth reprojection and half decent graphics. Don't laugh, GTX 1660 Super/Ryzen 5 3600/16GB, somehow surviving doing mostly nice and slow sightseeing with the amazing Airbus H135 while island hopping in the pre-cached less demanding Caribbean islands area. I would say an 8 out of 10 sessions success rate. The only problem encountered once or twice was the annoying white semi-tranclucent horizontal line across the screen.

Here are some assorted findings hoping it may help someone. Sorry if some of it seems a bit off at this point but I'm glad to enjoy the flights, so...

1 - Guardian must be on, if you try to turn it off you will encounter assorted quest guardian-off bugs. You get a higher chance for a proper USB superspeed connection with the guardian on. Sadly disable the double-tap see-through feature, go to advanced guardian settings and set all the sensitivities to minimum, clear the guardian history. Then force restart, and then force shutdown after making these changes.

After relaunch go to your stationary seating (if you don't have one, make one up), set the guardian stationary settings, turn off the headset, then go to your play area seating (like where I fly), turn on the headset, set up the guardian as roomscale for that area. Restart/shutdown after changes.

2 - Using quest v27, Nvidia 465.89, oculus public beta, latest B550M MB drivers and firmware (that really helped with stabilizing the link USB 3 high speed connection), not original but good link cable connected via USB 3.0 Gen 2 port, no oculus tray or debug tool, link settings at 72hz and automatic resolution.

3 - Launch order is critical, any mishap or missed step along the way and you need to start from scratch. Yes, it's a bit crazy, it takes over 20 minutes from start to gameplay (when it works), but I'm taking into consideration that this will be fixed along the way and for me it's worth the sacrifice for now. Nothing beats flying MSFS in VR, link is the only option because using VD with msfs does not work(!).

So here goes (brace yourselves):

    Turn off headset, unlink link cable, restart the PC, turn on the xbox controller, turn on the headset, put it on and make sure it is happy and that the guardian is set, place the lenses guard in the headset so that it does not go to sleep, first and foremost launch USB TreeView or similar, connect the link cable and see that you have a superspeed connection (lately 80% success), if so breath deeply, make sure that the audio is routed to the headset in Windows, overclock the GPU, launch Intelligent standby list cleaner and purge any recoverable RAM, launch OpenXR and check that the scaling is set properly (I use 60%), launch MSFS, find something to do for the next 10 minutes, enter VR in the msfs app, make sure to move the mouse cursor to the bottom left or right, put on the headset with quest controller in hand facing the play area (do not remove the headset for the rest of the play session!), turn on Link, stretch your arm backwards, fumble around and find the keyboard space bar, hit it while you are facing the play area (great exercise), put down the quest controller and pick up the xbox controller (takes some skill "in the dark"), get comfortable, navigate the menus to your pre-set saved start airport (you can't search or use a keyboard in VR so you need to set up the location and fly it once in 2D before the VR flight), set up weather, time of day and such, start loading flight, scoot up to the required seating position in the cockpit.

And enjoy.

(** more msfs specific blah blah:

    *in the app mostly medium-high graphics settings, level of detail(s) 180%, render scaling 100%.

    *steam VR settings (msfs specific) render scale 100% advanced reprojection on.

    * steam use desktop game theatre setting unchecked.

    *HAGS off.

    *pre local cached flight locations, no flight over areas with photogrammetry or big cities, full offline flight.

    *a couple of power preference-over-quality msfs specific settings in Nvidia control panel.

    *OpenXR render scaling 60%.

    *no tray or debug tool.

    *stats show a nice stable 24 fps during flight, 100% GPU utilization, ~90% GPU RAM usage, ~80% CPU

    RAM usage, GPU temperature less than 80 degrees, CPU usage at 40%.)

[adestrix]

my dear people,

after many hours of troubleshooting on my PC, I have found out what was the problem. It was (as many times) infuriatingly simple. I had a USB 2 cable. Please look if your USB cable (packaging) CLEARLY states that it is

USB 3. If not, it is most likely USB 2. No matter what the vendor may have told you :)))

[ellismusic1]

Deleted

[AlasPoorJoric]

I'm using the official Oculus link cable, still detected as USB 2.0.

I've also tried it on a laptop, and with ports connected to intel, asmedia, nvidia and amd USB 3.2 controllers.

I've tried every suggestion I've read online and from support without effect.

[ellismusic1]

Deleted

[AlasPoorJoric]

That's not a USB C cable though. 

Did you switch from using a USB C port to a USB A port?

USB 3.2 C cables don't have blue connectors.

[ellismusic1]

Deleted

[Papitax]

I am trying to trouble shoot my oculus quest. i have a asus z370-e mother board with that chipset. with a 3rd party cable. if i restart the pc or the oculus some times it will connect as a 3.0 connection until i click accept in the headset then it will disconnect for a moment and reconnect as a 2.o connection. any tips? i dont want to buy the oculus cable and have it not work as well. 

[Traskas]

Same issue here.

I tried USB tree view: If I don´t move the headset is 3.2, port 19, but if I move it, changes to port 3 usb2.1.

ROG STRIX Z490 G.

So I think, in my case, it´s a hardware issue. I will trie with a new cable, this time, C to C.

[AlasPoorJoric]

I've given up. I tried Oculus support 3 times with absolutely zero resolution. I bought multiple cables (including the official cable), multiple adapters (using both USB C and USB A 3.1 ports), I've used multiple PCs and also purchased the highest spec USB 3.2 card I could get (so I've tried 4 types of USB controller). Always USB 2.0. I also tried all the settings combinations (developer on and off etc) and multiple factory resets. I wasn't using it at all for a few months, but airlink and virtual desktop have restored some usability at this stage.