v0.7.0-alpha3

[Remi123]

This release is a complete overhaul on how we manage memory and the animation is now much more robust.

Here is the most importants notes on this release :

1. The kdtree and all the data is now inside MMAnimationLibrary. This make more senses since we can create MMAnimationLibrary with purpose like "Locomotion" or "Attack" and query different information. It also allow reusing the same kdtree.
2. MMAnimationPlayer is now always initializing. In case the current animation finish, the body will inertialize to the last frame of the animation, instead of clipping to it. This also allowed the creation of request_pose(animname,timestamp) which move the body to the skeleton position at that time in the animation.
3. MotionFeatures now have a series of PackedFloat32Array serialize_XYZ(obj:Object) functions that let you obtain the information from the node that know the information. For example BonePositionVelocityMotionFeature has serialize_mmplayer(mmap:MMAnimationPlayer) and it retrieve the information correctly. Append all the MotionFeatures result into a single PackedFloat32Array and use MMAnimationLibrary::query_pose(accumulated_features_info), this will return a dictionary containing which animation and what time is the closest.

I still need to write the docs, but in a nutshell.

1. Create a MMAnimationLibrary, and add all animations inside it.
2. Select the MMAnimationLibrary in the file explorer, then you will see a MotionMatching tab in the bottom editor and a few options in the Inspector.
3. There is a MotionFeatures array in the Inspector, fill it with a few MotionFeature resource, then fill the info. In the Bottom Panel, press Bake, wait a little and there you go.
4. At runtime, for each features in the motion features, call serialize_XYZ and append the result to an array. The order is VERY important.
5. Call var pose := MMAnimationLibrary::query_pose(serialized_info) and pass the result to the MMAnimationPlayer::request_animation(pose.animation,pose.timestamp).
6. Repeat this process as much as you want.

There is some missing detail that the doc will go much further into, but this is the TLDR on how to use it.

---

This discussion was created from the release v0.7.0-alpha3.