Quick answer: Choose one source of truth: either fully root-motion-driven movement that feeds the controller, or logic-driven movement with animation that matches the commanded speed.
An AI whose feet slide or whose hitbox drifts away from its visible body is running animation and logic movement at the same time. Picking one authoritative driver fixes the desync. Here is how.
How to fix it
1. Pick one authoritative driver
Decide whether root motion or code owns movement. If root motion owns it, feed its delta into the character controller; if code owns it, disable root motion's position output.
2. Match animation speed to velocity
When logic-driven, drive a locomotion blend by the actual movement speed so the feet animate at the rate the body travels, eliminating foot skating.
3. Sync the capsule to the mesh
Keep the collision capsule and the animated mesh at the same origin each frame, so perception, hits, and pathing all agree on where the AI actually is.
Catching the ones you can't reproduce
The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.
Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.
This is where a tool like Bugnet earns its place. Its SDK captures every error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.
The bug you can't reproduce isn't gone — it's just invisible until you capture it from the player's device.