Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.2.X, 2017.3.X
Votes
3
Found in
5.6.2f1
Issue ID
966082
Regression
Yes
Animator.GetBehaviours returns empty array after a scene has been saved
To reproduce:
1. Open attached Unity project "GetBehaviours.zip"
2. Open "MyScene" scene
3. Click on "GameObject"
4. Inspect States (there should be names of all the states in the GameObject's Animator)
5. Click "Modify scene and save" button (it makes scene dirty and saves it through code) or do a change and save manually
Result: Upon saving the scene, Animator.GetBehaviours (MyScriptEditor.cs) does not return any states to the array (names list of States is empty)
Workaround: Clicking on "Reload scripts" or manually reloading the scripts fixes the bug
Reproduced on: 5.6.0f1, 5.6.4p1, 2017.1.2p2, 2017.2.0p1, 2017.3.0b8, 2018.1.0a3
Not reproduced on: 5.5.4p2, 5.6.0b9
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Add comment