Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2019.4
2020.1
2020.1.0a7
2020.2
Issue ID
1256104
Regression
No
Animator Controller asset can contain orphaned data which cannot be removed in the Editor without tweaking the file externally
How to reproduce:
1. Open user-submitted project (805665.zip)
2. Select the '[BUG] Anim Controller has orphan State that references the AnimationClip' controller
3. Note that it only contains 'Any State', 'Entry' and 'Exit' states and a 'New State'
4. Open this file externally via a text editor
5. Note that the controller also contains another state - 'New State Orphan'
Expected result: 'New State Orphan' can be found in the Animator window
Actual result: 'New State Open' does not appear in the Animator window
Reproducible with: 2018.4.23f1, 2019.4.1f1, 2020.1.0b13, 2020.2.0a15
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note:
Malformed data, with no repro on how to get in this state. Unless we have a clear repro steps to get into that state, we won't fix this.
Possible solution is for user to write script to cleanup orphaned asset.