Search Issue Tracker
Fixed in 1.0.0-preview.7
Votes
0
Found in [Package]
preview - 0.1.2, preview.4 - 1.0.0
Issue ID
1218544
Regression
No
Input System package does not re-resolve bindings when adding a new binding to a map that has already generated its state
To reproduce:
1. Open attached project ("case_1218544.zip")
2. Open Assets > Scenes > "SampleScene" scene
3. Press Play, in Game View press 'Run' button and click 'c' keyboard button
4. Observe the Console window
Expected result: Message with "action1 performed" is printed
Actual result: Message with "action1 performed" is not printed
Reproducible in: 2018.4.17f1 (0.1.2, 0.2.1), 2019.3.1f1, 2020.1.0a23 (0.2.10, preview.4 - 1.0.0)
Could not test in: 2017.4.36f1 (No Package Manager)
Could not test in package versions: 0.2.6, 0.2.8 (Due to errors in the project)
Note: Trying to get the bindings for an action (after adding a new binding to a map that has already generated its state) also throws a 'System.ArgumentException: length
' exception.
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/1094