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
Cannot complete Organization Verification by any method
Hello Support and everyone: We are a VR/MR game startup company from China, currently focusing on the development of Quest3 APP, we want to put our APP on the App Lab, but we have not been able to pass the "Organization Verification". When using the "Business Verification" method, the verification code will not be received, no matter email/phone/text message is the same, using the Chinese phone number/email address. When using the "Admin Verification" method, using all kinds of IDs, ID cards/passports/driver's licenses, you will receive an email saying "We can't use the ID you shared to verify your identity". I would like to ask if there are any Chinese developers who have similar problems and solutions, or can't pass the verification in China? Thank you.
Development of an audio-to-text transcription app for Oculus Quest 2 and 3.
I am developing an application for Oculus Quest 2 that converts audio into text, but I have encountered some issues. I tried using the SpeechRecognition API on a web page, but it doesn't seem to be compatible with the Oculus browser. I also tried installing Chrome, but that didn’t work either. I’ve explored alternatives like Vosk and PocketSphinx, but I haven't had success with them so far. My question is: is there any API or framework compatible with Oculus Quest 2 that would allow me to perform voice-to-text transcription? Any recommendations or guidance would be greatly appreciated. Thank you in advance for your help!window.requestAnimationFrame not working in newest 33.3 Meta browser in WebXR mode
I used window.requestAnimationFrame inside a WebXR app, which previously work fine in the Meta Browser, but it seems automatically update to 33.3 on June 3rd, and now this function only works when I press the Meta button to pop up the browser but not work at all when I hide the browser and enter the XR mode. Any helps? Maybe I need to change the function? But I don't see an alternative to count frames accurately. Basically I want to have a timeManager that supervise the timing of different assets in the app.
