Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.29f1
2022.3.6f1
2023.1.7f1
2023.2.0b3
2023.3.0a3
6000.0.0b11
7000.0.0a1
Issue ID
UUM-44743
Regression
No
Auto-Mapping fails for Humanoid Avatar when FBX file has Skinned Mesh
Reproduction steps:
1. Open the attached “ASDQWER” project
2. Select the “Assets/withSkinnedMesh.fbx” Asset
3. In the Inspector Window, select the “Rig” Button
4. In the “Rig” tab, select “Animation Type > Humanoid” and press the “Apply” Button
Expected result: The Avatar is successfully Auto-Mapped
Actual result: “Error(s) found while importing rig in this animation file. Open “Import Messages” foldout for more details” error is displayed in the Inspector Window and the Avatar is not fully Auto-Mapped
Reproducible with: 2021.3.29f1, 2022.3.6f1, 2023.1.7f1, 2023.2.0b3
Reproducible on: Intel macOS 13.5
Note: The situation is not reproducible when following the reproduction steps on the “withoutSkinnedMesh.fbx” Asset
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
- Character text is not bold in the title of GameObjects in the Inspector when naming using specific language characters
- IndexOutOfRangeException and GUI Error get thrown in Scene View when Articulation Body Edit Joints is set to "Edit the joint angular limits"
- Volumetric fog is not rendered around GameObjects that are baked with APV when Sky Occlusion is enabled
- UI Text color is incorrect when text is rendered on SubMeshUI
- "Invalid SortingGroup index set in Renderer" errors when making many modifications in same frame
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.