On UE5.3, the engine just simply doesn’t take additive layer track(edited in anim seq asset) to root motion.
Things changed on UE5.4, the engine attempts to take additive layer track data to root motion, however, not in an opposite direction, which results in double movement when root motion enabled.
I think the bug can be easily reproduced with any anim seq, as this seems to be an oversight rather than an exception.
bump