- Изменено
Skeleton Utility Objects Not Following Spine Skeleton
My spine (Spine 4.0.56) rig has stretchy bones that follow a path. The Utility skeleton (Unity 2017) objects are following but not correctly at all (in follow mode). Animation works fine in 2017.1.0 otherwise but I would like to attach other objects in the hierarchy without using the bone follower script.
Is there a fix for this issue? I'm assuming its some sort of problem with using IK or scaling bones. I'll send you the dragon rig if you have Unity 2017.1.0p4 available.
Hello, would you mind sharing some more information and/or screenshots of your issue?
I understand from your post that the utility skeleton objects are following; but what behavior are you expecting, and what behavior are you getting?
So in play runtime mode the expected behavior for the Skeleton Utility game objects is that they exactly match the transforms of their assigned bone transforms. In the image you will see that the manipulator for the selected game object shows that the HeadCTL bone is nowhere near the head.
The actual position of the HeadCTL bone is in near the eyes inside of the spine software program that I use to animate in. I assume it is that way in unity but the Skeleton Utility script isn't reading it that way (I guess). The animation itself is working perfectly in unity so I would assume that all the deforming bones are in their correct positions inside of unity.
All skeleton utility game objects that are in the neck and head area are not following correctly either and what they have in common is that those bones are under the influence of path IK constrains and bone scaling in the actual spine rig.
To show that the bone script is in fact engaged.
Which version of the spine-unity 4.0 unitypackage are you using (name of the unitypackage, also listed in the included version.txt
file)?
JPWestmas написалI'm assuming its some sort of problem with using IK or scaling bones. I'll send you the dragon rig if you have Unity 2017.1.0p4 available.
Yes, could you please send us a minimal Unity project that still shows this problem? You can send it as a zip package to contact@esotericsoftware.com (briefly mentioning this forum URL so that we know the context), then we can have a look at it.