Search Issue Tracker
Fixed
Fixed in 1.4.0
Votes
0
Found in [Package]
1.3.0
Issue ID
ISXB-166
Regression
No
Input from the keyboard is not working when the DualShock 4 controller is connected
Reproduction steps:
1. Connect DualShock 4 controller to the PC
2. Open the SampleScene Scene in the attached project "DS4InputEventRepro.zip"
3. Enter the Play mode
4. Move the left stick on the controller to the left, observe that in the Game View there is an output "Move: (-1.0, 0.0)"
5. Press the A button on the keyboard
6. Observe the Game view
Expected result: Output in the Game view is "Move: (-1.0, 0.0)"
Actual result: Output in the Game vies doesn't change or just flickers for a second
Reproducible with: 2019.4.32f1, 2020.3.22f1, 2021.1.28f1, 2021.2.2f1, 2022.1.0a14
Note:
- Input is not working with S, D, and W buttons
- Issue is not reproducible with Xbox controller
-
Victor_IMISELF
Dec 17, 2023 09:47
This can seemingly still happen on Dualshock 4 controllers even on Input System V. 1.6.3 and Unity version 2022.3.7f1. It seems that the input from the joysticks quickly cancels out any keyboard input that the Dualshock joysticks also handle, such as movement controls. I'll try to report this as an issue if I can find a way to consistently reproduce it.
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
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
- The build size is larger when Models have Animation Type set to Generic
Resolution Note (fix version 1.4.0):
Fixed in: Input system 1.4.1