Quest 3 — Still no PC audio when using Link via USB-C (2025)
Hi everyone, I am reopening this issue because it still happens in 2025. My Quest 3 loses all PC audio when using Link cable. Windows shows “Oculus Virtual Audio Device” and the audio meter moves, but there is no sound in the headset. Cable has been tested by the app and works at full speed. If I use the “Repair” option in the Meta/Oculus PC app, the audio works again. But after a few days, the problem returns and I have to run Repair again. This happens almost every week. This makes the headset annoying to use because repairing the app takes several minutes and should not be necessary for basic audio output. Why this is a problem: -Repairing the app every time: takes several minutes -closes services and restarts the PC app -sometimes resets parts of the configuration -shouldn’t be necessary for such a basic feature What I already checked: -Oculus Virtual Audio Device set as default in Windows -Volume and sound device settings are correct -Good USB 3 cable and port -Quest audio works fine in standalone mode -Windows 11 fully updated -Meta PC app fully updated What I am looking for: Are other users still experiencing this? Does anyone know what keeps breaking the audio driver? Is there a permanent fix that avoids repairing the app constantly? Meta support: when will this known issue be solved??? Thanks in advance for any help or new information.107Views2likes6CommentsEye Tracking with Meta Quest Link
Hello everyone! I am trying to trigger eye tracking via Unity directly in the Unity Editor with Meta Quest Pro. When I build an apk, eye tracking works. But it doesn't work via Meta Quest Link. I have read repeatedly over the last few weeks that there have been problems with Quest Link. I wanted to ask if anyone has recently been able to implement a project in which eye tracking worked via Meta Quest Link and what tools were used. I have already read that ALVR via SteamVR is an option for transferring eye-tracking data, but I had problems with the packages. (My understanding is that you then need the SteamVR package and XR Interaction Toolkit instead of the Meta All-In-One SDK). As a side topic, another question would be whether it is currently normal for passthrough transmission on the Quest Pro to be very slow with the current Quest Link version, but to work normally with the Quest 3. My preference would actually be to do everything with the Meta Quest Link connection and the Meta Quest All-In-One SDK. However, if passthrough and eye tracking don't work via Quest Link, a solution with SteamVR may be necessary. Thank you for taking the time to read this. I would appreciate any tips.24Views0likes0CommentsQuest 3 link cable keeps disconnecting
I just got my new Quest 3 3 days ago. When I connected it through Oculus link app and a genuine Oculus link cable to my PC the connection dropped almost immediately. After reconnecting I noticed that even the slightest movement of the plug of the link cable (while it is plugged in) results in a disconnection. This makes connecting to a PC with a link cable practically unusable as almost every time I move I get disconnected. I want to add that there is nothing wrong with the cable. I use the same cable to connect to my old Quest 2 and my link connection is absolutely solid. Have I been just very unlucky or is there a design flaw or fault of the USB port on the Quest 3 headset? I had a chat via live support. I am now expecting an email from the support. I guess I will need to wait to see what happens next...Solved27KViews0likes41CommentsOcculus Rift S issue with Meta Quest Link app.
Hello, I recently moved and have tons of space to set up my VR. I installed all the up to date drivers for according to my NIVIDIA App on my PC. I installed Meta Quest Link and I am currently trying to do the initial set up where you pair your remotes and headset to the app and draw the floor space. When I open Meta Quest Link it just stays as a black screen and my headset display has black floor, white sky, and 3 circles that just blink in the middle. I have audio from my headset as well. I am not sure what to do, as I am unaware of what is the underlining cause to my issue I am experiencing. I have attached a screen shot of what loads up on my PC: If anyone else has had this issue with your Rift S and the Meta Quest Link, please feel free to drop some suggestions. Thank you for your time reading this people!101Views0likes1CommentLinux Support???
I'm really disappointed that I wasted $400 on a Rift S just for it to become a paper-weight since I don't want to use Windows on my computer. I have no clue why a multi-billion dollar company can't afford to support more than one operating system. I'm by no means expecting perfect support with no performance issues or hiccups on the less popular OS's, but having the headset be COMPLETELY UNUSABLE is not at all excusable. Just let me use the headset, and I'll do the optimizing myself. It's pretty embarrassing that Valve, a company valued at $8 billion, can comfortably support Linux and Windows almost flawlessly on their headsets, but Oculus, which is owned by Meta, a company valued at $572 billion can only support Windows. I understand the tone may seem harsh, but as someone who spent $400 dollars on the thing, I should have the right to use it on whatever computer I see fit even with less than desirable performance.18KViews25likes28CommentsUsb C not connecting to quest link
Hello, i recently got my quest 3, i love it and am happy i decided to purchase it, however to date my only issue is that my computer or my quest will not recognize each other when connected with a USB C to USB C. i have had success with the same Cable using a USB A adapter on one end and tried to use the cable that came with the quest aswell. The quest will charge off of both ports but will only connect to quest link off of the USB C to USB A. Both ports are running usb 3.0. My computer is a Lenovo Legion Tower 7i Gen 8 (Intel) Gaming Desktop, i have a 4080 with a I7-13700KF, the usb ports i’m using are numbered 8&12 on the tech specs that i am sending a link to. It will only connect to quest link off of port 12 but still draws power (i think more) off port 8. I have tried to flip the cable as stated in the original post but no luck, please do inform me of any potential solutionsSolved13KViews1like19CommentsConsistent Unity Playmode Runtime Error when using Link after updating the Quest Link app
I updated my meta quest link app to version 71.0.0.167.524 on the date 9/30/2024. Since I have updated earlier this week, I have a new error that I face everytime I click into play mode in my editor with link. The error is "Microsoft Visual C++ Runtime Library Runtime Error! Program: This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information." I tested, around the error and it does NOT occur when running play mode normally or with the meta XR simulator, and it DOES occur 10/10 times when starting playmode with Quest Link open, which confirms the culprit. I searched the internet and the unity logs for more information but wasn't able to find answers. Please let me know if there are more logs that would be useful to attach from the Quest Link software. This error is blocking my work everyday this week, i'm working on a game that is about to ship, and now I cant get in headset to test in editor anymore. Its a shame I was just complementing folks at a meta about how much better link has gotten for developing mixed reality apps. The next things I will try are fresh installs of the project, fresh installs of the editor, then maybe a fresh install of windows. I hope this post gets noticed by others with this issue or someone at meta who can help fix it. Fingers crossed ill get another update any day here and I can get back to work. Versions and Info Windows 11 PC Quest 3 Connected via USB-C Unity Version:2022.3.20f1 Quest Link Version: 71.0.0.167.524 Quest Headset Version: 69.0.0.576.352.641228209611Views0likes0Comments