OVRManager.display returning null
Problem: I'm trying to set my Quest 2 headset to 120hz, Calling OVRManager.display returns null Details: I imported the Oculus Integration Plugin then wrote the below code, but when I build and deploy to the headset I get a null reference exception because OVRManager.display returns nulls Additional Info: Unity 2021.3.12f1, building for the Quest 2, I have Quest support disabled. Oculus XR Plugin V3.0.2 XR Plugin Management V4.2.1 Oculus Integration V49.0 BNG VR Interaction Framework 1.82 Thanks in advance for any help!
Can't Get OVRSceneManager to Work
Hi, I'm developing a VR app, that will now have MR scenes available. I added the OVRSceneManager to my scene, assigned the plane and volume prefabs, scanned my room, yet no meshing or prefabs are instantiated in my scene. And with verbose logging I am getting this message: "Loading the Scene definition yielded no result. Typically, this means the user has not captured the room they are in yet. Alternatively, an internal error may be preventing this app from accessing scene. Invoking NoSceneModelToLoad." Even though I did scan my room successfully. All the documentation I am reading is outdated, and under my OVRManager component, I have Anchor Support enabled. I see Meta's documentation online saying you need to enable Scene Support in the dropdown, but I don't see it appear in my Quest Features.... How can I get my scene model to load and mesh correctly? Thank you!
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.
[Unity/Rift S] Unchecking "Use Position Tracking" in OVR Manager leads to weird distortions in HMD
Using: - Unity 2018.4.2 - Oculus Integration 1.38 - Rift S Test Environment: - Clean, new project, only Oculus Integration inside and a test scene with default cubes - Tested on two different machines with two different Rift S headsets Problem: When I disable "Use Position Tracking" in the OVRManager of the default OVRCameraRig, the image inside the HMD gets super distorted. The image in editor is displayed correctly however. What I would expect from this checkbox is to simply disable 6-DoF positonal tracking and switch to 3-DoF instead. So there seems to be a bug of some kind. Does anyone know about this one or can provide a workaround for dynamically switching between 6- and 3-DoF on runtime? Best, Adrian
