This reminds me of every other time that Roblox for whatever reason adds a new feature to the engine (usable now) but intentionally disables it and spams errors if you try to use it. (This happened to me with ZoomToExtents and IKControls in the past!)
For now, the only way to stop these useless error messages is to set the AnimatorIsThrottledPropertyEnabled DFFlag to true, which requires Roblox Studio Mod Manager or a ClientSettings(?) modification.
They should really come up with a new “log message type” for disabled features like this so I can hide them easily; It makes it harder to spot legitimate errors while my experience is loading.
FWIW, this error does seem to happen when printing a Humanoid into the Output window, as indicated by the subject of the original poster. If you can avoid outputting the Humanoid variable then the error goes away.
I was using code like this to keep track of when damage was happening to a humanoid “hum”.
print("Damage", hum, hum.Health)
Changing the print to use hum.DisplayName causes the “Animator.EvaluationThrottled” error to go away.
print("Damage", hum.DisplayName, hum.Health)
Not a fix for the underlying problem, but a workaround that helps clean up the Output window.
I just got this error recently too while working with Animator Instances. I was not printing the Animator instance anywhere, though. However, after removing a print statement which was printing out the client Camera instance, the error went away. Very odd.
