Quests hands tracking is not working in Unity editor
For some reason hands tracking is not working anymore in Unity editor. Tried with Quest Link and with Air Link. Tried in a clean project with the latest updates and Quest Pro. Tried in some old project for Quest 2 (and with Quest 2) where everything was fine a few month ago. Nothing. Checked with Oculus Integration examples - controller ok, hands are absent in the editor. In latest Unity Movement examples eye & face tracking works, controllers works, but no hands tracking, no head movement mirroring, no hands mirroring even with the controllers in the scene. And of course I tried to reboot everything. No errors in editor, but some warnings appear (only sometimes): I will be grateful for any help. Windows 11 Unity 2021.3.4/2021.3.13 Oculus Integration v46 Oculus XR 3.2.2-pre.1 Oculus app version 46.0.0.230.0 (46.0.0.229.0). I tried latest Oculus app, then switched to test channel - no changes. Quest Pro v46.0.0.226
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?
Performance issue with OVRPlugin using OpenXR backend
Hello, our game is using Unity 2020.3.32f1 and Oculus Integration v39.0.0. We found in profiler that with OpenXR backend, OVRManager takes about 2ms CPU every frame on a Quest 1 device, while it only takes about 0.32ms if we switch back to the legacy OVRPlugin with LibOVR and VRAPI backends. (The profiler data were taken using a new project with only Oculus Integration 39.0 added, and with the sample scene MRC in Oculus/VR/Scenes) With deep profiling on, we found that it is from OVRP_1_16_0.ovrp_GetControllerState4(). We also found that if we remove the battery in 1 or both Oculus Touch controllers, the time drops (with 1 battery removed, it drops to around half and with both removed, it drops to near 0ms, but of course we can no longer play without controllers). As a result of this, we can hardly switch to the OpenXR backend due to the FPS requirement in Quest 1. Anyone knows if I am missing something or is it a problem with the plugin itself? Thank you.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 and Meta XR SDK at the same time
When I install OpenXR Plugin alongside Meta XR All-in-One SDK I get this warning in Project Validation to use Oculus XR Plug-in instead of OpenXR. What is the recommended/correct approach to achieve cross-platform compatibility with OpenXR while using Meta XR SDKs in that case? Or should I ignore this warning?
