Unreal - Use Take Recorder with Live Link for Hand Tracking as Motion Capture?
Hi everyone, I'm trying to record an animation in Unreal using the Hand Tracking of the Quest 3 and 2 as a motion capture and once recorded I need to export the animation for future use. When I record with the Take Recorder, the only things that move are the rotation and location of the Motion Controller Components. I searched for a Live Link connection but found only the tracking for body and face with Quest 2. Is there a function for recording the Skeletal Mesh movements of the hand with the Take Recorder? (I found this Post similar to my question but didn't know how to record the bone transforms.) Is there a Live Link connection for the Hand Tracking? I'm using the Meta XR plug-in and already set it for Hand Tracking only.
How To Build Hello_Xr sample with Android Version
Hi, I want to try how to write a VR APP with OpenXR SDK. I found Oculus had published OpenXR Mobile SDK: Actually, I don't know how to build hello_xr sample in OpenXR SDK for Android version. Does anyone know how to build this sample with Oculus OpenXR Mobile SDK? I appreciate your help.TransformRecognizerActiveState is never activating
I haven't been able to get a Transform Recognizer Active State to register as active. I have no issues with Shape Recognizer Active State. Are there any additional steps that are required in order to get a TransformRecognizerActiveState to work? I have also examined it with an Active State Debug Tree UI and it confirms that the shape recognizer is activating but not the transform recognizer. Here is my component setup: Can anyone see or guess what I might be doing wrong?
Unity + OpenXR + OVRSpatialAnchor + Passthrough = Wobbly models
Previously we were using the Oculus XR Plugin with OVRSpatialAnchors and passthrough and all was working as intended. We needed to switch from the Oculus XR Plugin to OpenXR (for a separate package) and managed to get everything working except for when we put an OVRSpatialAnchor on a model with passthrough active, the model appears to be very wobbly compared to it's intended stable state. Once the spatial anchor has been removed off the model it appears much more stable but obviously doesn't have the other characteristics of having a spatial anchor that we need. Does anyone know how to fix this? I saw this post with a similar issue and I updated the AndroidManifest.xml via the Oculus tools menu but that did not seem to fix it. Potentially relevant details: Unity 2020.3.36 MRTK v2.7.2 OpenXR plugin v1.5.3 Oculus XR plugin v1.12.0 Oculus Integration v53.1 Minimum Android API Level: Android 10 (API level 29) OpenXR settings: Render mode: Single Pass Instanced/Multi-view Depth Submission Mode: Depth 16 Bit Interaction Profiles: Oculus Touch Controller Profile OpenXR Feature Groups: Hand Tracking MetaXR Feature Oculus Quest Support I have tried turning off passthrough and saw that the models became stable again but that is not acceptable. I tried updating the AndroidManifest.xml as stated in the linked post but that did not change anything. My code hasn't changed going from the Oculus XR Plugin to the OpenXR Plugin but it can be summed up to just adding the OVRSpatialAnchor component: model.AddComponent<OVRSpatialAnchor>();
Need help figuring out how to enable the OpenXR Runtime "Set Oculus as active" option
I am trying to connect my unity editor to my Meta Quest 2 to rapid run and test out my VR apps. However running into issues with the set up. The "set oculus as active" option on my Oculus desktop app is not enabling or responding. This seems to be a key problem. I am not sure why, here are some videos from my end: 1. Oculus Desktop App / https://youtu.be/c5zleDI-EIg 2. Unity Editor Settings / https://youtu.be/2qB6kau6bdQOpenXR News and Feedback Thread
This thread is to highlight latest developments regarding Oculus and OpenXR! If you're running into any issues with OpenXR and/or have feedback to share, leave it as a comment in this thread! Latest Update 7/23/21: Oculus opens full support for OpenXR, deprecating proprietary APIs! Full Support for OpenXR means that we: Help developers build new applications with OpenXR via our Developer Site Perform QA testing of OpenXR to ensure features are working Address bugs when reported Provide developers API access to new capabilities via OpenXR A year from now (August 31, 2022), Compatibility Support for Oculus Native Mobile and PC APIs will end and they will be Unsupported. Existing applications will continue to function on Oculus devices, but our level of support will change. Read the full details in the following blog: https://developer.oculus.com/blog/oculus-all-in-on-openxr-deprecates-proprietary-apis/ Past Updates 7/23/20: As of v19, we are officially supporting OpenXR 1.0 implementation. Developers can now submit their OpenXR apps to the Oculus Store. For mobile, please use the OpenXR loader that shipped with v19 or higher. You can find the latest PC SDK version here and the latest version of the OpenXR SDK here. Known Issues (will be fixed in future release): Grip pose is misaligned. Action spaces continue to track even when isActive == false, which is conformant but misaligned with other runtimes. This will cause issues if relying on on tracking state vs. isActive for rendering hands. Parent interaction profile bindings are missing for non-natively supported profiles (everything besides the Simple, Touch, and XBox controller profiles). If you have any questions regarding this release, please post them as a reply to this thread!How to handle being a truly OpenXR game with some Oculus OpenXR features?
Hello, I'm building a game for every platform, Steam and Meta, and it works that way so far. I've read Meta documentation, and it seems like I'm supposed to use Meta's "OpenXR" rig for some features like Dynamic Resolution . Currently I'm using the Hurricane VR and Hexa Rig asset combo (VR - Physics Interactions Bundle | Physics | Unity Asset Store) for my player rig. I've attached a screenshot of the camera settings set up as a generic XR device. If I wanted to use some oculus camera features, how would I organize that for my project? Do I need to make two rigs and switch between them depending on the platform??OpenXR error XR_ERROR_SPACE_COMPONENT_NOT_SUPPORTED_FB in build when Mixed Reality scene loaded
Hi, I am getting spammed by the following error after I load my mixed reality scene (room) via the OVRSceneManager.cs [XRCMD][failure] [XR_ERROR_SPACE_COMPONENT_NOT_SUPPORTED_FB]: xrLocateSpace(*(XrSpace*)space, baseSpace, ToXrTime(GetTimeInSeconds()), &spaceLocation), arvr/projects/integrations/OVRPlugin/Src/Util/CompositorOpenXR.cpp:11311 (arvr/projects/integrations/OVRPlugin/Src\Util/CompositorOpenXR.h:318) The mixed Reality room seems to load fine (mostly), and I am able to localize all anchors, but logcat is being spammed by the error. Not sure it's related, but also getting this error often: AnchorManagerHelpers: The tracked root node uuids are different?! 0efe69dd-c03e-a729-a4b2-3108ac493f34 - 00000000-0000-0000-0000-000000000000 Any ideas how to get rid of the error, please? Thank you. Unity 2021.3.25f1, Oculus integration v56.0, OpenXR Plugin 1.7.0, Oculus XR Plugin 3.3.0 Quest 2 and Quest Pro
Pre-Existing Kotlin Android App - Unable to upload without Oculus SDK
Hi, I have an existing android application written in kotlin which I wish to upload to the quest store. I have built and run the application on a headset locally and it all works perfectly. Upon uploading to the store i get the error "* Oculus SDK not found or older than 1.0." The app does not include the Oculus SDK or similar as it is not needed. It does not take advantage of any headset specific features and is just your standard 2d app. Is bundling the sdk in required to upload to the store? If so is there documentation on how to do so with an existing kotlin app as all the documentation is largely around apps containing native code and doesn't provide clear guidance on this use case. I've considered grabbing the OpenXR samples and smashing that together with the existing app. Is this a reasonable approach? It seems over the top especially for an app that won't require the SDK (for now). Thanks, Nathan
