Recent Discussions
Authentication error
For some reason when I try to join multiplayer games it gives me an error message. On some games it says it’s because of authentication or validation issues, on others it doesn’t say something at all. I’ve been using every method I could find. I came here to see if it’s happened to anyone before and hopefully they know how to fix it.drlego.12310 hours agoHonored Guest1like2Commentsv85 quest 2 Black screen but boots through pc link.
I just had my quest 2 headset preform a auto update and when I came back a minute later it was on and booted but the screen is lit up but black non responsive. I plugged it into my laptop to check the issue, and then it auto booted into the pc link. From there I am able to back out and go to the regular standalone menu, everything works games apps but it says I am up to date but I believe the update is corrupt cause once I turn it off it boots back to the black screen. also to further my Idea I launched the boot loader and it said the device is corrupt. I don't have anything I really care about on the headset but would prefer not to do a firmware and total wipe. Any ideas? was totally fine before update.FriedtoastFried6 days agoExplorer2likes14CommentsLink seems to be fighting steamvr in a recent update
a tale as old as time, about 3 or so days ago i still had the old (and commonly agreed, better) UI in my quest pro, and i was able to play PCVR with no issue, today i boot up my pro, see the new, frankly worse UI, think nothing of it, try to launch steamvr and suddenly my headset loses connection to my pc entirely after about 5 seconds im certain this isnt my cable as its brand new and i tested it by jiggling the wire at the base of my headset and my pc's port, im also almost certain its not the link app itself as the last update was just over a week ago, i last played around Wednesday with no issue side note: we really do need the option to turn off forced updates, on both headset and link app, it would install a LOT of trust the community has back into metaKidDexo10 days agoProtege0likes2CommentsHand Tracking suddenly stopped working in Link
Yesterday I was playing Maestro through PCVR and everything was working fine. I quit the app to play other games then when I came back I noticed that hand tracking stopped working entirely within the Link app. It works normally everywhere else, even Virtual Desktop. Anyone have a solution? I tried disabling and enabling Hand tracking and reinstalling the Link app on PC to no avail.ipdiot11 days agoHonored Guest0likes0CommentsNow you can't change bit rate anymore ...
The latest version of Meta Horizon Link (PTBeta), now give you the ILLUISION of everything going just amazing. You can put whatever bit rate you want in DebugTool ... from 10 to 2048mbits ... and you will have an smooth experience, no stutter, no jumps, everything going AMAZING! ... UNTIL! ... You realize... wait a minute! ... I can put 10mbits to 2048mbits as Encoding Bitrate ? ... Great but! ... WHY I don't see ANY DIFFERENCE on IMAGE QUALITY? ... Oh no!, yep ... the bit rate it's FIXED now (I don't know at what value, maybe the default one), no matter what number you put, and you can even confirm the number with the Performance Graph in the DebugTool, with the "Oculus Link DETAILS" option .. and check that your bitrate value it's there. But it's NOT USING IT AT ALL. So, if you quit the beta version, you go back to a v83, and there it's everything as bad and messy/buggy/laggy/stuttery as we start posting this problems about 4 months ago now (since v83 got released), unless you use less than 300mbits. Thanks META!.AEFox17 days agoExpert Protege8likes45CommentsHorizon link
Hello, I am experiencing a persistent issue with my Meta Quest 3 when using Meta Quest Link via USB cable. The issue started only after a recent headset software update. Before that update, Quest Link worked perfectly with the same PC, same cable, and same setup. Problem description: While playing PCVR games through Quest Link (USB cable), the image inside the headset suddenly freezes. Head tracking still works on the PC monitor. Audio continues to play in the headset. The PC still detects the headset correctly. Air Link works perfectly without any freezing. The issue only happens with wired Link. Additional details: After the freeze occurs, the Meta Horizon Link app sometimes shows: “No access to Link service”. The headset remains connected, but the status indicator changes to an orange dot. Restarting the following processes temporarily fixes the issue: OVRServer_x64.exe OVR Redir OVR Service Launcher After restarting those services, Link works normally again until the issue repeats. Troubleshooting already attempted: Reinstalled Meta Horizon Link completely. Disabled USB power saving in Windows. Disabled Hardware Accelerated GPU Scheduling (HAGS). Restarted Oculus/Meta services. Tried different USB ports. Confirmed that Air Link works correctly. The issue persists consistently only with wired Link. Based on testing, this appears to be a Meta Link runtime/service issue introduced after a Quest software update. Could you please: investigate whether this is a known issue; provide any available fix or workaround; or advise whether a firmware/runtime rollback is possible? Thank you.leone101418 days agoHonored Guest0likes1Commentv85/v2.1.1034 Passthrough Loop
I put this on Reddit also posting here in case it's a bugged update? Ok so this is my issue after Feb 27th v2.1.1034 Update: 1. The Problem: v85/v2.1 "Passthrough Loop" AI advises: This specific flickering issue (cycling between Home and Passthrough) is a known bug associated with the v85/v2.1 update. It appears to be tied to a conflict between the new "Navigator" UI and the headset's tracking/boundary service. Why it happens: The OS is essentially "crashing" the immersive home environment and falling back to Passthrough as a failsafe, then attempting to reload the environment again. The "Double Tap" Fix: Manually forcing Passthrough works because it tells the OS to stop trying to render the immersive environment, which bypasses the crash loop. 2. Process: Meta Software Update Tool Attempted resolution: I proceeded with the Sideload Update - update successfully loaded but.... Issue persists > Goto 1. LOL. So right now I will perhaps await the next meta update which may fix my problem before attempting a factory reset and linking accounts up etc... > If I manually enable pass through, I can get to quick access menus etc. so could update from there when next update available. > I haven't tried - PC Wired Link yet, so hopefully can get to MSFS SIM I use. > For the moment, standalone usage is a no go. Note: > I do have WhatsApp on the Quest which I know is active and in past updates I've seen this crashing in the background via notifications message things popping up. That has not happend this time but I think the Q2 may be struggling in my case as per above, something is causing it to crash. > I recently starting testing the 3rd party Immersive App on Q2 with it's version of remote desktop and virtual second monitor feature it can use with a laptop, as native Meta RD can't do that.....but I'm assuming nothing is running in BG with that app if it's not being used...... META / Anyone - any thoughts?SolvedMorpheusXII23 days agoProtege1like17CommentsUnity Editor Crash During Play Mode with Link and Hand/Body tracking
Description: Since updating to Meta Horizon Link v85.0.0.239.552, developers using Unity 6 experience an immediate Crash to Desktop upon entering Play Mode. The crash occurs during the initialization of XR tracking subsystems. The error is originating from XR_EXT_hand_tracking.dll and/or XR_FB_body_tracking.dll located in C:\Program Files\Meta Horizon\Support\oculus-runtime\client-plugins\x64\. Environment Details: Unity Version: Unity 6.2 (6000.2.14f1) Meta Horizon Link Version: 85.0.0.239.552 (85.0.0.239.552) Horizon OS Version: 2.3 (Build 5208318.1010.520) Error Signature: Exception Code: 0xc0000409 (Stack Buffer Overrun) Faulting Modules: XR_EXT_hand_tracking.dll and/or XR_FB_body_tracking.dll Path: C:\Program Files\Meta Horizon\Support\oculus-runtime\client-plugins\x64\ Workaround: The .bak Method If you are encountering this crash and need to continue development using controllers, you can "hide" the unstable tracking DLLs from the Unity Editor. This bypasses the memory fault during the Play Mode handshake. Close Unity and the Meta Horizon Link PC app. Navigate to: C:\Program Files\Meta Horizon\Support\oculus-runtime\client-plugins\x64\ Locate XR_EXT_hand_tracking.dll and XR_FB_body_tracking.dll. Rename them by adding .bak to the end (e.g., XR_EXT_hand_tracking.dll.bak). Restart Unity. Note on PTC: This version (85.0.0.239.552) is currently circulating in the Public Test Channel. If you are enrolled in PTC, opting out may roll you back to a stable version, though the .bak method is a faster fix for those who need to stay on v85/Horizon OS 2.3 for other features. Note on Builds: This only affects the PC Link Runtime used for Editor Play Mode. Native Quest builds (.apk) are unaffected as they use the headset's internal drivers; tracking will function normally on-device. Link to first access post of same issueWellPlayedStudios30 days agoMHCP Partner14likes4CommentsHorizon Link v85 issues with SteamVR?
Earlier today (1/28/26) I was using my Quest 3 to run SteamVR, worked fine. A couple hours later, after not being on VR for most of the day, decide to get back in, boot up Horizon Link App, hit with an update. After update, go to open SteamVR, to find I'm hit with a "VRApplicationError_IPCFailed" from Steam several times, never able to get into SteamVR. The ONLY thing that has changed in the last 12-ish hours is that I updated to v85. Should I look for a workaround or just wait for another patch?Isopod331 month agoHonored Guest1like20CommentsI factory reset my quest 2 headset and the app won't unlink
So i was having charging and memory issues so i factory reset my headset and the headset reset but i went onto the app to relink it but the app says it's still connected and i can't go into it's settings. It says "headset not connected" on the app. What do I do?Ooga_Booga2171 month agoHonored Guest0likes1Comment