Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2019.1.0a9
2019.1.6f1
2019.2.0a1
2019.3.0a1
Issue ID
1165175
Regression
Yes
Errors "Bone index is not within the number of bones" are thrown when render.sharedMesh.boneWeights is set to null
How to reproduce:
1. Open the attached project ("case_1165175-bug_remove_skin.zip")
2. Reimport the "male_body.fbx" asset
3. Inspect console
Expected results: No errors in the console
Actual results: "Bone index is not within the number of bones" errors are thrown
Reproducible with: 2019.1.0a9, 2019.1.8f1, 2019.2.0b8, 2019.3.0a8
Not reproducible with: 2017.4.29f1, 2018.4.3f1, 2019.1.0a8
Comments (3)
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
- Animator Controller throws MissingReferenceException after undoing Layer Creation
- Full stack trace is always printed when an exception occurs in an IL2CPP build
- Licensing Client fails to launch when opening Unity Hub (licensing client path is not found)
- Licensing Client fails to launch when opening Unity Hub
- Different custom Shader behavior when GPU Resident Drawer is enabled
frozenpepper
Jun 03, 2023 21:37
Started getting this recently (Unity 2022.3.0f1 and 2021.3.26f1) and in my case it is related to EasyDecal. Brute forced a solution by using "EditorUtility.CollectDependencies()" to gather the SkinnedMeshRenderers EasyDecal references internally and destroying them. Can now build again. I'm not using Skinned Decals so don't know if solution would work in that case too.
kbm
Apr 17, 2021 21:35
I am still getting this error in Unity 2020.3.3f1 in combination with the EasyDecal plugin.
Any help would be greatly appreciated!
andyasj
Aug 26, 2019 08:11
This issue in android build 2019.1.6f1