Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2019.3.0a1
2020.1
Issue ID
1213291
Regression
No
Override Controllers are missing their state-to-clip mapping when imported via a custom package.
How to reproduce:
1. Create a new project
2. Import attached "walkers02 (1).unitypackage"
3. Navigate to "/Assets/Low Poly Animated People/- Animator Controllers/Controller Overide 1.overrideController"
4. Check the inspector
Expected: the Override Controller shows the states from Base Controller
Actual: the Override Controller shows NO state-to-clip mapping ("List is Empty")
Reproduced versions: 2019.3.2f1, 2020.1.0a23
Regressed in 2019.3.0a1
Not reproduced versions: 2017.4.36f1, 2018.4.17f1, 2019.2.21f1
Note: Only reproduced on a MacOS
Workaround:
Unlink and then relink any state's "motion" clip. Notice the Override Controller's state-to-clip mapping is back.
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
- Player build freezes after calling Application.Quit() when the scripting backend is set to IL2CPP
- Texture is not applied on a Custom Render Texture when a Cubemap is selected as the texture
- 2D light leaks through ShadowCaster2D when ShadowCaster2D components are disabled then re enabled at runtime in Player builds
- Unity Hub redirects to The Unity Roadmap when navigating to “Send Feedback” option
- UI Toolkit throws warning and fails to clear references when fields are not typed as UnityEngine.Object
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0b1