Capture mode interpolation is not affected by interpolation type

[MysteriousDeve]

Tested versions

Reproducible in v4.3.rc1.mono.official [e343dbb]

System information

Godot v4.3.rc1.mono - Windows 10.0.16299 - Vulkan (Forward+) - dedicated NVIDIA GeForce GT 1030 (NVIDIA; 30.0.14.7196) - Intel(R) Core(TM) i3-10105F CPU @ 3.70GHz (8 Threads)

Issue description

Some of the easing options for Capture track ("Auto Capture Transition Type" in the editor for AnimationPlayer) is not working correctly. For example, "Cubic" option make the animation blend elastically instead of gradually. Some other easing type have issue as well, but "Linear" seems to not be affected.

2024-07-27.16-53-32.mp4

Steps to reproduce

• Create a project
• Create a 3D scene
• Add a MeshInstance3D
• Add a BoxMesh to MeshInstance3D (or anything that makes the object visible in runtime)
• Add a Camera and move them back 2 unit so that it faces the MeshInstance3D
• Add an AnimationPlayer node and create an Animation
• Set "Auto Capture Transition Type" to Cubic
• Set Animation duration to 1 seconds
• Add an Property track, select MeshInstance3D --> Node3D/position
• Set property Update Mode to "Capture"
• Move/Set MeshInstance3D position to (2, 0, 0)
• Add a keyframe of MeshInstance3D at 1 seconds
• Move/Set MeshInstance3D position back to (0, 0, 0)
• Create a script for the root node to run the animation in AnimationPlayer in ready()
• Run current scene (F6)
• If success, the cube will more to the right with elastic movement (instead of gradual movement)

Minimal reproduction project (MRP)

auto-capture-reproduce-copy.zip

[akien-mga]

Does it work in 4.2.2.stable? Mainly trying to assess whether this a regression report or "just" a bug.

[MysteriousDeve]

4.2.2.stable doesn't have such feature. I think this is a new implementation, since the old code for this has been removed when implementing AnimationMixer, as mentioned in #83166.

[TokageItLab]

I was asked the same question by @Calinou earlier, but CaptureMode is no longer affected by InterpolationType, so you need to use a tween instead.

[MysteriousDeve]

I was asked the same question by @Calinou earlier, but CaptureMode is no longer affected by InterpolationType, so you need to use a tween instead.

Could you clarify it further? Seem that the CaptureMode is affected by TransitionType, but the curves are just wrongly labelled.
Another thing I've just found is that the bug I mentioned seems to only affect the Auto Capture properties of the AnimationPlayer, and if the Capture is used manually (via play_with_capture()), then the problem no longer exists.

[MysteriousDeve]

By the way, not only the transition type, but ease type is also messed up: Ease Out actually makes the animation ease in, and vice versa.
This was present in both Auto Capture and manual calling, should I make a seperate issue for this?

[TokageItLab]

Since it interpolates from the Captured frame to the Animation, EaseOut indicates EaseIn to the Animation (In other words, it means that the captured frame is EaseOut), so there should be no problem. Also, I don't know what is wrong with the curves, as they are working correctly.

The two breaking compatibility changes for capture mode I remember from 4.1 are that it is no longer possible to interpolate at different times for each track; Auto Capture will interpolate between the first non-zero key and the first key when the duration is -1. If there are multiple Capture tracks, the shortest interval is used. And the rest is InterpolationType is no longer affected as I mentioned above.