Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.31f1
2022.3.10f1
2023.1.16f1
2023.2.0b12
2023.3.0a9
Issue ID
UUM-52480
Regression
No
[Android] PS5 Controller buttons doesn't match the mapped buttons in the Player
How to reproduce:
1. Open the "IN_56535" project
2. In the Build Settings "Run Device" dropdown select the desired device
3. Press Build And Run
4. Connect the PS5 controller to the mobile device
5. In the Player press the controller buttons
6. Observe the Player
Expected result: Pressed button on the controller matches the mapped buttons in the Player
Actual result: Pressed button on the controller doesn't match the mapped buttons in the Player
Reproducible with: 2021.3.31f1, 2022.3.10f1, 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:
VLNQA00512, Samsung Galaxy S9 (SM-G960F), Android 10, CPU: Exynos 9 (9810), GPU: Mali-G72
VLNQA00120, Google Pixel 2 (Pixel 2), Android 8.1.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00489, Htc 10 (HTC 10), Android 6.0.1, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
Not reproducible on these devices:
iPad Air 4th Gen (iOS 15.2.1)
Notes:
- Not reproducible with PS4 and Xbox series X controller
- Not reproducible on iOS and Windows Standalone Platform
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
- Animation Clip with Legacy enabled does not play when Time.timeScale is set to 0 despite Update mode set to "Unscaled time"
- Rename is enabled on subfolder empty space - "Can't rename to empty name" warning
- SamplerState Property Missing Anisotropic Filtering
- Visual glitches when using Handles API
- The RGBA color values are inconsistent when comparing two identical colors set in the Inspector
Resolution Note:
There is no official DualSense support for versions earlier than Android 12. For supported devices, the issue goes as deep as device drivers, so unfortunately, it’s not something we can realistically fix on our side. There is a patch available for this issue in later versions of Android.