Mantle Bug in Game Animation Sample Project

Hello, I found a bug in the Game Animation Sample Project. When you are standing still and trying to mantle onto an object that is less than 1 meter tall, your character still mantles up to 1 meter and floats in the air. This works for all other movement states and is just broken when you are standing still. I’ve attached a video for reference. Note that these cases work as intended:

  • Walking and Running mantles on all heights
  • Stationary mantle to an object higher than 1 meter

It’s just the case where you mantle onto a smaller object that is broken. Has anyone managed to fix this? I’m looking into it and will update the post if I find an answer. Thanks!

The bug you described occurs when mantling onto objects less than 1 meter while standing still, causing the character to float. It works fine for walking, running, and taller objects. The issue seems specific to stationary mantling on smaller objects. Hopefully, you can find a fix soon, and keep us posted with updates!

I did some investigating and I narrowed it down to the following files:

  • AM_M_Neutral_Traversal_Mantle_1_0_stand_F_Lfoot
  • AM_M_Neutral_Traversal_Mantle_1_0_stand_F_Rfoot
  • M_Neutral_Traversal_Mantle_1_0_stand_F_Lfoot
  • M_Neutral_Traversal_Mantle_1_0_stand_F_Rfoot

I don’t know enough about how these curves and notifies are set up to debug further from here so I did not find a way to make it all work as expected with these montages. Essentially the attach bone is staying at exactly 1.0 meters instead of moving to the desired position.

However I found a good fix was to go into CHT_TraversalAnims and click into the Mantles section. Swap out the top two rows with AM_M_Neutral_Traversal_Mantle_1_0_walk_F_Lfoot and AM_M_Neutral_Traversal_Mantle_1_0_walk_F_Rfoot. These are the walking animations that aren’t much different from the standing ones and do the job just fine. Why the above files are bugged I don’t know, but if anyone wants a quick fix that looks pretty good then here you go.

This bug is still present in the 5.5 update by the way