Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.4
2020.3
2021.1
2021.1.15f1
2021.2
2022.1
Issue ID
1354473
Regression
No
State Machine Behaviour reference becomes null when moving State in Animator window
How to reproduce:
1. Open the attached project (TestSMB.zip)
2. Open Scenes/SampleScene
3. Press the Play button
4. Observe the Console
5. Click on OtherObject in the Hierarchy window
6. Observe the SMB field under the Test (Script) component in the Inspector window
7. Double-click on New Animator Controller in the Project Window
8. In the newly opened Animator window, click and drag the New State
9. Observe the Console
10. Click on OtherObject in the Hierarchy window
11. Observe the SMB field under the Test (Script) component in the Inspector window
Expected result: reference to State Machine Behaviour remains the same
Actual result: reference to State Machine Behaviour becomes null
Reproducible with: 2019.4.29f1, 2020.3.15f1, 2021.1.16f1, 2021.2.0b6, 2022.1.0a4
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
After evaluating the impact, workaround and risk associated with fixing this issue, in addition to the current team's bandwidth and priorities, we have concluded that this issue will not be addressed in the foreseeable future. Therefore any edits done to an Animator State Machine graph will invalidate State Machine Behaviors that have previously been referenced. We are closing this issue as Won’t Fix.