Search Issue Tracker
Fixed
Fixed in 2022.3.7f1, 2023.1.7f1, 2023.2.0b3, 2023.3.0a1, 2024.1.0a1
Votes
13
Found in
2022.3.1f1
2023.1.0b21
2023.2.0a18
2023.3.0a1
Issue ID
UUM-38104
Regression
Yes
Crash on "'anonymous namespace'::ConvertFBXShapes" when importing an FBX file
How to reproduce:
1. Create a new project
2. Import the “Carmen.fbx” file into the project
Expected result: The file is imported
Actual result: The project crashes
Reproducible with: 2022.2.0a16, 2022.3.1f1, 2023.1.0b21, 2023.2.0a18
Not Reproducible: 2021.3.27f1, 2022.2.0a15
Reproduced on: macOS Ventura 13.4, Windows 11 (User Reported)
Note: The issue was reproducible but it was a Silent Crash
First few lines of the Stack Trace:
0x00007ff6e64ffa38 (Unity) `anonymous namespace'::ConvertFBXShapes
0x00007ff6e64fe3b2 (Unity) UnityFBX::ConvertFBXSceneToImportScene
0x00007ff6e6502c69 (Unity) UnityFBX::DoImportScene
0x00007ff6e64b6081 (Unity) FBXImporter::DoMeshImport
0x00007ff6e6cc2dea (Unity) ModelImporter::GenerateAssetData
0x00007ff6e6371f15 (Unity) ImportToObjects
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
- Sprite Atlas remains loaded in memory after scene change or unloading assets
- Decompressing a DeflateStream under IL2CPP misses a few bytes
- Referred style sheet stays dirty after saving when using the UIBuilder
- The Height map Amplitude is not working when using HDRP/LayeredLit
- Infinite inertial tensor rotation values are not discarded (both AB and RB)
supneo
Jun 06, 2023 14:51
It's frustrating that you can't import new characters or simply can't update your project to a new version because of this annoying error with fbx, I hope it gets fixed quickly , thanks.