Search Issue Tracker
Fixed in 1.4.3
Found in [Package]
InputAction fields are not labeled correctly when they are inside of a Serialized non-MonoBehaviour class
1. Open the attached project
2. Select the "GameObject" GameObject in the Hierarchy window
3. Observe the Input Action field label under the "MB Class (Script)" component's "Class With Broken Name" field
Expected result: the Input Action is labeled according to its variable name
Actual result: the Input Action is labeled as "Input Action"
Reproducible with: 1.1.0-pre.5, 1.1.1, 1.2.0, 1.3.0 (2019.4.38f1, 2020.3.34f1, 2021.3.2f1, 2022.1.0f1, 2022.2.0a13)
Not reproducible with: 1.1.0-preview.3 (2019.4.38f1, 2020.3.34f1, 2021.3.2f1, 2022.1.0f1, 2022.2.0a13)
Note: using the Input System package version 1.3.0, the Serialized InputAction field, which is inside a class, which inherits the MonoBehaviour class, is labeled correctly, however, if the Serialized InputAction field is inside a Serialized non-MonoBehaviour class, it isn't
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- Standard Unity Materials and Shaders become corrupted after importing specific Asset Packages
- [Linux][OpenGL][Vulkan] Draw calls are not shown in the Event List when taking a capture of a frame with RenderDoc
- Inaccurate collision detections when Rigidbody Collision Detection is set to "Continuous" or "Continuous Dynamic"
- Crash on Object::IncrementPersistentDirtyIndex when upgrading project version
- [iOS] Multiple Xcode project instances created before opens up when performing Build and Run for iOS Platform