Search Issue Tracker
Fixed in 1.1-preview.4
Votes
0
Found in [Package]
0.9.0-preview
Issue ID
1291334
Regression
Yes
Input Action Binding doesn't show up in the Inspector when set without name in a Script
How to reproduce:
1. Open the attached "1291334" project
2. Open the SampleScene
3. Attach the "script" Script to the GameObject via Inspector
4. Observe the Script component of the GameObject in the Inspector
Expected result: IgnitionKey has its binding set as "Button North [Gamepad]"
Actual result: IgnitionKey binding is blank
Reproducible with: 0.9.0-preview (2019.4.14f1), 1.0.0 (2019.4.14f1), 1.1.0-preview.2 (2019.4.14f1, 2020.1.13f1, 2020.2.0b11, 2021.1.0a5)
Not reproducible with: 0.2.1-preview (2018.4.28f1)
Could not test with: 0.2.6, 0.2.8, 0.2.10 (2019.4.14f1) package throws compile errors
Note:
-If testing on 0.2.1-preview (2018.4.28f1), the "using UnityEngine.InputSystem" needs to be changed to "using UnityEngine.Experimental.Input" in the Script
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
- "Assertion failed on expression" exceptions are thrown when using IJobParallelForTransformExtensions.RunReadOnly
- [WebGL] Blit with Custom Shader is not rendered in Player
- Error “TypeError: Cannot read properties of undefined (reading ’getSupportedExtensions')" is thrown and WebGL builds do not run on ChromeOS devices when using WebGL 1.0 Graphics API
- [HDRP] SUCCEEDED(hr) error is thrown when the project's Shadows Filtering Quality is set to High or Very High
- With specific Windows 10 settings, the player window resolution does not match the values passed into Screen.SetResolution()
Resolution Note (fix version 1.1-preview.4):
Fixed in Input System 1.1-preview.4