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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment