Search Issue Tracker
Fixed in 5.4.0
Votes
1
Found in
5.3.1f1
Issue ID
756129
Regression
Yes
State machine behavior that has a specific serialization error removes all state machine behaviors
To reproduce:
1. Open attached project
2. Open "testscene" scene
3. Play the scene
4. Press space keyboard button
5. Notice the robot turns red at the end of it's slide animation
6. Build the game for standalone version
7. Press space keyboard button
8. Notice that robot does not turn red at the end of animation
Expected behavior: 5 and 8 steps result should be the same (see gifs below)
Note: when adding a state machine behavior that has a specific serialization error to an animation controller it removes all state machine behaviors when the game is built
Reproducible with: 5.2.4p1, 5.3.1f1, 5.4.0b1
Not reproducible with: 5.1.4p1
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