Search Issue Tracker
By Design
Votes
0
Found in
2017.3.0f3
Issue ID
987243
Regression
No
[FBX] Bones with imported zero weight values are invisible when configuring rig's Avatar
To reproduce:
1. Open project attached
2. In Project window, select BONEW0 (rig with weightless bone)
3. In Inspector window, press Configure, observe lower right hand
4. Repeat steps 2 and 3 with BONEW1 asset
5. Observe the differences (check pictures for easy comparison)
Expected: bones are visible no matter the weight parameter
Actual: bones are invisible when all it's weights are zero
Reproduced in: 2017.1.3p1, 2017.2.2f1, 2017.3.1p2, 2018.1.0b9, 2018.2.0a1
Note: tested with 3d Studio Max 2018
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:
in AvatarSetupTool.GetModelBones() we specifically filter out the bones with 0 weight.
By design and cosmetic.
Not willing to take the risk that there are a lot of files where non-skinned bones would pollute the view excessively