Search Issue Tracker
Fixed
Fixed in 1.4.3
Votes
0
Found in [Package]
1.1.0-pre.5
Issue ID
ISXB-124
Regression
Yes
InputAction fields are not labeled correctly when they are inside of a Serialized non-MonoBehaviour class
Reproduction steps:
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
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
- Previous model to world matrix is not correctly set for ASW
- More calls are made to GC.Alloc in an HDRP Sample Template when compared to the 2022.3 stream
- Generating Light Probe lighting returns inconsistent results on a specific mesh
- Two Warnings appear for every Soft Delete Operation when Deleting Sub Assets in the Project Browser
- “Item m_LightProbeSystem not found” warning is thrown when pressing the “Open” button multiple times in the Adaptive Probe Volume component warning
Resolution Note (fix version 1.4.3):
InputAction fields are now displayed correctly when serialized inside of a serialized non-MonoBehavior class.