Search Issue Tracker
Active
Under Consideration for 1.11.X
Votes
1
Found in [Package]
1.11.1
Issue ID
ISXB-1137
Regression
No
[Quest] Controller sometimes does not get recognized or controls do not get registered when using the Player Input Component
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Build and Run on Quest
4. Use the thumbstick of the left controller and the B button on the right controller and observe the box
Expected result: Box moves on the X and Z axes when using the left controller’s thumbstick and jumps up on the Y axis when using the B button on the right controller
Actual result: Box does not move
Reproducible with: 1.8.0 (2021.3.45f1), 1.11.1 (2021.3.45f1, 2022.3.50f1, 6000.1.0a1)
Reproducible on:
Quest 3 (user reported)
Android Player (VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650)
Windows Standalone Player (VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650)
Not reproducible on:
Play Mode (VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650) (the cube sometimes moves very slowly when using the left controller’s thumbstick)
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Notes:
- Does not reproduce after removing the Player Input Component
- If the Controller is not active before opening Player it might not get detected
- Controller might not get recognized depending on whether the controller was active when the app started or whether the auto-switch works
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Bovine
Oct 18, 2024 17:01
This is pretty terminal for quest atm