Search Issue Tracker
Active
Under Consideration for 1.10.X, 2021.3.X, 2022.3.X, 6000.0.X
Votes
7
Found in [Package]
1.10.0
Issue ID
ISXB-1031
Regression
No
[Android] Gamepad input gets stuck if both the D-Pad and South button is pressed at the same time
How to reproduce:
1. Open the "IN_56015" project
2. In the Build Settings "Run Device" dropdown, select the desired device
3. Press Build And Run
4. Connect the Gamepad to the device
5. In the Player on the Gamepad press the D-Pad (left or right buttons) and at the same time press the South button
Expected result: Cube moves as long as the D-Pad is pressed and stops once released
Actual result: D-Pad gets stuck and cubes move after the D-Pad and South button are released
Reproducible with: 2021.3.31f1, 2022.3.10f1 (user reported)
Not reproducible with: 2023.1.16f1, 2023.2.0b12, 2023.3.0a9
Reproducible on: Windows 10 Pro
Not reproducible on: no other environment tested
Reproducible on these devices:
VLNQA00120, Google Pixel 2 (Pixel 2), Android 8.1.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00512, Samsung Galaxy S9 (SM-G960F), Android 10, CPU: Exynos 9 (9810), GPU: Mali-G72
VLNQA00489, Htc 10 (HTC 10), Android 6.0.1, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
VLNQA00178, Xiaomi Redmi Note 4 (Redmi Note 4), Android 6.0, CPU: MediaTek Helio X20 MT6797M, GPU: Mali-T880
Not reproducible on these devices:
VLNQA00494 - iPhone 14 Pro Max, 16.3.1 iOS
VLNQA00358 - iPhone 12, 14.1 iOS
VLNQA00392 - iPad (9th generation), 15.0 iOS
VLNQA00310 - iPad Pro 12.9", 13.4.1 iOS
Notes:
- Couldn't reproduce on 2022.3.10f1 (cube sometimes not moving at all which could be related to the issue)
- Didn't search for a fixed version because I'm not able to reproduce the issue on the user-mentioned 2022.3.10f1 version which could lead to an incorrect fixed version
- Not reproducible on the iOS and the Windows Standalone Player
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
Add comment