Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.7.0
1.8.0-pre.2
Issue ID
ISXB-725
Regression
No
RebindingUISampleScene “Waiting for Button input…” window doesn't disappear when X button is pressed on the PlayStation controller
Reproduction steps:
1. Open the attached “InputSystemSample.zip“ project
2. Connect the PlayStation controller
3. Enter Play mode and select "Interact" binding for the gamepad
4. Press the X button on the gamepad and observe the Game window
Expected result: “Waiting for Button input…” window disappears after pressing the button once
Actual result: “Waiting for Button input…” window does not disappear or appears again after pressing the button once
Reproducible with: 1.7.0 (2023.2.4f1), 1.8.0-pre.2 (2021.3.34f1, 2022.3.17f1, 2023.2.4f1, 2023.3.0b1)
Reproduced on: Windows 11 Pro, DualShock and DualSense controllers
Not reproduced on: Xbox One controller
Note: To remove the “Waiting for Button input…” window X button needs to be pressed twice
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
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
- Scene view has Y coordinates of the Screen Position node flipped when some of the URP features are disabled
- Volumetric fog shader variants are missing from build when "Strict Shader Variant Matching" is disabled
- Unnecessary modifications clutter the Scene when using a RectTransform driven by a LayoutGroup in a Prefab
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.
Note that the X button is also retriggering the UX in this particular sample. This can be worked around by disabling the UI action map. We will look to improve the sample in the future.
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.