Search Issue Tracker
Fixed in 2022.3.8f1
Fixed in 2022.3.X, 2023.1.X, 2023.2.X, 2023.3.X, 2023.3.0a1
Votes
0
Found in
2022.3.4f1
2023.1.2f1
2023.2.0a21
2023.3.0a1
Issue ID
UUM-41684
Regression
Yes
StateMachineBehaviour messages don't fire when used on Animator Controller Override Layers
Steps to reproduce:
1. Open the attached user's project "1593820 StateMachineBehaviour Messages.zip"
2. Open SampleScene
3. Notice the three Cubes with different Animator Controllers setups
4. Notice that some of the Animators States have a StateMachineBehavior on Layer 1
5. Press Play
6. Observe the Console
Expected result: Some of the Messages should state that they are fired from Layer 1
Actual result: Only Messages fired from the Base Layer are triggered
Reproducible on: 2022.1.0a13, 2022.3.4f1, 2023.1.2f1, 2023.2.0a21
Not reproducible on: 2021.3.28f1, 2022.1.0a12
Environment Tested on: Windows 10
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment