can't set oculus as active openxr runtime
i have a quest 2 and use it on link but it wont work at all because when i click the button here it just does nothing in the quest when i click enable link it loads for a few seconds and just reloads the home area (nothing happens) please help my quest 2 is unusable for pcvr like this and it seems like such a simple thingSolved180KViews12likes96CommentsQuest link not working with Quest 3
I just updated my Nvidia driver to the most recent version (537.58), and now Quest link just isn't working at all. Tried uplugging and replugging the link cable, nope. Tried restarting the headset, nope. Anyone else having this problem?Solved170KViews16likes156CommentsUSB 3.0 issues with Quest 2
I see lots of similar posts about things surrounding this issue but they usually get brushed off, I am hoping that making this post and outlining what I have done so far it may finally prompt a fix. Essentially the issue is that when connecting with a USB 2.0 connection, the link is completely stable, it reliably connects for several hours and even if the headset is removed and left to "sleep", it reawakens and is still successfully connected (team events in iRacing if you're asking). When using USB 3.0 however, the exact opposite is true, generally speaking in the best case scenario, when keeping the headset awake the whole time, I can sometimes get an hour before a disconnect, however, nearly every time it goes to sleep, it disconnects and sometimes the connection will be lost within minutes of launching with no explanation. For a bit of history, over the course of trying to find a solution to this issue I have: Used a USB A-C 3.0 cable, 2x USB C-C 3.0 cables (including Oculus' own), a USB A-C 2.0 cable, a USB C-C 2.0 cable, replaced my PC's motherboard with a Asus Prime Z-390A, so I would like to think this firmly rules out the frequently posed "solutions" such as better quality cables or using different ports. I have also tried resetting experimental features as I read that sometimes causes issues but this didn't have an effect, nor has making sure that video drivers and my motherboards firmware are up to date, disabled legacy USB support in my bios settings or ensuring there is no power saving settings activated on USB ports. The most frustrating part of all is that recently I did a factory reset of the headset 'cause I couldn't think of any other fix and seemingly this finally gave me a stable USB 3.0 connection using the official cable, which not only lasted until I disconnected it (several hours), but also through cycles of sleeping and waking the headset. I then didn't play for a week and Oculus app version 38.0.0.51.727 (38.0.0.51.727) / headset version 38.0.0.63.727.351486028 installed themselves and now I'm back to the same problem of 3.0 not working and 2.0 being absolutely fine, the factory reset and experimental features reset has not had an effect this time. To be clear, there have been no hardware changes at this time so given it did work as intended previously, it has nothing to do with cable quality or any mechanical issue. Any other insight of fixes that I have not yet tried would be appreciated, although mostly an indication that this is being sincerely looked into as a known issue not just brushed off as an outlier. Please let me know if you need any additional information and I'll post when I can.Solved92KViews9likes49CommentsMeta Quest Link not working
Hello, I used to be able to play on my VR with a link cable perfectly fine, but I recently got a new computer, and it doesn't work. I checked the requirements and my PC meets them without question, but whenever I try to connect the headset, my computer gives me messages like "Meta Quest Link isn't working correctly. Click here to check our support article." I checked that article, but nothing seemed to help. The Quest program on my computer shows that my headset is connected and ready to launch, and so does my headset, but when I launch it through the link cable, it just doesn't load, and it stays on a black screen. I've also tried connecting my headset through a USB hub instead of the actual computer to connect it through USB 3, but it still doesn't work. Is there any way I can troubleshoot it? Thank you!Solved29KViews3likes53CommentsLink error. [RCTVR_V8] [warn]: Animated: `useNativeDriver` was not specified.
Hi. Two days ago, Link started to throw this weird error I've never seen before: "Minified exception occurred; use the non-minified dev environment for the full error message and additional helpful warnings" I have to press a button to make it disappear but it happens again and again. Reading the logs, the error says: [RCTVR_V8] [warn]: Animated: `useNativeDriver` was not specified. This is a required option and must be explicitly set to `true` or `false` [RCTVR_V8] [error]: Error: Minified exception occurred; use the non-minified dev environment for the full error message and additional helpful warnings. Location: {"pathname":"/","search":"","hash":"","action":"POP","key":null,"query":{}} Breadcrumbs: Location: {"pathname":"/dash/landing/default","search":"","hash":"","action":"POP","key":"678u4i","query":{}} Breadcrumbs: Router[1].history.REPLACE(/dash/landing/default) Can't find anything related to this error around here. What is this error all about? Thanks!17KViews2likes10CommentsMeta PC software can't reach Meta Quest Link services.
as you can see in my screenshot somethings not right. ive searched the internet but i found nothing, i use windows and this error came when i installed the software and it went through a scan to verify everythings alright. I also tried the "repair" button many times and uninstalled and reinstalled the program a couple of times but its still not working. (also restarted my pc many times and i also have a stable internet connection.) Does anyone know what i could try?15KViews2likes24CommentsHand Tracking over Link still not working in Unity Editor
Hi, I have spent the last two years developing for the Quest 2, and recently got the Quest 3. It's a great device and I'm super happy with it. There is just one big problem standing between me and total developer bliss. How is it possible that we still don't have a stable, robust hand tracking implementation across the whole development pipeline in 2023? I'm confused as to how Meta envisions developers to take full advantage of their (really good) hand tracking tech, if there are consistent inconsistencies, fumbling around, trying seven different versions of all of the little SDKs, components, etc. Can someone please advise me on how to achieve a simple Unity scene using the standard Oculus Integration, where I can just click "Play" in the editor and get hand tracking working over my Link cable? So far I have gone through five different Unity versions from 2021-2023, even more different Oculus Integration SDK versions (v50-57), and three different headsets (Quest 1, 2 and 3). Nothing worked. The only way that I have managed to have hand tracking working in the editor via link is to use a long deprecated version of the Oculus Integration, where I had to manually select "Oculus -> Tools -> OVR Utilities Plugin -> Set OVRPlugin to Legacy LibOVR+VRAPI" from within Unity. Three things. First, this option is no longer available in the later Oculus Integration versions. Second, selecting this option explicitly disables the possibility of building for the Quest 2 and 3. So you'd have to switch back and forth between the old LibOVR+VRAPI and the newer OpenXR integration, just to get hand tracking working in the editor. Really? Third, we as developers cannot reasonably be expected to stick to this legacy API, as all of the newer mixed reality features, like scene understanding, spatial anchors, etc. are not supported in the old version. Hence I want to ask my question one more time: how does Meta expect people to develop for their platform? Please let me know if you have an answer to this dilemma, I am grateful for any pointers! Note: I am explicitly talking about hand tracking through the Unity Editor using Link, in the standalone Android builds it works fine and it's amazing to use! Best, MaxSolved9KViews3likes14CommentsNew drivers are required for Meta Quest Link
I've updated to the latest, non-beta for both the newly named 'Meta Horizon Link' software as well as the Quest 2 now on v83.0. The Meta Horizon Link software doesn't seem quite finished and ready for prime time. I have a persistent beam across the top of the app stating "New drivers are required for Meta Quest Link. Update now" - When I click "Update now", the app shuts but nothing more happens. I've waited several minutes thinking it might be doing something silently - it isn't. I then reopen the app which is a preceded by a 'Repair' screen. Getting back into the app, I see that same "Update now" button, click it but now it fails because the required services were stopped in the previous attempt. I restart the services and then the app, click the "Update now" button and we're back to point 1 with it closing the app and nothing happening. I've tried completely removing the app and its registry amends using Revo Uninstaller so I can completely start with a clean slate and the issue persists after a reset and re-installation. Is there a download url to the most recent link driver outside of the app available? Or is this a false notification due to a naming mismatch between the link driver and the newly named Horizon Link software? Many thanks in advance.7.3KViews6likes31CommentsQuest Link / Air Link suddenly stopped working today – session never starts
Device: Meta Quest 3 OS: Windows 11 GPU: NVIDIA RTX 5080 Connection: Air Link and USB Link (same behavior) Quest Link (both Air Link and USB Link) was working normally for months and was working earlier today. After ending a session and starting another one, Link stopped working completely. The headset is detected, the session initializes, but it freezes on the grey/purple Link screen and never reaches VR Home. Eventually the session drops or returns to the headset home. This is not a USB issue, not a network issue, and not a headset pairing issue. Important facts Same hardware and setup working for ~4 months Worked earlier today No hardware change No Windows reinstall No BIOS change No GPU change What I already tried Reinstalled Meta Quest Link multiple times Factory reset the Quest 3 Removed all Oculus / Meta registry entries Clean GPU driver reinstall with DDU Downgraded NVIDIA driver Tested both Air Link and USB Link Repair installation Restarted all Meta/Oculus services Reconfigured the headset from scratch None of the above resolved the issue. Observed behavior PC app detects the headset Session enters VR mode Streaming loop starts Grey / purple Link screen appears No image is ever presented Session freezes or terminates This indicates the session is created, but the compositor never presents a valid frame. Relevant log behavior From Service.log and LinkClient.log (same timestamps): VR session initializes Streaming starts Frames may briefly decode Compositor or transport fails shortly after Errors such as: Failed to read display driver information Graphics adapter state UNKNOWN Elevated Shared Memory failed to initialize Error -1002 Registry/config access failures after reinstall This points to a runtime or compositor state failure, not user configuration. Key point This did not degrade gradually. It stopped working suddenly today after previously working normally. That strongly suggests a silent Meta runtime update or a runtime state corruption that reinstall does not fully reset. Request to Meta Please confirm whether there was a Quest Link / runtime update today Clarify how to perform a true clean runtime reset (not just reinstall) Confirm if there is a known issue with Link compositor initialization Provide a way to roll back the Quest Link runtime At the moment, Quest Link is completely unusable despite supported hardware and exhaustive troubleshooting. I can provide full Service and LinkClient logs with timestamps if needed.Solved6.1KViews35likes88CommentsMeta Quest Link Infinite Loading
Worked fine since buying Quest 3 a month ago, was working yesterday, today it wont work, tried reinstalling the app, nothing, tried beta branch, nothing. my AMD graphics driver is up to date, it was literally working yesterday with no changes whatsoeverSolved5.5KViews0likes7Comments