Search Issue Tracker
Fixed
Fixed in 2020.3.44f1, 2021.3.11f1, 2022.1.23f1, 2022.2.0b14, 2023.1.0a3
Votes
1
Found in
2021.3.8f1
2022.2.0a17
2023.1.0a1
Issue ID
UUM-3981
Regression
No
Editor get stuck loading when Importing Corrupted FBX Models
Reproduction steps:
1. Open user attached Project
2. Wait
Expected result: The Project is Imported
Actual result: The Project loads forever
Reproducible with: 2019.4.29f1, 2020.3.14f1, 2021.1.16f1, 2021.2.0b4, 2022.1.0a3
Comments (1)
-
davidallan1703
Aug 17, 2021 11:12
Just to note this bug doesn't happen on 2020.2.4f1 and works as intended, and also happens for .mb files that Unity converts to FBX via Maya 2019. I personally couldn't recreate the bug in Windows, and things worked as expected (although it took a while), the FBX models in the project are opened without issue by Maya and seems to just be a bug in unity's loading of them in MacOS.
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
- “Asset X has no meta file, but it's in an immutable folder. The asset will be ignored.” errors are thrown when importing package with files not listed in package.json's "files" property
- There is no way to adjust the HDR Paper White value of the Unity Editor's interface, making it difficult/uncomfortable for some developers to work on very dark/bright scenes in HDR
- Animator window has a dropdown button that throws “MissingReferenceException” error on a new project when the previous project had a GameObject with an animation
- Animator State name overflows outside the visual box when the State has a long name
- UI Document file remains marked as Dirty after Undoing made changes
Resolution Note (fix version 2022.2.0b14):
Fixed UUM-3981 @ashwin-g:
Graphics: Graphics: Fix issue in which editor would get stuck when importing corrupted FBX models.
Resolution Note (fix version 2021.3.11f1):
This fix only works for Apple silicone, but not for Intel machines
Resolution Note (fix version 2020.3.44f1):
Hi,
Thanks again for reporting this issue. It's now fixed in Unity 2020.3.44f1 and above.
Please reach out to me if I can be of further help.
Thanks,
Povilas
Customer QA Team