Search Issue Tracker
Won't Fix
Won't Fix in 1.8.X
Votes
0
Found in [Package]
1.8.1
Issue ID
ISXB-814
Regression
No
DualSense controller Rebinding for Composite displays different strings for the same button after pressing any of the trigger buttons
Reproduction steps:
1. Open the attached “ps5 controller bug.zip“ project
2. Connect the DualSense controller
3. Open “RebindingUISampleScene”
4. Enter Play Mode and click the Move binding field in the Gamepad section to rebind the action
5. Click the right trigger on a PS5 controller and observe the Move binding field result
Expected result: “R2/R2” or “rightTriggerButton/rightTriggerButton” is displayed
Actual result: “rightTriggerButton/R2” is displayed
Reproducible with: 1.7.0 (2021.3.36f1), 1.8.1 (2021.3.36f1, 2022.3.22f1, 2023.2.15f1, 6000.0.0b12)
Reproduced on: Windows 11 Pro, macOS Sonoma 14.3.1 (Intel), macOS 14.3.1 (M1) (by reporter)
Notes:
- Also reproducible in Player
- Not reproducible with Xbox and DualShock controllers
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
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.
Resolution Note (1.8.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
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.