Agreed, as Spine projects get more complex they feel like magic at first! It can be OK if the complexity is truly warranted, but as you said we should help people understand and achieve the most common goals so they can apply that to their more unique scenarios.

Using a transform constraint like this and leveraging the wrapping of world rotation 0-360 to achieve modulo is very clever, but probably not the simplest solution. Now that we have sliders, you should be able to get a much more straightforward solution. It's also more powerful, as you can animate the walk however you like.

For the spider to pause between steps, you'd just animate it!

Here's a neat one:

Изображение удалено из-за отсутствия поддержки HTTPS. | Показать

There's only a single bone rotating here. The seconds hand is controlled be an animation, so there is full control of the tick-to-tick movement. Also note the shadows.

Good luck!

Do i have to use the 180°-360° rotation split, what Harald has written above to avoid the snap? Or is there another solution with the slider?

Sure, I can post the finished project, but that ruins the fun a little so I'll wait a while. If I post it, there would be a strong temptation to just look at the solution rather than figure it out. Better not to tempt!

Probably you are running into "world rotation wrapping". World rotation is defined as the direction the bone is pointing in world space, which in the Spine editor is screen space, ie your monitor. There are only 360 degrees in a circle. As a bone rotates, at some point its world rotation has to jump from 359.999 back to 0. That jump can wreak havoc with your slider or transform constraints, since it will cause the target bones to jump.

0 world rotation is pointing right, which would be 03:00 on a clock. That's why you see a jump at 03:00. As as you rotate clockwise past 03:00 you jump from 0 to 359.999 degrees world rotation.

To prevent jumps with your constraints, use local space by checking Local on the left (source bone) side of the transform constraint properties. In local space the local rotation is defined so 0 degrees is pointing in the direction of the parent bone and any other value is how far from 0. In local space you can go > 360 or < -360, around and around, without any jumps back to 0.

It's so common to use local space on the source side, maybe it should be the default.

Ok, local was already a solution option, but then my constraint couldn't move anymore. I could see i still used the world coordinates instead of local coordinates. So one step further . Thanks for the hint. So don't share the project.

Nate
我是通过滑块跟物理去做的，不知道是否正确，但是阴影我不知道该怎么处理了

Nate


另外我觉得滑块约束缺一个跟变换约束一样逻辑的东西
1.下面主要用来控制它的映射方式，直接通过匹配数值就好了
2.通过混合数值的大小和正反来控制，映射的比列
滑块约束也添加一个类似变换约束的匹配数值，和混合来控制比例，会不会方便很多？

warmanw 哈哈哈期待他们公布答案

A slider can stomp (or mix from) values from your animations. If you don't like that, which is common, then you can check Additive on the slider. That makes key values add to whatever the pose is when the constraint is applied, instead of replacing (or mixing from) the current value. Keys are stored relative to the setup pose, so when you key the setup pose, it's actually storing zero. The current value plus zero is of course the current value, so you can have an animation that has no effect in some parts.

Here's the project with our solution:

Nate 还是不太明白你的建议是什么

就是为滑块约束也添加上，类似变换约束的【匹配】按钮，这样就不用手动输入数值了

变换约束的【混合】，通过0-100、-100-0，或者任意数值，来控制骨骼之间的映射变换比例，和正反变换方向的

我认为滑块约束的混合或者应该有个类似的功能，用来控制骨骼跟时间轴之间的映射变换比例，和映射方向
目前滑块约束的混合，是用来控制动画的混合，而不是骨骼跟时间轴映射之间的混合
不知道这样描述可以吗