I don’t think it’s a bug, rather just an unfortunate side effect
the main node should be centered, then it would smoothly spin
tough to explain but if you think about how tweening is working, to go from keyframe1 -> keyframe2, it’s rotating the object across (2/4/8/whatever) tweened frames, but ALSO moving the main node to match where it is in keyframe2
it doesn’t necessarily transition visually how you want it to in this case
Replying to:roninOh, more reasons to not use tween.
1+ points for “add tween
I was going to say (but I see you don’t have the update lolol) press “Add tweened frame” and it will create a tweened frame, the same one the app generates when playing, and you would see how it moves the figure and how in that one frame, it’s “wrong”
so with tweening it’s jittering all over right?
I don’t think it’s a bug, rather just an unfortunate side effect
the main node should be centered, then it would smoothly spin
tough to explain but if you think about how tweening is working, to go from keyframe1 -> keyframe2, it’s rotating the object across (2/4/8/whatever) tweened frames, but ALSO moving the main node to match where it is in keyframe2
it doesn’t necessarily transition visually how you want it to in this case
tl;dr center the main node and spin it
Oh, more reasons to not use tween.
1+ points for “add tweened frame”
I was going to say (but I see you don’t have the update lolol) press “Add tweened frame” and it will create a tweened frame, the same one the app generates when playing, and you would see how it moves the figure and how in that one frame, it’s “wrong”
also lololol
*welp*
At least i can adjust it
And i also understand the explanation, as long as it’s not the language called ‘high af’
aka Dalton
exactly