Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.4.0f1
2019.1.0b10
Issue ID
1144310
Regression
No
fbxsdk::FbxMemoryFile::Truncate crashes when importing a .fbx file
To reproduce:
1. Download attached project “Dressup.zip" and open in Unity
2. Import "Bikini.fbx", "CherryBlossoms.fbx", "CherrySkirt.fbx" or "CherryVest.fbx" file
Expected results: Unity Editor successfully imports .fbx file
Actual results: Unity Editor crashes
Notes:
- This issue appears both on Windows and macOS
- Stacktrace is shared in Comments section
Reproduced on Unity 2017.4.0f1, 2017.4.25f2, 2018.3.12f1, 2019.1.0f1 and 2019.2.0a11
Comments (1)
-
Summit_Peak
Apr 23, 2019 22:01
Both fbx and obj files cause Unity 2019.1.0f2 (Windows) to crash when opening the editor.
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- A frame spike occurs when Physics Simulation Mode is switched from Script to FixedUpdate
Resolution Note:
Those files can't be opened in either 3DsMax, Maya, MotionBuilder or FBX Review. The files must be corrupted.