Voice and Haptics SDKs not 16kb aligned
I develop AR applications designed to run on both the Quest3 as well as Android/iOS devices in Unity. It would appear as though a couple of the aar/so files in the meta voice SDK and Haptics SDK are not 16kb aligned and cause issues when trying to deploy to the google play store (using the all-in-one package updated to latest at the time of this post, v81). Since both targets (Quest3 and Android) share build settings, it complicates deploying an APK that has these meta libraries in it. The files with issues are: mailto:com.meta.xr.sdk.voice@1613052ece81\Lib\Telemetry\Plugins\SDKTelemetry.aar mailto:com.meta.xr.sdk.voice@1613052ece81\Lib\Wit.ai\Lib\third-party\UnityOpus\Plugins\UnityOpus\Plugins\Androidunityopus.aar mailto:com.meta.xr.sdk.haptics@cd1f215a823c\Plugins\libs\Android\ARM64\libhaptics_sdk.so I did notice in the changelogs for v81 that several libraries were updated for 16kb alignment, it seems as though a few may have been missed. One big thing to note is that the two aar files DO NOT trigger the 16kb warning within the unity editor at build time, so the issue will only be caught once you upload it to the google play store for deployment.13Views0likes0CommentsIssue with Meta Interaction SDK v74 on Oculus-5.5-v74 Unreal Engine Fork
Issue Description I downloaded the Meta Interaction SDK (version 74) and integrated it into the Unreal Engine fork oculus-5.5-v74 from GitHub. The integration works correctly inside the Editor, and VR Preview runs without any issues. However, when I package the project for Quest and install the APK on the headset, the application: launches, shows a black screen for less than a second, then immediately crashes/auto-closes. When I disable the Meta Interaction SDK plugin and rebuild the project, the packaged application works normally on the device. This confirms that the crash is directly caused by the Interaction SDK during runtime on the Quest. What I Have Already Verified The plugin is properly added under /Plugins/runtime/OculusInteraction. Engine fork version matches the Meta SDK version (both v74). No conflicts in Editor logs. No errors during packaging. The crash happens only on device startup, not in VR Preview. Expected Behavior The packaged app should run the same way it does inside VR Preview. The Interaction SDK should not crash the application on Quest when the correct version is used. Request Could you please advise on: Whether Meta Interaction SDK v74 is fully compatible with the fork oculus-5.5-v74-openxr-asw-ffr. Any additional setup required to ensure correct initialization on Quest (permissions, XR loader, manifest changes, MetaXR modules, etc.). Whether this is a known issue for v74 of the SDK. If this fork requires a specific Interaction SDK variant different from the public one.58Views0likes2CommentsHow to achieve recognition of a set of dynamic gesture movements rather than individual actions.
Hello everyone, I’m wondering how to record a complete set of gesture movements for the Quest 3 to recognize—for example, having it detect when I stretch out my palm and wave, rather than only recognizing when I’m holding my palm still in front of me. Could anyone help me with this? Thank you so much. To be honest, the Quest 3’s user gesture interaction experience has left me a bit frustrated. I have to rely on my thumb and index finger for extended periods to perform operations—like making a fist and extending my index finger to click, or pinching the objects or interfaces I want with my thumb and index finger. It was okay at first, but after prolonged use, this puts a significant strain on my fingers. Moreover, it’s not smooth enough to fully integrate the operations into my daily life experience. So I want to make some attempts. I hope the Quest 3’s gesture interaction experience can be as smooth as that of excellent web front-end pages—seamlessly integrating into daily life like the ones shown in AR concept videos, rather than just generating a few virtual screens in front of you. At the very least, it shouldn’t keep straining my index finger anymore; my fingers are really sore. If you share the same thoughts or want to communicate with me, feel free to send an email to luoyiheng2005@outlook.com. I look forward to your emails.31Views0likes1Comment