Hello everyone,
After copying my arm hierarchy with path constraint the copy doesnt act like i want.
I reaply the path constraint on the other arm.
Every vertices position is changed when path constraint is applied.
Thanks.
Hello everyone,
After copying my arm hierarchy with path constraint the copy doesnt act like i want.
I reaply the path constraint on the other arm.
Every vertices position is changed when path constraint is applied.
Thanks.
It seems like the issue you're experiencing with the path constraint and the vertices positions changing is related to the order in which constraints are applied. When you copy the arm hierarchy and reapply the path constraint, the vertices positions might be affected if the constraint order is not set correctly.
To fix this, you should ensure that the path constraint is applied in the correct order. Constraints are calculated from top to bottom in the constraints node, so you need to move the path constraint to the appropriate position in the list. This ensures that the path constraint is calculated before any other constraints that might affect the vertices positions.
Here are the steps to follow:
For more details on constraint order, you can refer to the Spine User Guide on Constraints.
Additionally, ensure that the vertices are selected and pasted in the same order when copying and pasting. This can also affect the final positions of the vertices.
If you continue to experience issues, you might want to check if the axes are set to "World" instead of "Local" as this can also impact the vertices positions when constraints are applied.
Here is a related discussion that might help: Path Constraint abnormal behavior.
WOOOH,
It's was just a bad renaming via copying.
Does spine provide naming convention for chain bone ?
Became this after duplicating
Don't understand why.
How can I prevent this from happening again ?
Have a nice day.
valahaha Hmm, as far as I tried to duplicate the stretchman-pro's path constraint with the latest version editor, Spine 4.2.33, I could not reproduce the problem of the order being messed up as you did. If you are using an older version of the editor, maybe the problem was fixed at some point. If you can reproduce the problem using Spine 4.2.33, could you please provide detailed reproduction steps?
Hey,
Thanks for your answer
I actually use 4.2.33 version.
It's a problem with the name of my bones when i rename with unique name for each bone it's seem to work instantly.
When bone are nested it work well but i needed this that way for chainscale path constraint.
valahaha Thanks for providing the Spine project! I was indeed able to reproduce the problem, and after investigating this issue, I found that the order in which the bones were created affects the problem. For example, if I create a long bone and then split it into 10 bones using the Split
button, the bones will remain in the correct order. However, if the bones were created individually and later renamed, the order in which they were first created and the numbering of the named bones must match or the order of the duplicated bones will be incorrect. I will create an issue ticket to fix this.
I have created an issue ticket here: EsotericSoftware/spine-editor817
You can subscribe to this issue ticket to receive notifications when there is any progress on this issue.
This issue will not occur if the order in which the bones are created and the names of the bones match, so I hope you will make sure they match until the fix is complete.