Search Issue Tracker
Third Party Issue
Votes
0
Found in
2021.3.35f1
2022.3.20f1
2023.2.11f1
2023.3.0b8
Issue ID
UUM-64346
Regression
No
[Quest] Controllers are missing when Meta All-in-One SDK is installed
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Samples/OpenXR Plugin/1.9.1/Controller/ControllerSample.unity” Scene
3. Select Oculus Touch Controller Profile in OpenXR Settings (Edit > Project Settings > OpenXR > Enabled Interaction Profiles)
4. Install Meta XR All-in-One SDK
5. Enter the Play Mode
6. Try using the controllers
Expected result: Controllers are present
Actual result: Controllers do not exist and references to controls are missing
Reproducible with: 2021.3.35f1, 2022.3.20f1, 2023.2.11f1, 2023.3.0b8
Reproducible with devices:
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 OpenXR and Oculus XR
- Reproducible with Windows Standalone Player
- Reproducible with a new project
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Hi,
This issue is fixed starting in com.meta.xr.sdk.core version 63.0.0 and the project is using 60.0.0. If there is a specific reason you need a version 60.0.0, you should reach out to Meta about the issue as we do not have access to the source code in the com.meta.xr.sdk.core package on our end to create a fix for that specific version. Or you could try using an older version of com.unity.xr.openxr
Thank you,
Customer QA Team