Search Issue Tracker

Won't Fix

Won't Fix in 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

Package: Input System

-

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

  1. Resolution Note:

    Thank you for reporting a bug to Unity.

    The bug came from the use of the same InputActionAsset accross project-wide input action and PlayerInput component. This workflow is discouraged in latest version of the package.
    Moreover, this particular issue could not be reproduced on latest package version (1.17+)

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

  2. Resolution Note (1.11.X):

    Thank you for reporting a bug to Unity.

    The bug came from the use of the same InputActionAsset accross project-wide input action and PlayerInput component. This workflow is discouraged in latest version of the package.
    Moreover, this particular issue could not be reproduced on latest package version (1.17+)

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

Comments (1)

  1. Bovine

    Oct 18, 2024 17:01

    This is pretty terminal for quest atm

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.