Search Issue Tracker
Fixed
Fixed in 6000.6.0a5
Fix In Review for 6000.6.0a5
Under Consideration for 6000.0.X, 6000.3.X, 6000.4.X, 6000.5.X
Votes
2
Found in
6000.1.0a1
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
6000.6.0a1
Issue ID
UUM-85319
Regression
No
[Quest] Input.GetButtonUp("XRI_Left_TriggerButton") is false when releasing the Trigger button
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Enter the Play Mode
4. Press the Trigger button on the left controller
5. Observe the Console
Expected result: Message logs “button down“ and “button up” exist
Actual result: Message log “button down“ is present
Reproducible with: 2.5.4 (2022.3.36f1), 3.0.5 (2021.3.45f1, 2022.3.50f1, 6000.1.0a1)
Reproducible on:
Play Mode (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)
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Comments (1)
-
ryekis
Oct 19, 2024 02:09
also same error with the XRI_RIGHT_TRIGGERBUTTON
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
- Package Manager's Filter Panel does not show borders when viewed on Windows
- Package installation fails non-deterministically with Errors "EPERM: operation not permitted" when installing Packages
- Blend Tree Threshold fields accepts NaN/Infinity values causing Node backgrounds disappear in Animator Controller view
- Port keyboard selection sync improvements from legacy UGUI InputField to TMP_InputField
- Animator Controller Layer Weight field accepts “NaN” as a valid value instead of rejecting it
Resolution Note (fix version 6000.6.0a5):
Fixed in 6000.6.0a5