Unity 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 issue
V85 Breaks Fixed Bitrate, ODT issues, sync issues
Dear Meta Developers, Please note the following about v85: A 2 year previously stable ecosystem with a wired high end PC (4090/5090) 2.5 gbps ethernet wired into a dedicated quest only wifi6e high end router. I ran fixed bitrate at 500 mbps for years with flawless results. I was extremely happy. Since v85 fixed bitrate breaks link completely it seems stuck at 10 or less mbps. I can sometimes get rid the low limit with putting 0 then enter or dynamic (tried overriding dynamic to 500 tried offset) but I now always have synchronization issues like vsync there is judder and latency. I tried everything all pc and quest and gpu settings - nothings works. Please fix. Thank you. Respectfully yours
Can't prevent app startup
This issue has been driving me up the wall. I don't allow any app to pop up on my screen after starting up my PC. No discord, web browser, or music until I tell my computer that I want those things opened. It annoys me to no end when I download a new app and find out that it wants startup rights. So I got the meta app a while ago but didn't use it much. Disabled startup through task manager--no problem! Then a few years and an update later, and suddenly it's starting up again. "No problem", I say, "I'll just disable it again. Maybe it forgot with the update, it happens!" And then it's somehow missing from task manager's list of startup apps. With a little bit of looking around online, I find that you need to disable the Oculus runtime stuff from the services menu now. So I do that, and it works until I update my app again. Little more digging later, and I find a way to manually add the app (Client.exe) to the startup folder, which then allowed me to disable it from task manager. This worked... for about a week, until I stupidly updated my app again. Now it's once again got the gall to open on startup every single time I boot my PC. I read somewhere that this is a bug... is that true, or is Meta just trying to get as much of that sweet, juicy background data collecting we all know Facebook loves so much? We may not know the true answer for sure, but I do know what answer they suggest by still running the app in the background after it's been closed. Just sayin. Any help with getting Meta off of my startup for good would be greatly appreciated. I've turned off app updates, and I won't be updating the app again anytime soon.
Meta Link v.85 infinite loading
Whenever I try starting up meta link my headset will display this image It will not stop loading and will spam my windows notifications about how my link isn't working and that I should check a support article that doesn't exist. I've tried every solution at this point including: Restarting pc and quest multiple times Blocking oculus outbound rules on firewall settings Clearing all temp file Relocating my link cable to a different USB port Blocking my ethernet before starting link Reinstalling and repairing meta pcvr app Trying to use airlink to play, doesn't work Does anyone have any other fixes I can use?
v85 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.PTC v85 - OVR Metrics Tool doesnt update in app from unknown sources
In the new update, while using the OVR Metrics Tool with persistent overlay enabled, it seems to work fine in a normal app, however any app launched from unknown-sources causes the OVR overlay to just stall and not update, until you either navigate the meta menu at which point it will start refreshing/updating again.
