Using a cable confirmed working by others (Amazon Basics USB 3 3M) and GTX 1650, 16Gb, Ryzen 5 3550H based laptop I'm having problems launching Quest Link! Headset is recognised and passes text in Oculus Desktop software and prompt appears in headset. When I launch in the headset I get a black screen with 3 moving dots. Shortly afterwards, just a black screen with the Guardian circle on the floor.
Anyone else had this?
3
Comments
(Surface Book with 940M GPU using the USB A to C cable that came with the Google Pixel.)
I thought it might have been because I wasn't in roomscale mode but I was unable to test.
AMD Ryzen 7 2700, GeForce RTX 2060 Super, 32GB, Asus B450 Motherboard
Corsair Hydro H100i | Samsung SSDs: 860 Evo 1 TB, 850 Evo 1 TB, 840 Evo 1 TB | Seagate BarraCuda HDD 3 TB
I had been having the exact same issues. At first I thought it was my wire as I got a different one from the Anker one recommended but the GeForce issue was what was causing me problems.
I had updated all my drivers and restarted a bunch of times. At times I did get it connected and working, if I unplugged the cable and replaced it, it would return to black screen.
This is probably because after a reboot, GeF Exp didn't have a chance to start up correctly.
I would ensurer your drivers are up-to-date, disable overlay, and restart both.
Able to connect without a single issue.
Just want to say thanks to who found this to be the problem and posted it here. Been following this thread for 4 days hoping for the answers and here they are.
Now back to my issue, it was due to USB controller, I found in the logs this:
Then I check in the Compatibility.json this:
"UsbBlackList": [
...
I checked in my devices and I have the "ASMedia USB 3.0 eXtensible Host Controller" and that's that. I don't know why that is not supported. Luckily my Nvidia card has an USB C (3.0) port and I got an adapter to from C to type A female (usb 3 compliant) and it worked. Even with a cable made of three segments alittle over 3 meters, since I don't have yet one long enough.
Long story short, it was the USB 3 controller not compatible/ black listed. You can check the json file/logs to get a hint what is wrong.
Now back to my issue, it was due to USB controller, I found in the logs this:
Then I check in the Compatibility.json this:
"UsbBlackList": [ ..
Long story short, it was the USB 3 controller not compatible/ black listed. You can check the json file/logs to get a hint what is wrong.
Basically, my problem was due to USB controller in my desktop not compatible(black listed by Oculus).
Check in device manager, Universal serial bus controllers (look for USB3) and see if yours is listed in the bellow black list. If so you will need use another usb controller, I used the one I have on the NVIDIA card, or buy one.