Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2020.3.45f1
2021.3.21f1
2022.2.12f1
2023.1.0b8
2023.2.0a7
Issue ID
UUM-31826
Regression
No
[Input Manager] "Joystick is connected" is logged into the Console when connecting a gamepad
How to reproduce:
1. Create a new Unity project
2. Connect a gamepad
3. Observe the Console
Expected result: “Gamepad is connected” is logged into the Console
Actual result: “Joystick is connected” is logged into the Console
Reproducible with: 2020.3.45f1, 2021.3.21f1, 2022.2.12f1, 2023.1.0b8, 2023.2.0a7
Reproducible on: Windows 11 Pro with Dualsense, Switch Pro, and Dualshock 4 controllers
Note: Also reproducible in the Player
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
- “InvalidOperationException” errors are thrown when entering Play Mode in the Timeline’s Customization Samples
- EditorSceneManager.SaveOpenScenes returns true when the Scene is not successfully saved
- ScrollView snaps back to the target after ScrollTo() when the UI updates every frame
- Dlig ligatures are applied by default when "liga" Font Feature is enabled
- Colliders are rendered deformed when viewed through Physics Debugger in Scene View
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
Resolution Note (2023.2.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.