Search Issue Tracker
Fixed
Votes
0
Found in
6000.0.11f1
Issue ID
UUM-76490
Regression
Yes
[Quest 2] Can't look around and hands are not tracked when in Play Mode
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Enter the Play Mode
4. Move your head and try using hand-tracking
Expected result: Can look around the Scene and hands are tracked
Actual result: Can’t look around the Scene and hands are not tracked
Reproducible with: 6000.0.0b16, 6000.0.11f1
Not reproducible with: 2021.3.40f1, 2022.3.38f1, 6000.0.0b15
Reproducible on:
Play Mode (VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650)
Not reproducible on:
Windows Standalone Player (VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650)
Android Player (VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650)
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Notes:
- Reproducible with Oculus XR, but does not reproduce with OpenXR
- A workaround to switch head tracking back on involves adding a tracked pose driver to CenterEyeAnchor
- A workaround to turn hand tracking back on involves replacing the OculusXR plugin with the OpenXR plugin, adding the Oculus Touch Pro profile, and turning on hand poses
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-71393