Errors : time >= m_lastUsedTime and timeSinceLastUsed >= 0, with no traceback.

time >= m_lastUsedTime

timeSinceLastUsed >= 0

These errors fire one after another. Clicking on them in the console offers no further explanation. They do not stop my game from running, but they do halt an animation.

The only weirdness of note is that the animation is stuck in a state with its trigger still on.

The animation states go Normal → Pressed → Closed → back to normal. Normal → Pressed and Pressed → Closed happen on different trigger calls. When these errors are thrown, the animator is currently in the “Pressed” state, and the trigger to transition from Normal->Pressed is still turned on. Normally it would clear as soon as the transition to that state is done.

That’s all I got. Googling the errors gets me 4 results - in Chinese. Help is much appreciated.

i know this is an old thread, but i just solved this on my pc.
i overclocked my cpu and these errors came out of the closet!
i then clocked my cpu back down and the errors vanished!
maybe this helps!

no code changes or anything.
i know it sounds strange but every time i got these errors i ran unity on a overclocked cpu!

@paperdroid