- Изменено
Weight issues: 2 pictures for the same bone
Hi guys 
I'v got a issue since the new spine's version (3.6.48) with the weight (I'm on Mac)
Every time I try to weight my mesh with a common bone on my 2 pictures, in second time, I do the weight and it doesn't want to the proper auto repartition.
I mean, the second weight will be always at 100% for only 1 bone (the common one) and doesn't care about the other bones.
(you can see in my exemple)
It looks like the second weight doesn't work because of the common's bone in the middle :/
I tried to repro your problem on the raptor example file, even bounding the same bones on different meshes, but the auto weights generator has always been working good so far, I have your same Spine version, but I'm on Windows, is it possible for you to provide the file on which this problem always occurs maybe?
Please send it to contact@esotericsoftware.com mentioning this topic so I can try to test on that to repro the problem.
Ok so, I tried again with different file, and it's always the same. Anyway, I sent you an email with my file to take a look, so let me know if you found something strange 
Thank you for sending the file, I've tested your project file and it still works fine on windows, we'll try to test it on a mac soon.
Note when you press Auto with bones selected in the Weights view, it will compute weights with only the selected bones.
Thanks Nate
I just tried to select all the bones and after that, select the "auto" option, and... it works!
But I never had to do this before the 3.6.48 spine's version. So is it a new thing? Because it was more quick before, to just bind bones and hit "auto" option, directly.
Now, I have to do one more manipulation to finish my weight, I dont' understand the good thing in this :/
I think you can also deselect everything by pressing space and then hit auto.
Doing auto weights only with the selected bones allows you to bind some bones, but not have them participate in auto weighting. This can be useful for when you want to use auto for some bones, and manual for others. The normal workflow is to bind bones, then if the bones were the first bones bound, auto weight is applied when binding is complete. What workflow are you using were the new behavior requires an extra click?
In the previous version, I had just to bind my bones, and click "auto" without other things to do (before, the binding automatically applied to all the bones I chose without having to select all of them in the weight window).
Now I have to select all the bones for the binding, AND click all of them again for the "auto" option.
Since the "auto" option has come to spine a couple of years ago, I've always use the weight to manage all my bones selected. I mean, if I want 1 bones with 100% influence, I do that manually.
(version 3.5.51)
https://drive.google.com/file/d/0B9epOt8a7k3-cFhDanFyUDNRQThRdGJDVDczWEJPWTdWWXlN/view?usp=sharing
(version 3.6.48) Note the behavior now, 1 bone is selected randomly for no reason.
https://drive.google.com/file/d/0B9epOt8a7k3-Rjcyb01wdWNLSXR6cWtucWxMa20wMzFuSTEw/view?usp=sharing
It might be some bug because I was't able to reproduce it each time, don't you think?
I tried to test your repro file again.
If you simply click "Auto" in the weights panel after selecting the second mesh, it will work as expected.
However, if instead one removes the weights first, and then tries to bind the bones again, one bone will end up selected as you showed in your gifs.
Therefore the problem is that one bone (the first selected) gets automatically selected.
I could repro this on the raptor as well, by removing the weights from a leg, then binding some bones to it again.
I opened an issue listing the exact steps:
On binding the first bone gets selected, making auto weights only weight one bone · #308 · EsotericSoftware/spine-editor