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
- ACES Tonemapping causes banding artifacts and negative values in ColorGradingLUT when HDR is enabled and "High Dynamic Range" Grading mode is selected while Android Platform is used
- Android Player freezes when an Audio Source is playing and an incoming call is picked up and then hung up and the Audio Source is started again
- Green success icon is poorly visible in the light Unity theme
- Incorrect input into the Input Field when using Microsoft IME Japanese
- Multiplayer role "ClientAndServer" is displayed without the spaces in the "Play Mode Scenarios" window
Add comment