Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2020.3.X, 2021.1.X
Votes
19
Found in
2020.1.0a19
2020.1.0b16
2020.2
Issue ID
1265275
Regression
Yes
[Performance Regression] Importing an fbx model is noticeably slower when the model contains Animations
Reproduction steps:
1. Create and open a new Unity project
2. Import the attached "ProblematicModel.fbx" model
Expected result: it takes around 5 seconds to import the model (depending on the machine used)
Actual result: it takes over 16 seconds to import the model (depending on the machine used)
Reproducible with: 2020.1.0a19, 2020.1.1f1, 2020.2.0a19
Not reproducible with: 2018.4.25f1, 2019.4.5f1, 2020.1.0a18
Notes:
-The time values are taken from the Editor.log file
-The speed of importing only Animation files to the Editor doesn't seem to change across different Unity version and is consistently good. The problem only reproduces with an fbx file containing Animations.
-The import time is consistently around 3 times longer in the affected versions
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
- Crash on PrepareDrawShadowsCommandStep1 when entering the Play Mode in a specific project
- Physics Layer Collision Matrix's Layer names, checkboxes and hover highlights become misaligned when the Editor's UI Scaling gets changed
- Light/shadow information on an edge of a Terrain tile creates a seam with an adjacent Terrain tile when baking a LightMap
- "Missing types referenced from component UniversalRenderPipelineGlobalSettings on game object UniversalRenderPipelineGlobalSettings..." warning is thrown after switching the Platform to tvOS
- “Metal: Error creating pipeline state (Universal Render Pipeline/2D/Sprite-Lit-Default): Vertex attribute BLENDINDICES0(5) of type uint4 cannot be read using MTLAttributeFormatFloat2 (null)“ when setting GPU Skinning to GPU after opening the project
Resolution Note (fix version 2020.2):
Fixed in 2021.2.0a10
Resolution Note (fix version 2021.1):
Fixed in 2021.1.4f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.10f1