01-04-2020 05:49 AM
01-13-2020 12:50 PM
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?
01-13-2020 12:52 PM
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:
- https://www.reddit.com/r/OculusQuest/comments/ek5pbw/oculus_link_pc_not_detected_official_cable/
- https://www.reddit.com/r/OculusQuest/comments/e9loy4/oculus_link_setup_for_notebooks_and_slower_pcs/
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?
01-13-2020 01:27 PM
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.
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?
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!
01-13-2020 02:39 PM
01-13-2020 03:21 PM
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?
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...?
01-13-2020 04:01 PM
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.
01-13-2020 04:04 PM
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.
01-14-2020 01:35 AM
01-14-2020 04:29 AM
01-14-2020 05:13 AM
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.