New to the forums? Click here to read the "How To" Guide.

Developer? Click here to go to the Developer Forums.

The Official Oculus Link cable is not working for me. Anyone else have this issue?

24

Comments

  • enigma01enigma01 Posts: 764
    3Jane
    I had the same issue, but it was fixed for me by an adaptor I already had. But a type c dongle adapter, so it just seems like the cable isn't recognised properly 
    There is no point in me doing that though. My laptop USB A ports are 3.1 Gen 1 at only 5gbps, my Thunderbolt supports 3.1 Gen 2 at 10gbps. I only purchased the expensive Oculus cable as I thought it would support the higher bandwidth as I read somewhere that Carmack may have a way of increasing the Quests resolution using Oculus Link cable https://uploadvr.com/john-carmack-oculus-link-update/

    I have been using 5m of passive USB 3.1 cable connected to my USB 3.1 Gen 1 port with Link and works fine. It cost a small fraction of what Oculus official cable does. 
  • The_Kingpin66The_Kingpin66 Posts: 4
    NerveGear
    enigma01 said:
    I had the same issue, but it was fixed for me by an adaptor I already had. But a type c dongle adapter, so it just seems like the cable isn't recognised properly 

    Same here, after I installed a usb C 3.1 PCI-E card to use the official link cable. Headset would show as connected but to a USB 2, so I got a Adapter from Amazon C to A and now it works. Full Data and Power. 

  • enigma01enigma01 Posts: 764
    3Jane
    The_Kingpin66 said:
    Same here, after I installed a usb C 3.1 PCI-E card to use the official link cable. Headset would show as connected but to a USB 2, so I got a Adapter from Amazon C to A and now it works. Full Data and Power. 

    Not sure if have exactly the same issue... When connected to my Thunderbolt / USB C 3.1 Gen 2 the Quest does show as connected as USB 3.0:


    These above devices (PCI Bridge and USB Root Hub) only show when the Quest is connected to my USB C port, when connected to my USB Type A 3.1 Gen 1 only the 'Quest' Device is displayed. 




    But Link will not launch, works fine connected with my USB A to C cable. 
  • The_Kingpin66The_Kingpin66 Posts: 4
    NerveGear
    This may sound stupid, but try turning on public beta join with oculus app on your pc. It will download a newer version of the software. It won't work because it then says you need to update the software on the quest headset  And you can't  So, back on your pc turn off public beta and let "update" again. Also to be sure you have the latest drivers for your chipset. I know it's not much but give it a try  
  • dandolan315dandolan315 Posts: 1
    NerveGear
    Same issue here, I am using the party link USB converter and it's hit or miss. Sometimes it works, other times it doesn't. No rhyme or reason, different USB ports, lots of restarts, lots of USB power setting tweaks... All of the above that others have done in this thread. Why didn't oculus consider the thousands of PCs that have USB 3.0 version A on them? That connector is like.......... the most popular... of all time? Seems like a big swing and a miss to me, and prone to lots of issues with third party adapters. I'm returning mine. Not worth the $80. 
  • J-TrickyJ-Tricky Posts: 6
    NerveGear
    Same issue here, I am using the party link USB converter and it's hit or miss. Sometimes it works, other times it doesn't. No rhyme or reason, different USB ports, lots of restarts, lots of USB power setting tweaks... All of the above that others have done in this thread. Why didn't oculus consider the thousands of PCs that have USB 3.0 version A on them? That connector is like.......... the most popular... of all time? Seems like a big swing and a miss to me, and prone to lots of issues with third party adapters. I'm returning mine. Not worth the $80. 
    The reason Oculus didn’t go type A is for a few reasons.

    1. Maximum recommended length is only 10ft. With their optical cable they are able to get 16+ feet. Also It would be bad business and cause many issues if they ignored those recommendations 
    2. Type A has lower bandwidth (In the future, higher bandwidth might be necessary)
    3. Type A can not support fast charging. This Keeps the headset fully charged while gaming. Although Type A does charge, it does it at a slower rate and therefor the headset depletes faster than it charges and will eventually die after many hours of gameplay. This probably isn’t an issue for most people however oculus is trying to give the best possible experience and highest quality cable. 

    I think many of the issues we are seeing are simply software and driver related (seemingly mostly related to Thunderbolt 3 ports) and will eventually be ironed out. It sucks for those of us that are having problems but we must also remember that Quest Link is still in Beta so we can’t expect flawlessness at this point. 

  • iTesla8iTesla8 Posts: 106
    Art3mis
    Maybe Oculus can enable the devices remotelly, so after they decide to enable it will work for everyone. :D
    My Own PC Build: NZXT Source S340 White > Corsair RM1000i > Asus ROG Strix Z270F Gaming > CPU Intel i7-7700K 4.5Ghz > Deepcool Captain120 EX > RAM KHX2400C15/16G | 4pcs = 64GB > Asus GTX1070 Dual O8G > Samsung U32J59xUQ 4K > Realtek High Definition Audio > Intel SSD 760p Series PCIE/NVMe M2.1 1TB > Intel SSD 600p Series PCIE/NVMe M2.2 1TB > AZIO Retro Classic Copper > Razer Mamba Hyperflux = Oculus Quest/Link
  • enigma01enigma01 Posts: 764
    3Jane
    J-Tricky said:
    I think many of the issues we are seeing are simply software and driver related (seemingly mostly related to Thunderbolt 3 ports) and will eventually be ironed out. It sucks for those of us that are having problems but we must also remember that Quest Link is still in Beta so we can’t expect flawlessness at this point. 
    So I think I have demonstrated your theory wrong in my situation (sorry! lol)...

    I wanted to try rule out any issues with my drivers etc causing Link not to work when using the Official cable connected to my Thunderbolt 3, so I borrowed a 1m (I know too short for practical gaming, it was just to test) Cable Matters 3.1 Gen 2 type c to type c Thunderbolt 3 compatible cable (Amazon ASIN B07QDZV9PY) 

    Connected the Cable Matters cable to my Thunderbolt 3, and guess what... Link launched and worked just fine, I was able to launch Asgards and everything seemed to work fine with no stutters etc. My official cable would not launch to Link at all. 

    So, if the issue I am facing with my Official Oculus link cable not working when connected to my Thunderbolt 3 is software / driver related. Then when does the Cable Matters cable launch Link just fine when connected to the same port? 
  • h.r.gargih.r.gargi Posts: 165
    Art3mis
    Found another thing: What is not working is a "Hub" Please for those who the cable is not working: Unplug the cable from your machine. Shutdown your machine. Plug the cable into the headset FIRST! After your computer restarts plug the cable into your USB C Port. This seems to work! The Quest has to be attached to the Link cable before you connect it to your PC! The cable is a own device not a pure standard USB cable. It works for me for different reboots. 
    German Oculus Quest / Go / Link Facebook Group ... join us
    https://www.facebook.com/groups/oculusquestgermany/
  • kilogoldkilogold Posts: 32
    Brain Burst
    enigma01 said:
    J-Tricky said:
    I think many of the issues we are seeing are simply software and driver related (seemingly mostly related to Thunderbolt 3 ports) and will eventually be ironed out. It sucks for those of us that are having problems but we must also remember that Quest Link is still in Beta so we can’t expect flawlessness at this point. 
    So I think I have demonstrated your theory wrong in my situation (sorry! lol)...

    I wanted to try rule out any issues with my drivers etc causing Link not to work when using the Official cable connected to my Thunderbolt 3, so I borrowed a 1m (I know too short for practical gaming, it was just to test) Cable Matters 3.1 Gen 2 type c to type c Thunderbolt 3 compatible cable (Amazon ASIN B07QDZV9PY) 

    Connected the Cable Matters cable to my Thunderbolt 3, and guess what... Link launched and worked just fine, I was able to launch Asgards and everything seemed to work fine with no stutters etc. My official cable would not launch to Link at all. 

    So, if the issue I am facing with my Official Oculus link cable not working when connected to my Thunderbolt 3 is software / driver related. Then when does the Cable Matters cable launch Link just fine when connected to the same port? 
    I'm unable to check the cable you tried on Amazon. No sure how to search via ASIN, regular searching for 'B07QDZV9PY' returns zero results.
    Remember, that not just any Thunderbolt cable will do. The whole point here is that Oculus is selling a Fiber Optic cable. Your test will only be valid if you used such a cable. Judging by the length (makes no sense to manufacture a 1m fiber optic cable), I guarantee you have a copper wire - you're comparing apples to oranges at that point.
  • kilogoldkilogold Posts: 32
    Brain Burst
    To understand it better, this is my explanation on the matter --- which I'm still waiting for an expert to validate:
    kilogold said:
    kilogold said:
    Since I don't know whether my work machine should ever work with this cable, I'm going to return the Official Cable at this point and get the alternative cables... 

    I'm actually depending on Oculus Link for development, and trying to get the Official Link Cable working has been a drain of company time & money. 
    So... I'm still trying to solve this mystery - and I am damn sure my boss is going to kill me for beating this dead horse... Maybe I'm stubborn...

    I think I have learned something... But I'm in dire need of an expert's input on this.
    There's a recurring theme in this issue thread - most of us are attempting to connect via Thunderbolt, and we are not alone:
    On that last reddit post:

    Cables: I got the recommended Anker cable with the Amazon basics extension which gives me a total of 10 feet. Though both cables work in general, the extension cable won’t be recognized by link if you connect it through a USB A port. I connected a USB C hub to the Thunderbolt port which gives me 3 additional USB A ports. Connected to one of those, both cables worked fine in conjunction. Disclaimer: Boneworks didn’t run as smoothly and froze several times with the extension cable so I guess the longer the better doesn’t apply here. But in general I think that connecting your cable through the Thunderbolt port (I didn’t have a USB C to USB C cable) will give you a better connection especially when your are on a slower PC.

    According to Wikipedia:
    Thunderbolt 3 has limited power delivery capabilities on copper cables and no power delivery capability on optical cables. Using USB-C on copper cables, it can incorporate USB Power Delivery, allowing the ports to source or sink up to 100 watts of power.

    Call me crazy (or ignorant) here but...
    It seems to me that anyone reporting stable success with Thunderbolt 3, is proxying through some sort of copper connection, instead of a direct optical connection (using adapters, hubs, etc.). It makes sense that copper wires work because they follow USB protocols to draw power, but perhaps a pure optical connection is not instructing the hardware to draw the expected amount of power to operate an Oculus optic cable. By using a typical adapter, the computer only sees a "copper USB cable connection", which happens to actually be an optical cable on the other end of the adapter, thus provides some expected amount of power.
    I'm guessing the Oculus proprietary drivers (not the hardware USB drivers) are expecting the power traffic to match a copper wire's power consumption to determine a valid connection for Oculus Link.

    Because the power traffic differs in optical, perhaps the intermittent Thunderbolt success is that lucky timing (race condition) between the Oculus driver sampling a power consumption and an optical connection being recognized. It's almost as if there's a tiny window when the optical cable connection happens to consume about as much power as a copper cable...?
    Since optical cables provide no power, there must be some copper in the Oculus Link cable, if it's able to charge the Quest, right?

    tl;dr....
    Maybe the Oculus driver is not programmed to handle a Thunderbolt connection?
  • enigma01enigma01 Posts: 764
    3Jane
    kilogold said:
    Your test will only be valid if you used such a cable. Judging by the length (makes no sense to manufacture a 1m fiber optic cable), I guarantee you have a copper wire - you're comparing apples to oranges at that point.
    It was a copper cable, the purpose of my test was to establish whether the issue with Link not working when connected to my Thunderbolt was in relation to my computer drivers not working correctly. As Link did work, my drivers must be okay right? I had missed your previous comments in relation power. When you say 'Maybe the Oculus driver is not programmed to handle a Thunderbolt connection', do you mean specifically when using the Oculus Fibre cable, as Link worked for me as mentioned previously using my Thunderbolt, but a copper only cable?
    kilogold said:
    Since optical cables provide no power, there must be some copper in the Oculus Link cable, if it's able to charge the Quest, right?
    I am assuming the Oculus Link cable works in a similar manner to Cornings Fibre USB cable https://www.corning.com/optical-cables-by-corning/worldwide/en/products/usb-optical-cables.html. Which does have a copper conductor element. 


    h.r.gargi said:
    Found another thing: What is not working is a "Hub" Please for those who the cable is not working: Unplug the cable from your machine. Shutdown your machine. Plug the cable into the headset FIRST! After your computer restarts plug the cable into your USB C Port. This seems to work! The Quest has to be attached to the Link cable before you connect it to your PC! 
    I just tried this and still didn't work for me. Powered on my Quest and waited to load up fully, connected Oculus Link cable then connected to my Thunderbolt 3 from a freshly booted computer, I still got the 'PC can't be detected' message from within the headset. 
  • cnorton76cnorton76 Posts: 1
    NerveGear
    edited January 13
    I am having similar issues with the official Quest Link cable. I have an Alienware 17R4 and everything works perfectly when connected to the side USB-C port. When moving to the Thunderbolt 3/USB-C port, the headset shows "PC Not Detected" error message everyone else is getting.
  • kilogoldkilogold Posts: 32
    Brain Burst
    edited January 13
    enigma01 said:
    When you say 'Maybe the Oculus driver is not programmed to handle a Thunderbolt connection', do you mean specifically when using the Oculus Fibre cable, as Link worked for me as mentioned previously using my Thunderbolt, but a copper only cable?

     Ah, yes, excuse my incomplete phrasing.
    Indeed, I meant that perhaps the driver assumes a copper connection (because there is some copper), and therefore expects a particular power consumption, which never occurs because the cable is actually fiber optic. Therefore, a connection is not properly established.

    This is only an assumption though - because I've managed to connect via Oculus Link Cable a handful of times, though the repro steps seem to always change, leading me to believe this is a race condition issue:
    kilogold said:
    Because the power traffic differs in optical, perhaps the intermittent Thunderbolt success is that lucky timing (race condition) between the Oculus driver sampling a power consumption and an optical connection being recognized. It's almost as if there's a tiny window when the optical cable connection happens to consume about as much power as a copper cable...?

    Furthermore, your test was only testing the Windows driver, which never really was an issue AFAIK, because Windows does seem to recognize the device regardless. You can see the device in device manager. Oculus app does also detect the device is connected. So this also leads me to believe it's an Oculus driver, not a Windows driver. There's nothing we can install to fix this - Oculus would have to simply fix how a Fiber Optic USB connection from a Thunderbolt is detected, which is closer to the hardware level, aka a driver.

    Edit:
    To test my theory, I'm tempted on buying this:
    https://www.amazon.com/dp/B07MBWH7QG/ref=cm_sw_r_tw_dp_U_x_HXphEbW4NNMB4

    Does anyone have one of these perchance? I only need it for a test.

    My hypothesis is that this will seemingly create a "copper connection" from the computer's end, thus providing usual copper-cable power output that which shall drive the fiber optic cable.
    In other words:
    Fiber optic requests too little power. Make the cable seem copper in order to receive more power than the fiber cable is requesting.


  • nschlipnschlip Posts: 21
    Brain Burst
    kilogold said:
    enigma01 said:
    When you say 'Maybe the Oculus driver is not programmed to handle a Thunderbolt connection', do you mean specifically when using the Oculus Fibre cable, as Link worked for me as mentioned previously using my Thunderbolt, but a copper only cable?

     Ah, yes, excuse my incomplete phrasing.
    Indeed, I meant that perhaps the driver assumes a copper connection (because there is some copper), and therefore expects a particular power consumption, which never occurs because the cable is actually fiber optic. Therefore, a connection is not properly established.

    This is only an assumption though - because I've managed to connect via Oculus Link Cable a handful of times, though the repro steps seem to always change, leading me to believe this is a race condition issue:
    kilogold said:
    Because the power traffic differs in optical, perhaps the intermittent Thunderbolt success is that lucky timing (race condition) between the Oculus driver sampling a power consumption and an optical connection being recognized. It's almost as if there's a tiny window when the optical cable connection happens to consume about as much power as a copper cable...?

    Furthermore, your test was only testing the Windows driver, which never really was an issue AFAIK, because Windows does seem to recognize the device regardless. You can see the device in device manager. Oculus app does also detect the device is connected. So this also leads me to believe it's an Oculus driver, not a Windows driver. There's nothing we can install to fix this - Oculus would have to simply fix how a Fiber Optic USB connection from a Thunderbolt is detected, which is closer to the hardware level, aka a driver.

    Edit:
    To test my theory, I'm tempted on buying this

    Does anyone have one of these perchance? I only need it for a test.

    My hypothesis is that this will seemingly create a "copper connection" from the computer's end, thus providing usual copper-cable power output that which shall drive the fiber optic cable.
    In other words:
    Fiber optic requests too little power. Make the cable seem copper in order to receive more power than the fiber cable is requesting.


    I and several others have already tested this theory in another post on this forum, and indeed it does fix it. If you use a USB C to A converter (like the link you posted) the official Oculus link cable will work. It's still irritating we have to use a converter just to get this $80 cable to work.
  • enigma01enigma01 Posts: 764
    3Jane
    nschlip said.
    I and several others have already tested this theory in another post on this forum, and indeed it does fix it. If you use a USB C to A converter (like the link you posted) the official Oculus link cable will work. It's still irritating we have to use a converter just to get this $80 cable to work.
    The link he posted was a USB C extender not a USB C to A. He plans to try this with a Thunderbolt 3 port. 
  • MidnightDisplayMidnightDisplay Posts: 9
    NerveGear
    Have the same issue on my Dell Precision 7530 laptop. (Quadro P3200, 2x USB3 A and 2x USB C Thunderbolts on board)
    The USB A to C copper cable I got from Amazon does work well for a while. However, disconnects when the laptop starts bursting the cooling fans. USB A loses power for a split second when the fans switch on, I guess??
    To avoid that I bought the official link cable and... it doesn't work at all!
    I have 2 USB C thunderbolts I tried it with. Behaves exactly as described by @kilogold, device is "connected" but VR doesn't run.
    Going to try A to C adapter to test it with the USB A ports on the other side.

    Does anyone have any speculations on whether this will ever be fixed? Can this be fixed at all?
  • nalex66nalex66 Posts: 5,441 Volunteer Moderator
    If it was a power fluctuation issue causing the drop-outs, you might be able to fix it by running I through an externally-powered USB hub.
    i7 5820K @ 4.25GHz | EVGA GTX 1080 SC | Gigabyte GA-X99-UD4 | Corsair DDR4 3000 32GB | Corsair HX 750W
    SSDs: Intel 660p M.2 2TB, Samsung 860 Evo 1TB, 850 Evo 1TB, 840 Evo 1TB | Startech 4 controller PCIe USB 3.0
  • MidnightDisplayMidnightDisplay Posts: 9
    NerveGear
    nalex66 said:
    If it was a power fluctuation issue causing the drop-outs, you might be able to fix it by running I through an externally-powered USB hub.
    Well, I guess the only way to find out is to get one. Which I don't have atm.

    My thinking was: "I better buy the Official Link Cable to avoid all the hackery-tinkery." So I did.
    Such a shame these Thunderbolt 3 ports refuse to run Oculus Link VR. Or Oculus Link VR refuses to run with them.
    I double-checked that all of the chipset drivers are up to date. And they are.
    I have no issues running 2 additional monitors and other peripherals through the DELL dock that hooks up to those two ports when I'm at work. So they must be okay.
  • enigma01enigma01 Posts: 764
    3Jane
    edited January 14
    nalex66 said:
    If it was a power fluctuation issue causing the drop-outs, you might be able to fix it by running I through an externally-powered USB hub.
    I can’t find anywhere on the Oculus site a description of the computer requirements for the Oculus official cable to work (there are Link system requirements, but not cable) If externally powered hubs, adapters etc are required then the cables requirements are not adequately described. The only thing I can fine is ‘USB 3.2 Gen 1 Signalling 5 Gbps USB 2 backwards-compatible‘, which Thunderbolt 3 should support, correct? 

  • nalex66nalex66 Posts: 5,441 Volunteer Moderator
    enigma01 said:
    nalex66 said:
    If it was a power fluctuation issue causing the drop-outs, you might be able to fix it by running I through an externally-powered USB hub.
    I can’t find anywhere on the Oculus site a description of the computer requirements for the Oculus official cable to work (there are Link system requirements, but not cable) If externally powered hubs, adapters etc are required then the cables requirements are not adequately described. The only thing I can fine is ‘USB 3.2 Gen 1 Signalling 5 Gbps USB 2 backwards-compatible‘, which Thunderbolt 3 should support, correct? 

    Yeah, it shouldn't require a powered hub, I was just suggesting that it would be a way to test the above poster's hypothesis that power fluctuations were causing his disconnects. In theory, power fluctuations shouldn't impact anything except charging.

    The problem may well be with the USB and Thunderbolt ports (or the drivers for those ports). We've seen all sorts of USB problems since the release of CV1, due to some manufacturers playing fast and loose with USB standards.
    i7 5820K @ 4.25GHz | EVGA GTX 1080 SC | Gigabyte GA-X99-UD4 | Corsair DDR4 3000 32GB | Corsair HX 750W
    SSDs: Intel 660p M.2 2TB, Samsung 860 Evo 1TB, 850 Evo 1TB, 840 Evo 1TB | Startech 4 controller PCIe USB 3.0
  • MidnightDisplayMidnightDisplay Posts: 9
    NerveGear
    edited January 14
    Just to avoid further confusion: my hypothesis about power fluctuations has nothing to do with the official cable. That was in reference to the copper cable I got from Amazon prior to getting the official.

    To summarize: cheap USB3 Type A to C copper cable works, but with random disconnects; whereas the official cable connected through thunderbolt 3 doesn't run at all.

    At the moment I have no means of testing it with the USB 3 A port (need adapter), nor do I have a powered hub. Thinking of getting C female to A male adapter.
  • nalex66nalex66 Posts: 5,441 Volunteer Moderator
    I've been using this C to A adapter with my official cable, and it's been working well for me.
    i7 5820K @ 4.25GHz | EVGA GTX 1080 SC | Gigabyte GA-X99-UD4 | Corsair DDR4 3000 32GB | Corsair HX 750W
    SSDs: Intel 660p M.2 2TB, Samsung 860 Evo 1TB, 850 Evo 1TB, 840 Evo 1TB | Startech 4 controller PCIe USB 3.0
  • MidnightDisplayMidnightDisplay Posts: 9
    NerveGear
    nalex66 said:
    I've been using this C to A adapter with my official cable, and it's been working well for me.
    Thanks for sharing this. I have now ordered a similar one from Amazon UK.
    fingers crossed...
  • MorknanoMorknano Posts: 5
    NerveGear
    First of all, sorry for my English
    I received links and inserted into the pc, but link does not connect. The connect your headeset screen remains on the app.
    My pc:
    win10 home - intel i9-9880h - 32 gb ram - nvidia geforce rtx 2080 with max-q.
    how do I set up links? Help me!!
  • enigma01enigma01 Posts: 764
    3Jane
    edited January 14
    Okay so this is crazy but.... I just got Oculus Link to launch with the Official cable connected to my Thunderbolt 3, by connecting the cable 'backwards!'. So connecting the angled part to my PC and the straight part to the headset! It doesn't appear to be by chance either, I've tried disconnecting and reconnecting several times and tried the cable back the other. Every time it worked when connected 'backward', but not the other way around! If you have been having similar issues as me when using Thunderbolt 3 please try this and let me know what happens! 
  • XeroldXerold Posts: 4
    NerveGear
    Update. I tried connecting the cable the other direction. ie the part that is supposed to go on the headset to the computer and viceversa and now it works. sounds dumb but it worked. Not sure how can I explain this!! 
  • enigma01enigma01 Posts: 764
    3Jane
    edited January 14
    Xerold said:
    Update. I tried connecting the cable the other direction. ie the part that is supposed to go on the headset to the computer and viceversa and now it works. sounds dumb but it worked. Not sure how can I explain this!! 
    So that’s worked for both of us! I really don’t understand why this is working either, but surely there must be some fault with the cables? They should surely work connected either way. Is this something similar to Oculus earphones being wired incorrectly when they were first launched?
  • MidnightDisplayMidnightDisplay Posts: 9
    NerveGear
    Just tried this out. Doesn't seem to work for me.
  • KillingYOUsoftlyKillingYOUsoftly Posts: 1
    NerveGear
    FIXED WITH C to A ADAPTER.

    I had a USB C to USB A adapter lying about, tried it and it fixed the 'No PC Detected' issue for me immediately.
    Seems to be a problem with the USB C connection on the PC end.

    Wouldn't let me post the link so here is the desc to search on Amazon UK:

    UGREEN USB C Adapter USB 3.0 A Male to Type C Female Converter Connector Support Fast Charge,5Gbps Sync,Audio,Compatible for iPhone 11,Samsung S10+ S9 S8 A70 A50 A20e,Google Pixel 3a XL,Huawei P30 P20



Sign In or Register to comment.