Good morning! It seems like you're experiencing differences in animation behavior between the Spine editor and Unreal Engine when changing the animation speed. This issue might be related to how physics and animations are handled differently in the two environments, especially at higher speeds. In the editor, animations might be previewed with a certain consistency, but when exported to Unreal Engine, the physics simulation can behave differently due to differences in frame rates or physics calculations.

To address this, you might want to ensure that the physics settings in both environments are as similar as possible. This includes checking the frame rate settings and ensuring that any physics constraints or properties are consistent. Additionally, consider creating transition animations or adjusting the mix settings to smooth out the differences in movement and rotation at higher speeds. If the problem persists, sharing your project files with the support team could help them provide more specific guidance.

I'm guessing that you are setting the AnimationState time scale, which affects animation playback speed. Physics are driven by skeleton time rather than animation time, as there could be many animations running at different speeds. Typically the skeleton time is updated each frame, incremented by the time since the last frame. To run physics at a different speed, updating the skeleton time needs to change accordingly. My colleagues who are more familiar with how this is done in Unreal will be along to help soon, though a number of the Spine team are on vacation for the holidays, so it may be a little longer than usual.

Yes, it sounds reasonable to have a node that can change the skeleton update rate, if that doesn't exist yet.

In general the node-based programming is somewhat limited. Everything is available in C++.

I'm glad you are enjoying physics!

I've added an issue here.
EsotericSoftware/spine-runtimes2727

We need a Blueprint function that let's you set the scaling factor applied to the skeleton update that. However, that is a "global" setting for the skeleton. If you enqueue multiple animations with different animation time scales, it will not work.

Thanks, that clears it up! I guess we need a "physics time scale" instead then.

This week!

I've now implemented functions in both SpineWidget and SpineSkeletonAnimation called SetPhysicsTimeScale and GetPhysicsTimeScale. They work similarly to the time scale on TrackEntry instances, in that they will scale the delta time.

Please update your local copy of spine-ue with the latest sources from the spine-runtimes repo, branch 4.2.