Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.37f1
2022.3.25f1
2023.2.19f1
6000.0.0b16
Issue ID
UUM-70239
Regression
No
Crash on ModelImporter::ImportSkinnedMesh when disabling "Strip Bones" on a specific FBX model
How to reproduce:
1. Open the attached “ModelCrashBug.zip“ project
2. Select the “Assets/100120_Mesh.fbx“ asset
3. Select the “Rig“ tab in the Inspector
4. De-select “Strip Bones“ and press “Apply“
Reproducible with: 2021.3.37f1, 2022.3.25f1, 2023.2.19f1, 6000.0.0b16
Reproducible on: macOS 14.4 Sonoma (Intel)
Not reproducible on: 2020.3.44f1
First few lines of the stack trace:
0x00007FFEA4C6BDFC (Unity) ModelImporter::ImportSkinnedMesh
0x00007FFEA4C619B6 (Unity) ModelImporter::GenerateAll
0x00007FFEA4C64EDD (Unity) ModelImporter::GenerateAssetData
0x00007FFEA42C0412 (Unity) ImportToObjects
0x00007FFEA42BF296 (Unity) ImportAsset
Comments (1)
-
unity_B09096004081C8AD6925
Apr 19, 2024 20:08
Recovery may old account in lost day on earth game
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
- StackOverflowException occurs and tests fail to load when the Test Runner window is opened while System.Windows.Forms.dll and System.Deployment.dll are present in the project
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.