Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.4
2020.3
2021.1
2021.2
2021.2.0a18
Issue ID
1336288
Regression
No
A model with AnimationType - Legacy and ImportAnimation - false still generates an AnimationComponent on the Root GameObject
Reproduction steps:
1. Open attached project "AnimationReferences.zip"
2. Select "Ball@jump" in the Project view
3. In the "Animation" Tab uncheck "Import Animation"
4. Click "Apply"
5. Select "Model" tab
Expected result: Animation component is not there
Actual result: Animation component is there
Reproducible with: 2018.4.35f1, 2019.4.27f1, 2020.3.9f1, 2021.1.8f1, 2021.2.0a17
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (2021.2.X):
Sorry for the confusion but this actually is the expected behaviour because although a .fbx file may not import animations from the file, it still can reference animations from other fbx files via the "scene@clip.fbx" feature.