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
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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.
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.