Search Issue Tracker
Fixed
Fixed in 2022.3.42f1, 6000.0.0b16
Votes
0
Found in
2020.3.45f1
2021.3.18f1
2022.2.6f1
2023.1.0b3
2023.2.0a1
2023.3.0a3
6000.0.0b11
Issue ID
UUM-26794
Regression
Yes
Unity crashes when a specific .obj file is imported
How to reproduce:
1. Create a new project or open any project
2. Import the attached file “octahedron.obj“
Expected result: File is imported
Actual result: Unity crashes
Reproducible with: 2020.3.45f1, 2021.3.18f1, 2022.2.6f1, 2023.1.0b3, 2023.2.0a1
Reproduced on: macOS 13.0.1 (Intel)
Note: Unity doesn’t crash if the file is converted to the .fbx format before importing
----------------------------------------------------
This bug was introduced during a recent update of the FBX SDK. The SDK is owned and built by Autodesk and they decide when to release a new version.
We found a fix and sent it to them but we don't know when they'll make it available.
We will publish this as soon as we get it but this is sadly out of our control.
Thank you and really sorry about the inconvenience
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 ResizeScriptingList<ScriptingObjectPtr> when passing an undeclared variable to the results parameter for GameObject.FindGameObjectsWithTag
- [Android] "Screen.safeArea.y" always returns values outside of the Safe Area when the device is in Portrait orientation
- Frame spike due to many TreeRenderer.TreeUpdated calls when repositioning terrains in large Scenes
- Crash on GameObject::RemoveComponentFromGameObjectInternal when reparenting Text GameObjects
- [IL2CPP-GarbageCollector] Changing GCMode might permanently disable GC in a multithreaded context
Add comment