Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
5.0.0b10
Issue ID
643048
Regression
No
StateMachineBehaviours do not work if a state inside it has or has had its own StateMachineBehavior
To reproduce this issue:
1. Import the attached package
2. Open 'scene'
3. Select 'GO' object in the hierarchy
4. Open Animator
5. Notice there is a 'StateMachine' with 'SimpleStateMachineBehavior' script
6. Play the scene and notice the output in the console
7. Now open 'StateMachine' in the Animator
8. Select 'NewState' and add 'EmptyStamachineBehavior' on it
9. Play again and no output is seen in the console
10. Remove 'EmptyStamachineBehavior' from 'NewState'
11. The StateMachineBehavior still does not work
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [macOS] Editor window is not restored to previous position when launching the Editor and mouse cursor is on a different screen
- [Usability] Warning message in an Adaptive Probe Volume Component is not informative enough when Realtime Global Illumination is enabled
- Inspector for Adaptive Probe Volumes is not repainted when toggling Realtime Global Illumination setting in the Lighting Window
- Surface Inputs are not rendering when using the custom BaseShaderGUI
- Reflection Problem custom Cubemap loses its reference when HDR is enabled and the platform is switched
Add comment