Search Issue Tracker
By Design
Votes
0
Found in
5.0.0a16
Issue ID
619970
Regression
No
Adding a new script to a state in a Mecanim Animator state machine has issues
Adding a new or multiple behaviour to a state has issues
1) If you create and add a new behaviour to a state, it takes a moment for the script to be added to the list, and then once it appears on the list, the behaviour is missing the disable/enable check.
Adding an existing behaviour script doesn't cause that issue
The script has to be recompiled in playmode to get that check visible again.
2) Using the object selector to change the script for the existing behaviour, causes the behaviour to disappear form the list.
You need to add another behaviour in order for the change of the script to be registered.
Expected: It's possible to add/edit the scripts without them disappearing, the disable/enable check mark should always be visible.
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
Add comment