Search Issue Tracker
Fixed in 1.4.1
Votes
12
Found in [Package]
1.1.0-preview.2
Issue ID
1281633
Regression
No
[Input System] DualShock4 Controller returns random Input values when connected via Bluetooth while Steam is Running
How to reproduce:
1. Open the user attached project
2. Connect a DualShock 4 controller via a Bluetooth
3. Launch Steam
4. Click Window -> Analysis -> Input Debugger
5. Select the DS4 controller
6. Inspect the Input values reported. (Right trigger R2 in particular)
***IMPORTANT
The "Playstation Configuration Support" option under Controller Settings must be checked to repro the issue.
Expected results: The reported input value is 0 if the trigger is not pressed
Actual results: The reported values are random and keep changing all the time
Reproducible with: 1.0.0, 1.1.0-preview.2(2019.4.18f1, 2020.2.2f1, 2021.1.0b1, 2021.2.0a1)
Could not test with: 2018.4(Input system is not available)
Workaround: Quit Steam and re-start the controller
Notes:
1. Does not reproduce if the controller is connected via USB
-
Mirvini
Feb 26, 2022 01:37
It's a bit shocking that this still hasn't been fixed, not simply because the Dualshock controller is so widely used, but because according to this link, the cause of the bug has already been found along with the solution and a member of the steam dev team contacted unity
https://steamcommunity.com/groups/SteamClientBeta/discussions/0/4658391921146080253/It appears steam, and other apps, enable extended HID reporting from the controller. And for some reason the new input system does not handle these correctly.
-
HenryCGS
Jan 22, 2022 19:26
Still confirmed in 2020.3 LTS, package version 1.0.2. This is insane!! The DS4 is one of the most used controllers on PC, this bug is unacceptable!
-
ReneSchleese
Jan 04, 2022 23:01
Having the same problem with Unity 2021.1.23f1
PS4 controller via Bluetooth and Steam controller support disabled
* Gamepad Tester input correct
* Unity input correctPS4 controller via Bluetooth and Steam controller support enabled
* Gamepad Tester input correct
* Unity input faultyThis sort of proves that there is a way of getting correct PS4 Bluetooth input data, even with active "Steam input hack".
-
jackv471
Dec 30, 2021 00:19
This issue definitely isn't solved, I have been having the ds4 buggy Bluetooth inputs for well over a year and I cant find a solution, the proof that gamepad-tester.com has the same problem isn't even correct, my ds4 works fine on that website but unity still goes crazy.
If anybody finds a solution to this problem please let me know, this is driving me crazy -
BillyWM
Nov 27, 2021 04:36
This explanation doesn't seem credible.
I've done clean restarts where Steam / "Steam Client Service" is never allowed to launch in the background and get the exact same results. Also, when I do run steam and close it down it makes no difference (contrary to OP's "workaround" note). What, exactly, has Steam installed and where, to make this happen? I've checked over my Services in Windows settings and don't see anything else.
-
zackblack
Jun 11, 2021 16:48
So does this mean that every Unity built game on Steam just doesn't work with wireless PS4 controllers? I don't see how that's possible. What does Valve have to say about this?
-
zackblack
May 04, 2021 16:14
Having this same issue in 2020.3.0f1 and Input System 1.0.2. No Update after 8 months?? PLEASE!
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 1.4.1):
Fixed in Input System package version 1.4.1 which is available in Unity 2019.4 and above
PR for the fix - https://github.com/Unity-Technologies/InputSystem/pull/1513