Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.3.14f1
2019.4
2020.1
2020.2
Issue ID
1252768
Regression
No
Freeze when importing a specific FBX file
Reproduction steps:
1. Open user's attached project
2. in the Project window, click on MSL_clean_NoStringblend.fbx
Expected result: Inspector shows asset information
Actual result: Editor freezes
Reproducible with: 2018.4.23f1, 2019.4.0f1, 2020.1.0b12, 2020.2.0a14
Note:
1. If the project version is changed, the freeze will occur when trying to open the project.
2. With 2019.4.0f1 the FBX was able to be selected, but when trying to reimport the asset, the editor froze.
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
- Different text alignment in the column header in Entities "System" window
- 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
Resolution Note (2020.2.X):
The supplied asset has over 2,500 animation clips on one object. This is why it won't open in Blender, Max, Motion Builder and so on.
In Unity it does open, & the Inspector does eventually display, however it takes a very, very long time because it has to traverse 2,500 individual clips. This volume of clips is beyond what we would reasonably expect on an object, & I would suggest it's most likely an error has occurred at export or configuration time.