Search Issue Tracker
Fixed in 1.0.1
Votes
0
Found in [Package]
1.0.0
Issue ID
1254150
Regression
No
Input System "supported devices" results in empty control picker
Repro:
1. Open attached InputSystemSupportedDevices project.
2. Open Edit >> Project Settings >> Input System Package settings.
3. Verify that "Supported Devices" is a list comprising "Keyboard"
4. Open Assets/SampleInputActions.inputactioins
5. Select the <No Binding> binding of New Map >> New Action.
6. Click the "Path" dropdown
Expected result: given the action type is "Button", all the keyboard keys (which are buttons) should show up in the picker.
Actual result: Observe that only "Usages" and no keys are listed.
Verified in: 2020.1b1
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
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (fix version 1.0.1):
Fixed by https://github.com/Unity-Technologies/InputSystem/pull/1163