Sometimes an End notification that I added inside my animMontage, does not fires. And I am using Root Motion.
So, I change the Movement state to Flying, start the the AnimMontage( Root Motion ), and when it ends, I set the movement state to Walking again. But if that notification event does not fire, my character keeps floating around.
Look here on this video:
You can also see on that video, that sometimes, the Root Motion does not work.
Very well implemented, that bug aside!
Have you tried making the event fire a couple frames early in the animation rather than the end, or possibly adding a redundant “Movement state = walking” to the idle/walking animations? Those might be a temporary fix. Just throwin’ some ideas out there.
Good luck!
Thanks.
Yes, I try adding making a couple frames early. Most of the time it works, but sometimes, it just does not fires.
Also, the root motion, sometime does not works as you can see on the video. Everytime I change something inside blueprint, root motion stops working. I have to almost compile everything to make it work again. ARRHHHHH!!! I just added a Print string to my blueprint, and Root Motion stopped working. How can we work with that? I remove the print string, compile and save, and now root motion is working again.
Well, I made another test. Root motion was working. So, I save everything and close the editor. Then I openned it again, and played the level… Surprise, root motion is not working again.
Yeah, since root motion isn’t replicated over the network yet I’ve been avoiding it anyways. (Or so I think, I vaguely remember reading that somewhere) If all else fails you can script the movement in Blueprint for now, although it’ll probably take a lot of fiddling with to get it to look how you want it.
Root motion is replicated across the server, but AnimMontages are not.
If you want the notifies to trigger reliably, use Branching Point in AnimMontage. Notifies are supposed to trigger at the end of the frame. If you have a hitchy, it can skip or any other animation will blend in before it triggers. Could you see if branching point fixes the issue?
Thanks,
–Lina,
Thanks. Branching Point it is!
Thanks so much! I’ve been stuck on this same bug for days. It only happens when root motion is enabled which was super annoying!