Search Issue Tracker
Active
Under Consideration for 2022.3.X, 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
0
Found in
2022.3.65f1
6000.0.54f1
6000.2.0f1
6000.3.0a4
6000.4.0a1
Issue ID
UUM-113490
Regression
No
[XR] Input is not recognized with multiple Meta Profiles After Device Standby/Resume When "Development Build" is Enabled
Steps to reproduce:
1. Open the attached project "XRInputTest.zip"
2. Switch to Android
3. Open "Assets/SampleScene.unity"
4. Make sure Development build is enabled in the Build Settings
5. Make sure the headset has atleast 2 profiles so that the Profile Switch UI appears after the application is built
6. Once the application launches, confirm that the Scene is rendered
7. Open the Meta menu by pressing the home button on the controller
8. Press the power button on the headset and wait several seconds
9. Wake the headset up and observe the Profile Switch UI appearing and no input is registered
Expected result: input is registered after waking up the headset
Actual result: input is no longer registered after waking up the headset
Reproducible with: 2022.3.65f1, 6000.0.54f1, 6000.2.0f1, 6000.3.0a4
Reproducible with these devices:
VLNQA00644 - Oculus Quest 3S (Quest 3S), CPU: Google Tensor G2, GPU: Adreno 740, OS: 14
VLNQA00609 - Oculus Quest 3 (Quest 3), CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno 740, OS: 12
Environment tested: Windows 11 24H2
Notes:
-Issue only reproducible when multiple Meta Profiles are on the HMD
-Issue only reproducible with Development Build enabled
-Issue reproducible with both OpenXR and OculusXR plugins
-On Quest 2 the profile switch UI doesn't appear after following the steps
-Headset firmware version tested with: 76.1024
-Reproducible with Input Handling: New, Old and Both
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment