Search Issue Tracker
Third Party Issue
Under Consideration for 1.7.X
Votes
8
Found in [Package]
1.7.0
Issue ID
OXRB-162
Regression
No
[Quest] OpenXR Input does not work when Meta Quest Pro Interaction Profile is selected
Reproduction steps:
1. Open the attached project “ReproProj" with the Android Platform
2. Build And Run on the Quest 2 device
3. Try interacting with controllers and observe the Player
Expected result: The Player detects controller inputs
Actual result: The Player does not detect any controls
Reproducible with: 1.4.4 (2020.3.47f1), 1.5.0 (2020.3.47f1), 1.5.1 (2021.3.22f1, 2022.2.14f1, 2023.1.0b11, 2023.2.0a10)
Reproducible with devices:
VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650
Testing environment: Windows 10 Enterprise 21H2
Notes:
* LogCat is attached
* Removing the Meta Quest Touch Pro Controller Profile from the OpenXR Interaction Profiles resolves the issue
-
swantonb
May 24, 2023 07:47
I'd say "under consideration" is not the right response. This is a pretty important matter, please fix it soon!
-
Fuzzinator
May 24, 2023 03:26
This is completely preventing me from using the OpenXR backend because I dont want to exclude the Quest Pro from support
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
- [Scene View][Ubuntu] Prefab mode UI ghosting in HDRP
- Deleting AudioMixer asset throws MissingReferenceException and breaks the Audio Mixer window
- Crash on ScheduleGenerateTilingShape when modifying PolygonCollider2D path count and setting path vertices
- Crash when a scene is created with LocalPhysicsMode::Physics3D
- [HDRP] Light doesn't bounce off terrains
Resolution Note:
The fix is planned to be included in Oculus Integration Asset v57.0