Search Issue Tracker
Fixed
Fixed in 1.11.0-preview.1
Votes
42
Found in [Package]
1.11.0-preview.1
Issue ID
OXRB-279
Regression
Yes
[OpenXR] Height offset is not applied to the Camera when Tracking Origin Mode Floor option is selected after entering Play Mode
Steps to reproduce:
1. Create a new 3D project
2. Import OpenXR 1.9.1
3. Import the attached "CustomPackage.unitypackage"
4. Reload "SampleScene.unity"
5. Connect Quest 2 to Oculus Link
6. Enter Play Mode and in the Hierarchy select the "XR Rig" GameObject
7. In the Scene View, under the Tracking Origin Mode Setting observe how "Floor" option makes the Camera stay at the floor level
Expected results: Height offset is applied to the Camera when Tracking Origin Mode Floor option is selected after entering Play Mode
Actual Results: Height offset is not applied to the Camera when Tracking Origin Mode Floor option is selected after entering Play Mode
Reproducible with: OpenXR 1.9.1 (2021.3.33f1, 2022.3.15f1, 2023.2.2f1, 2023.3.0a18)
Not reproducible with: OpenXR 1.8.2 (2021.3.31f1, 2022.3.12f1, 2023.2.0b16, 2023.3.0a12)
Reproducible on these devices:
VLNQA00609 - Oculus Quest 3 (Quest 3), CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno 740, OS: 12
VLNQA00415 - Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650, OS: 10
Testing Environment: Windows 11
Not reproducible on: No other environment tested
Notes:
-If the Tracking Origin Mode is changed from "Floor" and back to it, issue no longer reproduces
-Issue does not reproduce when using other options besides Floor
-Forum thread: [https://forum.unity.com/threads/update-com-unity-xr-openxr-from-1-8-2-to-1-9-1-changes-tracking-origin.1515263/#post-9474268]
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
rzeeryp2
Mar 26, 2024 10:38
Issue still happening. Need a quick fix or something please.
baggyg
Feb 29, 2024 15:40
Still present on OpenXR 1.10.0 / 2022.3.20f1 Quest 3 (via AirLink)
TwistedSage
Feb 16, 2024 06:30
Issue on multiple headsets here
Aftermorrow
Dec 29, 2023 13:12
Also reproducible on a Rift CV1, Windows 11, floor setting before play mode.