cancel
Showing results for 
Search instead for 
Did you mean: 

Quest 3 with Oculus Link/Link Cable not working on USB-C 3.2 for PCVR

MacheQ
Honored Guest

So I have this very specific issue when using my Quest 3 for PCVR via Oculus PC app, my PC has 3 different USB Type-C ports and:

  • When I plug it into a 3.2 Gen 2 port, the headset recognizes it as USB-3, the image is clear and it works great, except the battery drains very quickly and it shows a notification about slow charging.
  • Then, I tried to plug it into a 3.2 Gen 2x2 port and it charges quickly, just as fast as it does with the stock power brick, however, the Oculus app recognizes this as USB 2.0, so streaming PCVR doesn't work.
  • And last, I tried on a 3.2 Gen 1 port and it's the same as the previous port.

My setup worked without issues for my Quest 2, so I don't know what in the world is going on.

Is it even possible to have fast charging and PCVR simultaneously via cable on Quest 3? I can do PCVR via Airlink/Steam Link while it's plugged into the "fast charging port" and it works, but the image sometimes suffers from compression. Any of the 3 ports should be able to charge it while streaming, and the 2x2 supports up to 20Gbps, but it's not working and I don't know why. I already checked USB drivers, tried changing USB power settings, updating BIOS, reinstalling the Oculus drivers, updating the headset, it's all the same.

Also, I already searched for other posts but I couldn't find anything specific for this, just some troubleshooting steps I already tried.

14 REPLIES 14

Zourak
Explorer

On the forums and on Reddit this is a more or less known issue that the Quest 3 is very picky when it comes to USB Ports on the PC. There have been different reports that some USB-C Ports that support Power Delivery have been supplying enough power to keep the Quest 3 charged. Most recently a Reddit user reported that his Thunderbolt 4 Ports on a PCie Card and on his Laptop seem to supply enough current aswell. There is no official statement by Meta which USB protocols work and which don't. They only state the following requirement:

"usb c port providing sufficient current" 

 

So far it's up to users trail and error to figure this out. 

MetaQuestSupport
Community Manager
Community Manager

Hey there, @MacheQ! Thank you for bringing this to our attention. We understand the importance of connecting your headset to your PC with a seamless effort. We'd love to take a deeper look into this issue for you. Send us a PM by selecting our name to get to our profile page, or click here: Next, click "Send a Message" to privately message us! Please remember, you must be signed into the community first to send us a private message.

If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!

MetaQuestSupport
Community Manager
Community Manager

Hi, @MacheQ. We wanted to follow up with you and see if you still need assistance with your Link Cable issue! We will be patiently waiting for your response and hope to get you back on track!
 

If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!

Hey! I just sent you a PM. Thanks in advance.

Jmoney9929
Honored Guest

I'm experiencing the same issue with my brand-new Quest 3 and official link cable in a USB-C 3.2 Gen 2 port directly into the Motherboard. Unfortunately all of the USB ports on my PC are USB-A 3.2 Gen 2 or the aforementioned single USB-C port on the back that I have primarily been trying to use. I've also tried the USB-A ports with a C to A adapter. No matter what I do, the Oculus app doesnt detect the headset nor does the headset detect the PC.

Pretty **bleep** frustrating out of the box experience after spending several hours researching minimum requirements and checking my specs. Am returning the cable and looking at getting a 3rd party one as people seem to have more success with those.

Hey @Jmoney9929! We got your PM, and will continue to provide further assistance from that channel. Looking forward to speaking to you soon. Have an exciting rest of your day!

If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!

IrrelevantD
Honored Guest

I'm wondering if there was a recent windows update or something that broke something.  My Quest 2 was working fine with the link cable up until 2-3 days ago.  Something changed, and I have been going crazy for the last few days trying to get it working again... Including buying a Quest 3 (partially so I can let my son have exclusive use of the 2).   AirLink connects in like 3-4 seconds, but if I try using USB, it's the never ending 3 dots.

AirLink works fine, and I've been through all of the Meta Chat suggestions.  I've tried factory resetting the device, an untold number of reboots, uninstalling video drivers (DDU in safe mode as well as AMD's removal tool), removing and re-isntalling the software and drivers more times than I can count, sifting through the server logs, I've tried multiple USB cables (The desktop app reports the connection as 2.3Gbps), and all I keep coming back to is there's some sort of permissions issue with it accessing the USB.

I keep comming back to the following lines in the OVRServer console and thinking it's gotta be some permissions issue in the registry or something:

09/03 17:16:44.168 {DEBUG}   [RemoteHeadset_V2] RemoteHeadsetPlugin::GetHeadsetState VsyncToFirstScanline = 0.011530
09/03 17:16:44.543 {!ERROR!} [xrstreaming] CreateFile('\\?\usb#vid_2833&pid_0182&mi_01#7&3a6beb2&0&0001#{f72fe0d4-cbcb-407d-8814-9ed673d0dd6b}') failed after 20 attempt(s): (5) Access is denied.
09/03 17:16:44.543 {!ERROR!} [Kernel:Error] OVR Error:
  Code: -6102 -- ovrError_XRStreamingUSBIssue
  Description: CreateFile('\\?\usb#vid_2833&pid_0182&mi_01#7&3a6beb2&0&0001#{f72fe0d4-cbcb-407d-8814-9ed673d0dd6b}') failed after 20 attempt(s): (5) Access is denied.
  OVRTime: 2256.277292
  Time: 2024-03-09 17:16:44 [543:264:0]
 
09/03 17:16:44.543 {INFO}    [xrstreaming] couldn't open device USB\VID_2833&PID_0182&MI_01\7&3A6BEB2&0&0001 (path: \\?\usb#vid_2833&pid_0182&mi_01#7&3a6beb2&0&0001#{f72fe0d4-cbcb-407d-8814-9ed673d0dd6b})
09/03 17:16:44.543 {DEBUG}   [xrstreaming] oculus_xrs_usb_create_failure error: 5 getlasterror: 5
09/03 17:16:44.543 {DEBUG}   [xrstreaming] device path: \\?\usb#vid_2833&pid_0182#2g0yc1zf9l0wm5#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
09/03 17:16:44.543 {!ERROR!} [xrstreaming] WinUsb_Initialize(0x0000000000064F68) failed: (8) Not enough memory resources are available to process this command.
09/03 17:16:44.543 {!ERROR!} [Kernel:Error] OVR Error:
  Code: -6102 -- ovrError_XRStreamingUSBIssue
  Description: WinUsb_Initialize(0x0000000000064F68) failed: (8) Not enough memory resources are available to process this command.
  OVRTime: 2256.277363
  Time: 2024-03-09 17:16:44 [543:335:300]



Anyone seen similar issues?

[edit] The plot thickens, I installed a second NVME drive and did a clean install on the same system.  Works perfectly.  Unfortunately the drive is too small to be usable, but it does confirm that it's not a hardware or cable issue.

Hello @IrrelevantD! We would love to help with using Air Link and Quest Link. We understand the importance of using PCVR for gaming and are so happy you are now part of the Quest 3 family in efforts to have your son enjoy the VR experience! We do see you have an open support ticket with us and will notify our specialist team that the issue has not been resolved yet. In order to minimize any confusion, we would suggest keeping an eye out on your email for a response from them and staying in contact via email. Rest assured, our team is working on your issue and we appreciate your patience! 

 

We are excited to get you and your family back to enjoying VR in no time! 

If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!

Hey there! We are just following up with you in regard to using Air link and Quest Link connecting to your PC. If you do still need assistance with this, feel free to reach out to us anytime, we are here to help! 

If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!