Oculus software detecting usb 3.0 as usb 2.0

Deathssaviour said:

Hi guys, just looked at this issue, from what I can see the system tells the device what type of connection it gets. Using an app called USB Tree Viewer I was able to start the app in administrative mode, find the host controller the Oculus device was on unplug the Oculus device and restart the host controller. Once I had restarted the controller I then plugged the Oculus device back in to see that the device was on a USB 3 port ( ss - super speed ) and then restarted the Oculus software and then my Oculus software could tell it was using a ss port and worked properly again. I know it's not a fix as such but, more of a workaround. Try the method and see what results you get. If you want the USB Tree Viewer, google it as I can't post url's yet or email me if you get stuck I don't mind helping anyone out where I can. deathssaviour@googlemail.com.

Cheers

Jon

SAME

=0(

How about USB power plant?

1. Press Windows + X.
2. Choose Power Options.
3. Select Choose when to turn off the display.
4. Open  Change advanced power settings.
5. Expand USB settings and USB selective suspend setting.
6. Select Enabled (default) or Disabled.

Click Apply, then OK.

Hi

I've been struggling with this issue for hours too : USB port is clear blue 3.0, tried two USB A/C adapters both clearly compliant with USB 3.0, and even checked with a USB key that the port was detected by windows as 3.0 BUT the Oculus is still detected as 2.0 😞

I wonder if you guys also have the "unknown USB device" error message. This shows up in place of what should be the USB 3.0 device.

Oculus Support have not been helpfull at all, just made me reinstall everything and send lots of logs but it didn't change anything .

I'm really sorry I bought the official cable to get this much trouble and end up with a slow bandwith. I should have sticked to the wireless solution. Hopefully some day they will fix the bug.

Good luck to you all !

I've only been able to get usb 2.0 speeds after update v25, using a usb 3.1 C cable.

I've tried 3 different cables and 2 PCs with different chipsets (Intel and AMD). Only connects at high speed, although it recognises the device is super speed capable. Prior to this is was connecting fine at USB 3.0, now I only get 366 mbps.

Having this same issue since a recent update, tried on multiple pc's too and it has this issue regardless 😞

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%.)

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 :)))

Deleted