Search Issue Tracker
Fixed in 1.0.0-preview.7
Votes
0
Found in [Package]
1.0.0-preview.6
Issue ID
1221015
Regression
No
[Input System] Default value of 'expectedControlType' is not being set when creating a new Action
Reproduction steps:
1. Create a new project
2. Install the "Input System" package
3. Create a new InputAsset asset
4. Create a new Action inside the asset
5. Save the asset and open it through a text editor
6. Find the newly created Action and see that it doesn't have an 'expectedControlType' set
7. Go back to Unity, Select Action Type and select 'Button' (same value as it already has)
8. Open the text editor again and inspect that 'expectedControlType' is now set to 'Button'
Expected result: The default 'expectedControlType' is set to Button after creating the asset
Actual result: The default 'expectedControlType' is not set, even though in the Editor it has 'Button' value set by default
Reproducible with: 2019.3.5f1, 2020.1.0b1, 2020.2.0a2
Couldn't test with: 2017.4, 2018.4 (package not supported)
Reproducible with package versions: 0.9.0, 1.0.0-preview.6
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
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
- Scale Snapping with Gizmos does not work in the Scene view when Snapping and Absolute Grid Snapping are toggled off
- Text Script Importer Reference button links to a Missing Page when clicking the Reference Button in the Inspector
- FrameTimingManager.GetLatestTimings adds background time to the next focused frame when the Player is unfocused
- PropertyDrawer gets disposed while still being active when adding a secondary component
Resolution Note (fix version 1.0.0-preview.7):
Fixed by https://github.com/Unity-Technologies/InputSystem/pull/1098