Search Issue Tracker
Fixed in 1.0.0-preview.7
Votes
0
Found in [Package]
preview.4 - 1.0.0
Issue ID
1219415
Regression
No
Impossible to choose Gamepad as Binding Path when Control Scheme is set as XboxOne_Scheme
Repro steps:
1. Open the attached project "case_1219415-BugRepro_003.zip"
2. In the Project tab, click on Assets > GameInputActions
3. In the Inspector tab, click on 'Edit asset'
4. In the top left of the newly opened window, change 'All Control Scheme' to 'XboxOne_Scheme'
5. In the Actions column, click on <No Binding>
6. In the Properties column, under Binding, open the dropdown menu for Path
Expected results: Usages and Gamepad are shown as possible options
Actual results: only Usages option is shown
Reproducible with: 2019.3.0f1 (Input Systems preview - 0.2.10), 2019.3.0f5 (Input Systems preview.4 - 1.0.0), 2020.1.0a23 (Input Systems preview.4 - 1.0.0)
Could not test with: 2017.4, 2018.4 due to errors
Notes:
-When Control Scheme is set to NintendoSwitch_Scheme and the same steps are taken, Gamepad appears as an option in the dropdown menu
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 1.0.0-preview.7):
Fixed by https://github.com/Unity-Technologies/InputSystem/pull/1093