Search Issue Tracker

Active

Under Consideration for 3.3.X, 4.5.X

Votes

0

Found in [Package]

3.3.0

4.5.0

Issue ID

OXPB-173

Regression

No

[Quest3][OculusXR] Current Tracking State is set to None on TrackedPoseDriver when using OculusXR plugin with Quest 3

Package: Oculus XR Plugin

-

Steps to reproduce:
1. Open the attached user's project "Hello VR.zip"
2. Connect Meta link to Quest 3
3. Open Input Debugger (Window -> Analysis -> Input Debugger)
4. Enter Play Mode
5. Double click the MetaQuest3 device and scroll to the bottom to observe the trackedState value

Expected Results: trackedState value is not 0
Actual Results: trackedState value is reported as 0 and Current Tracking State sets to None in the TrackedPoseDriver upon entering Play Mode with OculusXR and Quest 3

Reproducible with: OculusXR 3.3.0 - 4.5.1 (2021.3.50f1, 2022.3.61f1, 6000.0.46f1, 6000.1.0b14, 6000.2.0a8)

Reproducible with these devices:
VLNQA00609 - Oculus Quest 3 (Quest 3), CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno 740, OS: 12

Not reproducible with these devices:
VLNQA00417 - Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650, OS: 10

Environment tested: Windows 11 24H2

Notes:
-Issue reproduces with a new project, just by installing OculusXR Plugin and entering Play Mode with Meta Link connected, Input Debugger will show that TrackedState defaults to None
-Issue does not reproduce with OpenXR Plugin
-Discussion thread with more information: [https://discussions.unity.com/t/unity-xr-tracking-state-bug-with-meta-quest-3/1614027]

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.