VR in moving vehicle Rendering issue
I am working on a project which involves using meta quest 3 in Rift mode while inside a moving vehicle. We are attempting to display lidar information as a customer demo and visualization tool. We have run into the usual suspects while doing this (e.g. motion of vehicle is seen as player movement.) In an attempt to temporarily solve for these issues we have disable the safety boundary and limited tracking to just rotation. This handles most of the issues at least for a temporary internal demo. The issue I'm here for is that with this setup if we move/drive more than roughly 100 ft the rendering in the headset for lack of a better word breaks. The simulation/Unity is still running fine but the visual information is torn and frozen. If in this situation we stop the vehicle and recenter the view the rendering returns to normal and we can move another 100ft before it happens again. Has anyone had this result in another other situations? Is the distance thing a floating point issue? What can we do other than recent the view every few seconds automatically. This is not a solution we want to use. FYI. We are going to eventually attempt to use the IMU data of the vehicle and blend that data with the headset tracking but we are not their just yet and want to show something in the mean time.
Camera motion in passthrough
Hi! I am working on developing an app that rotates or translates the field of view during passthrough at different rates. I was wondering if there was a way to have the cameras on the Meta Quest 2, 3, or Pro track a virtual object that moves back and forth? I want the cameras to move back and forth independent from the user's head motion. I can clip some peripheral vision to make this possible as well. Does anybody have a recommendation on how to do this or think it is even possible with the current plugins? Thanks!
Position of OVRCameraRig
I am just starting out on the MQP and Unity development. I removed the camera, and put in an OVRCameraRig. Set up everything for passthru (not that it matters). In my scene, I have a planet about 0.5 meters deep in Z. I fire up Unity and as I move my head around, with the MQP on it, the planet stays in front of the camera. I would expect it to "stay where it was" and I would be able to "walk around it" and look at it from all angles. Nope. Is this expected behavior? I have OVRCR "tracking origin type" set to EyeLevel, and "use position tracking" set to checked. Is there something else I'm missing? It's as if it's not tracking position, and all it's getting is IMU updates. thanks.
Colliders and Positional Tracking on Oculus Quest.
Hello, I'm doing the porting on Quest (from an Oculus Go project). My game is based on free locomotion (a sort of walking inside a labyrinth). So my player is surrounded by ‘wall’ colliders. Now, there was no problem with the Oculus Go, because it was 3DOF, but with the Quest, if I move myself inside the user play area (using my own feet and not through the controller) , the consequence is that the player moves through walls… :( Is there a way to disable just the positional tracking in Unity? Thanks a lot! Valerio
[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, AdrianDisable the IR-leds for the constellation tracking system?
We are developing a serious simulation solution. We are using third party trackers to be able to track the HMD over a much larger space than the oculus constellation tracking system allows. This third party system is using IR-markers as well, hence we need to disable the built in IR-leds in the Oculus Rift HMD to aviod them interfering with the third party tracking cameras. Previously this could be done by simply disconnecting the Oculus Constellation sensors/cameras. As soon as you did that the IR-leds inside the Rift stopped flashing. But with the recent updates from Oculus, this is no longer allowed. If you try to disconnect/disabled the sensors the Oculus application just gives you a warning saying. "Critical Error - We can't find your sensor. Please connect your sensor" Disabling the positional tracking via the Oculus SDK won't stop the IR-leds from flashing either. It would be nice if there where a simple way of disabling the built in IR-leds from the SDK. The best way would be if the IR-leds stopped flashing as soon as you disabled the positional tracking from the SDK. Right now our very ugly workaround is to tape over every LED of the Rift with thick black duct tape.
