Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.8.0-pre.2
Issue ID
ISXB-759
Regression
No
Input device is not switching to Mouse and Keyboard when Dualshock 4 is connected
How to reproduce:
1. Open the user-attached project “InputSystem_Controller_Noisy”
2. Open the “Entry” scene
3. Connect the Dualshock 4 controller and enter the Play mode
4. Move the Mouse and observe the Console
Expected result: The active device is switched to the Mouse input
Actual result: The device is switching to the Mouse for the one frame and switches back to the Dualshock 4 even though it is not moving
Reproducible with: 1.7.0 (2021.3.34f1, 2022.3.18f1, 2023.2.4f1), 1.8.0-pre.2 (2021.3.34f1, 2022.3.18f1, 2023.2.4f1, 2023.3.0b3)
Reproducible on: Windows 11 Pro
Not reproducible on: No other environment tested
Notes:
-Not reproducible with Xbox One controller
-Dualshock 4 appears to be noisy device
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
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.
This is to do with the noisy gyroscope on the Dualshock 4 controller causing it to be the active device. We would recommend a more manual switching approach.
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.