Hm, I see what you mean. That was done to suit our pipeline here, but I can see how you may not want that result. So it depends on what you’re actually looking for here.
For instance, the root itself has a rig control that is not the master (it’s a little purple sphere) that you could transfer that motion to post import. It’s hard to explain, but our workflow here for root motion generally goes like this:
-animator creates animation the way they want, not worrying about root and animating only body and limb controls (no master)
-the animator then animates the purple sphere (root) the way they want the root to follow(generally, this is a point constraint with maintain offsets to the body control)
-end result gets exported and you now have root motion animation.
by animating the master directly, you’re still getting root motion because the root control will follow with. I don’t have a quick fix for getting mocap to directly import onto the master, but if the above method would suit your needs, it might be the way to go.
Sorry about that, and sorry for the delay. I was attempting to enjoy some vacation time and got sick instead 