Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.4.X
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.12f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1146244
Regression
No
Sub-State Machine appears in an Animator when inspecting an Animator Controller with less Layers than the previously opened one
Steps to reproduce:
1. Open "SampleScene" from "1146244_AnimatorIssue.zip" project
2. Open Animator window
3. Select Sphere object in the Hierarchy and see that there's no Sub-State Machine in Animator
4. Select Cube in Hierarchy
5. In Animator go to Layers and select "New Layer" layer
6. In Animator go to Parameters
7. Select Sphere object and inspect Animator window
Actual result: "(Up) Base Layer" appears in the Animator, which looks like a Sub-State Machine, but can't be interacted with
Expected result: Nothing new gets created in the Animator
Reproducible with: 2017.4.27f1, 2018.4.0f1, 2019.1.3f1, 2019.2.0b2, 2019.3.0a3
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.9f1