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
- Shadows flickering when a Mesh's Cast Shadows are set to Shadows Only and Camera is moving with Spotlight
- AudioMixer exposed parameters cause assertions when hidden and prevent the drop-down from functioning
- Package Manager/My Assets: 401 Response code trying to download a paid asset store package
- TrailRenderer.SetPosition will log a Index out of bounds error when index is in bounds of the positionCount property
- [URP] Graphics.DrawMeshInstancedIndirect rendering correctly after clicking an another application/refreshing Assets
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.9f1