Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
5.6.0f3
Issue ID
913301
Regression
Yes
Animator.GetBehaviour cannot find the specified StateMachineBehaviour after recompiling the code while in Play mode
To reproduce:
1. Open the project, attached by tester (compileAtRuntime.zip)
2. Open "test" scene
3. Enter Play mode
4. Observe the console (StateMachineBehaviour is FOUND)
5. Edit CapsuleMind script without exiting the Play mode
6. Return to Unity
7. Observe the console (StateMachineBehaviour is NOT FOUND)
Expected: StateMachineBehaviour is found after recompiling the code in Play mode
Actual: script recompilation at runtime causes Animator.GetBehaviour to not find the specified StateMachineBehaviour
Reproduced in 5.6.0b11, 5.6.0f3, 2017.1.0b6, 2017.2.0a1
Did not reproduce in 5.5.3p2, 5.6.0a1, 5.6.0b6, 5.6.0b9, 5.6.0b10
Regression introduced in 5.6.0b11
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Lack of documentation regarding VFX Ray Tracing support
- Shader properties do not appear on the GameObject when switching ShaderGraphs during runtime in the Player
- Multiple '-' symbols are allowed to appear in a row when inputting '.' into a non-decimal numeric field
- Rendering Debugger throws a warning and renders the Scene view in solid black when material debug tools and Path Tracing are used
- User gets "NullReferenceException: Object reference not set to an instance of an object" error in the Console during the search in the "Select Scene" window
Add comment