Search Issue Tracker
Third Party Issue
Votes
0
Found in
2022.2.19f1
2023.1.0b15
2023.2.0a13
Issue ID
UUM-36494
Regression
No
[Quest 2] [Oculus Integration] Project will result in Oculus controllers not being detectable when MetaXR Feature is enabled with OpenXR
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Connect the Quest 2 device with Oculus Link
4. Enter the Play Mode
5. Move controllers
Expected result: Controllers are detected and are responsive in Play Mode
Actual result: Controllers are not detected
Reproducible with: 2022.2.19f1, 2023.1.0b15, 2023.2.0a13
Could not test with: 2020.3.48f1, 2021.3.25f1 (Assets\Oculus\Interaction\Editor\AutoWiring\UnityObjectAddedBroadcaster.cs(74,50): error CS0117: 'SceneManager' does not contain a definition for 'loadedSceneCount')
Reproducible with devices:
VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650
Reproducible on: Windows 10 Enterprise 21H2
Notes:
- If MetaXR Feature is enabled in Project Settings > OpenXR, the project does not detect Oculus controllers
- To check if controllers are detected or not, you can go to Window > Analysis > Input Debugger
- Reproduced with Oculus Integration SDK v46 and v53. Could not downgrade to v46 or below due to the errors
- See controllers not being detected in Windows > Analysis > Input Debugger window
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note:
The fix is planned to be included in Oculus Integration Asset v57.0