Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X
Won't Fix in 2023.3.X
Votes
0
Found in
2020.3.47f1
2021.3.24f1
2022.2.17f1
2023.1.0b14
2023.2.0a12
2023.3.0a3
Issue ID
UUM-34724
Regression
No
DualSense controller mappings are corrupted when using legacy Input Manager
How to reproduce:
1. Open the “DualSense_LegacyInput_Bug“ project
2. Open the “MainScene“
3. Enter Play Mode and observe the Game view
4. Attempt to move around with the left analog stick, and look around with the right analog stick
Expected result: “Player” GameObject can move around and look freely with the use of analog sticks
Actual result: “Player” GameObject can’t fully/partially move and/or look
Reproduced with: 2020.3.47f1, 2021.3.24f1, 2022.2.17f1, 2023.1.0b14, 2023.2.0a12
Reproduced on: Windows 11, MacOS Ventura 13.0 (M1)
Not reproduced on: Linux-Ubuntu-20.04
Notes:
1. Also reproducible in Player
2. From version 2022.2.17f1 and above the “TutorialCallbacks“ script had to be modified to fix scripting errors → added “using Unity.AI.Navigation;”
3. Reproducible when DualSense controller is plugged in via wire (USB-C->USB-A)
4. Reproducible when DualSense controller is connected via Bluetooth
5. On Windows the right analog stick is unresponsive → cannot move the camera
6. On MacOS the right analog stick only allows the camera to move left or right
7. Could not test DualSense controller via Bluetooth on Linux
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
- Trail Renderer visual doesn't match the positions of vertices when they have been offset
- [Mobile] The Material is not visible when using the Decal Renderer Feature
- Uncaught TypeError: Cannot read properties of undefined is thrown when the tab is inactive for several minutes
- Crash on mono_array_length when building a project
- "StackOverflowException" error when changing spline curve type from "Bezier" to "Auto" in the "Element Inspector"
Resolution Note (2023.3.X):
The HID mappings for both PS4 and PS5 controllers do not match the default Axis mappings used by InputManager. This is a known limitation of "old" Input and won't be fixed.
Specifically, PlayStation controllers aren't officially supported on Windows and their HID reports don't match those form "Xbox based gamepads": the Right Stick and R2 Axis are configured differently. An official 3rd party driver like DS4Windows (https://ds4-windows.com/) may be necessary.
It's strongly recommended to migrate to the "new" InputSystem package (https://docs.unity3d.com/Packages/com.unity.inputsystem@1.7/manual/index.html) which does properly support PlayStation gamepads. The package contains various samples to help get started on the new system, but unfortunately many of the other samples (including FPS Sample) still use "old" InputManager.