# Does Mover support AdditiveVelocity MixMode RootMotion? 

**URL:** <https://forums.unrealengine.com/t/does-mover-support-additivevelocity-mixmode-rootmotion/2693084>\
**Category:** Programming & Scripting\
**Tags:** Epic-Pro-Support, unreal-engine, question\
**Created:** [December 19, 2025, 1:41am UTC](https://forums.unrealengine.com/t/does-mover-support-additivevelocity-mixmode-rootmotion/2693084 "2025-12-19T01:41:37Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [December 19, 2025, 1:41am UTC](https://forums.unrealengine.com/t/does-mover-support-additivevelocity-mixmode-rootmotion/2693084/1 "2025-12-19T01:41:37Z")

</div>

Based on Mover previous documents and video, rootmotion in design would no longer be the first citizen, and we can blend rootmotion with other LayeredMove. But whether it is FLayeredMove\_AnimRootMotion or FLayeredMove\_RootMotionAttribute, their mixmode is OverrideAll. And even if I change Mixmode to AdditiveVelocity, it still doesn’t work. Because the velocity generated by LayeredMove will leak into UBaseMovementMode::GenerateMove, thereby generating additional unnecessary velocity. Theoretically AdditiveVelocity typed LayeredMove is incompatible with UBaseMovementMode::GenerateMove. In the CharacterMovementComponent, there is a variable named FRootMotionSourceGroup::LastPreAdditiveVelocity specifically designed to subtract the additional velocity generated by RMS. I think Mover also needs the same treatment. Do you have any plans to support AdditiveVelocity MixMode RootMotion?

[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![PyroJimmy](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@PyroJimmy](https://forums.unrealengine.com/u/PyroJimmy)\
**Post date:** [December 19, 2025, 8:03pm UTC](https://forums.unrealengine.com/t/does-mover-support-additivevelocity-mixmode-rootmotion/2693084/2 "2025-12-19T20:03:12Z")

</div>

Thanks for reporting this. It’s a known unresolved issue, and it should be supported. As a dev user, do you have any input about how you might want this represented? For example, would including the prior frame’s pre-additive velocity in Mode::GenerateMove’s context be enough? That could include velocity from the movement mode and/or any higher-priority overriding layered moves. Would you find the velocity just from the mode helpful as well?

[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [December 20, 2025, 1:46am UTC](https://forums.unrealengine.com/t/does-mover-support-additivevelocity-mixmode-rootmotion/2693084/3 "2025-12-20T01:46:18Z")

</div>

Hi Justin,

It’s my pleasure to receive your reply. Our typical use case is that one character is being attracting (by traps, black holes, etc) while he is playing root motion ( attack s or hit reactions, etc). Also, we have complex movement projectiles which could be controlled by multiple layered move ( surrounding, homing, avoidance, etc) while they can have their own movement mode to implement something similar to MoveAlongFloor or SlideAlongSurface in CMC. I think including prior frame’s pre-additive velocity(only from movement mode) is enough for us currently, also, including higher-priority overriding layered moves sounds awesome. Thank you!

[Attachment Removed]
