Search Issue Tracker
Fixed in 0.3.1
Votes
0
Found in [Package]
0.2.10
Issue ID
1165496
Regression
Yes
[Input System] NullReferenceException when adding Bindings/1D Axis Composites/2D Vector Composites to specific devices
How to reproduce:
1. Open user-submitted project (New Unity Project (14))
2. Open 'New Controls' control settings
3. Select 'New Control Scheme 1'
4. Select 'Keyboard' device
5. Attempt to add a Binding/1D Axis Composite/2D Vector Composite to New action
Expected result: a Binding/1D Axis Composite/2D Vector Composite is added
Actual result: a NullReferenceException is thrown
Reproducible with Unity versions: 2019.1.8f1, 2019.2.0b7, 2019.3.0a7
Could not test with Unity versions: 2017.4.29f1, 2018.4.3f1(regressed package version incompatible)
Reproducible with package versions: 0.2.8, 0.2.10
Not reproducible with package versions: 0.2.1
Could not test with package versions: 0.2.6(Adding actions which are required for bindings results in another NullReferenceException)
Notes:
Does not reproduce when adding bindings to all devices
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment