Quest must be restarted while plugged in to be detected by Win10 PC on Developer mode
We are using the latest Oculus adb drivers, but the Quest in developer mode won't be detected by the PC once plugged in or started up whilst it is plugged in. The Quest seems to need to be plugged in while on, then restarted while still plugged in to be detected. Is this expected and desired behaviour? It creates a few extra minutes of hassle every day when setting the device up for building and testing on from a development PC.
Oculus App won't recognize Quest but Sidequest will.
For some reason, I have my Quest plugged into my PC but the Oculus app can't find it when I try and set up a headset. I am using a usb c to usb a Anker cord, all of the reviews online said that it worked perfectly with Oculus Link, my PC does not have a usb c (aka 3.0 I think) port, just usb a (aka 2.0 I think). I can go into the files on my Quest in the file explorer with no issue, I can sideload games onto my Quest with the Sideload application with no issue, but for some reason, I cannot get the Oculus app to recognize that the headset is plugged in. It keeps saying, "Connect Your Headset" and the only button I can click on is the one that says, "Quit Setup". I just want to play Minecraft VR but the Oculus app/software won't recognize my Quest. I'd really appreciate any help that I can get.
Oculus Quest + Intel RealSense D435i + Unity
Hello everybody, I'm designing a VR performance, in which the user would interact with a real-time point cloud of the space around them. I am using an Intel RealSense D435i depth camera (all the processing is done in the device) and an Oculus Quest, and I'm developing in Unity. My question is: Is it technically possible for the Quest to communicate with the RealSense camera, through the USB-C port ? If not, is it a hardware limitation (for example, the Quest can't even power the RealSense) or is it a driver / android library / unity sdk limitation ? So far, my test pointcloud-viewer project builds without errors and when I connect the Realsense to the Quest I get the familiar sound of the Quest recognizing that something connected to it, but the actual app does not show any pointcloud at all, and the depth camera is clearly inactive (no flashing laser, no IR illumination in the room when viewed in Passthrough mode). This is new ground, so any help would be greatly appreciated!UCB-C 3.0 showing as USB 2.0 with link cable after ADB driver install
Hi all, Need some help here as I am a complete rookie with VR. My new quest 2 was working well with link using the official link cable. After installing the Oculus ADB Drivers 2.0, the PC app now shows the following message: "USB 3 recommended". I am using the official cable, and it is plugged into the same USB-C 3.1 port. Any idea how I can get this working properly? Cheers.USB 3.0 doesn't work
I have a usb 3.0 type C and when i connect the usb to my laptop via "oculus link" this detect the cable as USB2.0 when it is not USB2.0 if not USB 3.0. I know the cable its USB 3.0 because i tried to connect the cable to a friend's laptop via "oculus link" and his Pc detect the clabe as USB 3.0 (2Gb/s) my in my laptop its detected as USB 2.0 (300mb/s)... You may can say : its a Usb controller driver fail, you must to update it... I already update several times de Chipset of my Motherboard and Bios drivers and all the rest of controllers, i tried also update the usb port via "device manager" and it still not working.... So where can be the problem?Games won't detect Oculus Link
I have a Oculus quest 2 and my PC is Alienware aroua R11 (I'm sure I miss spelled it). When I plug my cable into the USB 3.0 Port on my PC it tells me to use a 3.0 port even though I have it in one. I can load the oculus link but when I open ROBLOX the game doesn'y detect i'm in VR and puts me in the non-vr point of view (I do have unknown sourses on). I updated every driver I can see in device manager and that won't work. Is there a fix to this?
