Long bezier curves lead to obvious linear movement

Count0

In my attached example it is very visible that the bezier curves are used to generate a linear lookup. Having to insert new keyframes only to remove them before editing the curve again results in an awkward workflow.

I see three possible solutions:

Actually use the real bezier values
Set the number of keyframes exported from a single curve keyframe
Set the size of the lookup table, per curve

Pharan

@[silindi]
Count0 means key interpolation graph curves. Not PathAttachment bezier curves. This has nothing to do with paths.

nimbling

Would adressing this touch on an in-dopesheet curve editor that allows separate axes?

Pharan

No. It's a matter of resolving Bezier curves, and how to optimize its architecture and math for memory use, speed and accuracy.

Nate

Spine computes the Bezier curve as 10 segments, which works for most cases without being able to notice linear speed. Unfortunately you cannot increase the number of segments in the editor, however in the runtimes you can use any number of segments you like.

nimbling

One can hope 😉
<3

Count0

@[silindi]
Well that's the problem. In 98% of the cases 10 is a good number for the runtime. Not optimal to have to use a much higher number for all animations when only ₂% need it :/

Nate

Adding more keys can serve as a workaround for now. It might make sense to allow the segment count to be specified per curve, we'll consider it for a future update.