Search Issue Tracker
Fixed
Fixed in 1.8.0-pre.2
Votes
0
Found in [Package]
1.8.0-pre.2
Issue ID
ISXB-580
Regression
No
UI/Submit action from the DefaultInputActions asset is not recognised when using a Nintendo Switch Pro controller
Reproduction steps:
1. Open the "IN-47604.zip" project
2. Open "Assets/Scenes/SampleScene"
3. Connect a Nintendo Switch Pro controller to your computer via USB
4. Enter Play mode
5. Click on the top left button with your mouse in the Game view
6. Press the A button on the Nintendo Switch Pro controller and observe the Console
Expected result: "t" is printed to the Console
Actual result: Nothing is printed to the Console
Reproducible with: 1.5.1 (2021.3.26f1, 2022.3.0f1, 2023.1.0b19, 2023.2.0a17), 1.6.3 (2021.3.29f1, 2022.3.6f1, 2023.1.6f1, 2023.2.0b2)
Reproducible on: Windows 10, macOS 13.4.1 (M1) (Reported by the user)
Notes:
- Reproducible in Standalone Player
- On macOS, the issue is reproducible when the controller is connected via USB or Bluetooth
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.8.0-pre.2):
Switch Pro controller now has correct usages assigned to the relevant controls.