Transform constraint bug beta

Mmsmmike · 2025-06-02T01:37:23+00:00

Problem statement everytime I transform constraint this bone it goes to the root, and acts as if I’m moving the root.

Describe: 1) what you have tried, 2) what you expected, and 3) what actually happened.
Clicking the match button, readjusting bones. It to go to the green bone. It went to the root.
Give step-by-step instructions so we can reproduce the problem, if possible.
Not really possible

Editor information

Tell us your Spine Editor version.
4.3.35

Post your entire spine.log file here (or attach it), if you got any error messages.

Spinebot · 2025-06-02T01:38:07+00:00

It seems like you are experiencing an issue with transform constraints where the bone moves to the root instead of the intended target. This could be related to the order of constraints or the hierarchy of bones. Ensure that the constrained bone is not a child of the target bone, as this can cause unexpected behavior. Additionally, check the order of your constraints to ensure they are applied correctly. You can try resetting the constraints order or manually adjusting it to see if that resolves the issue. If the problem persists, it might be helpful to review the specific settings and hierarchy in your project to identify any potential conflicts.

Misaki · 2025-06-02T02:52:30+00:00

msmmike We would like to investigate this issue, but as Spinebot pointed out, there is a possibility that the order in which constraints are applied is not appropriate, causing other constraints to have an effect. To accurately understand the issue, we would appreciate it if you could provide us with reproducible steps from a new Spine project or a Spine project that reproduces the issue.

The reproduction project can be kept minimal with no images, similar to the skeleton you showed us in the video. You can also delete any irrelevant elements. We appreciate your cooperation.

Mmsmmike · 2025-06-02T03:03:08+00:00

heres the original file without the images.

meebkin.spine

4kB

Misaki · 2025-06-02T03:27:40+00:00

msmmike Thank you for providing the Spine project. I have identified the cause. This is not a bug, but rather the result of an option enabled in your transform constraints.

In that transform constraint, the Local option is enabled for both the source bone and the target bone:

This means that when each mix is set to 100, the local translate X and translate Y of bone29 will be applied to the local translate X and translate Y of stickjoint.

Looking at the local translate X and Y of bone29, we see the following:

When you apply these X and Y values to the stickjoint, which is a direct child of the root bone, moves to a position 1.1595 in the X direction and 2.0821 in the Y direction from the position of the root bone. (In other words, it moves to a position very close to the root bone.)

I'm not sure exactly what kind of rig you want to achieve, but if you want the stickjoint to move perfectly along the bone when bone29 is translated, you should set it up as follows: