title: Fluent movement with NetworkTransform & NetworkAnimator
body: <p>My player character moves around the world using the Animator with root motion activated. Basically, the AI system sets the velocities on Animator, which in turn controls the Animation clips that control character motion. As this is a standard feature that ensures very realistic animation without noticable sliding, I thought this was a good idea ...until I added Network synchronization.</p>
  
  <p>Synching the characters over the Network using NetworkTransform and NetworkAnimation causes those two components to conflict:</p>
  
  <ul>
  <li>NetworkTransform moves the character to whichever position the host commands.</li>
  <li>NetworkAnimator syncs the animation vars and plays the Animation clips as host instructs it to, while those Animation clips also apply root motion.</li>
  </ul>
  
  <p>The result is precise (meaning the character reaches the exact target destination), but very stuttering movement (noticable jumps).</p>
  
  <p>Removing NetworkTransform, the host and client instances of the characters desynchronize very quickly, meaning they will end up at different positions in the world when solely controlled by the timing-dependant Animator.</p>
  
  <p>Removing NetworkAnimator, client instances won't play the same animations as the host, if any animations at all.</p>
  
  <p>I tried keeping both Components while disabling root motion for the Animator (on client only). In that case however, NetworkTransform does not seem to interpolate at all. The character just jumps from synched position to synched position in steps of about 0.02 units. Same with rotation.</p>
  
  <p>NetworkTransform is configured to "Sync Transform", as the character neither has a RigidBody nor a CharacterController. All other values are the defaults: sync rate of 9 (also tried higher values there), movement threshold of 0.001, snap threshold of 5, interpolate movement = 1.</p>
  
  <p>How do I get fluent root motion based movement on the Network? I expected that to be a standard scenario...</p>