Search Issue Tracker
Won't Fix
Votes
0
Found in
4.3.0b3
Issue ID
570692
Regression
No
Animator.MatchTarget produces inconsistent behavior for moving targets
To reproduce:
1. Open project TargetMatchTest
2. Open scene Test
3. Enter play mode
4. Try moving the cube in the scene. The character should .MatchTarget to the cube. Sometimes it happens smoothly, other times the character just jumps into the position
Explanation: MatchTarget is called at every frame. Mecanim register one MatchTarget at a time. So once its set, it will keep the same target time, until target is reached or user has called InterruptMatchTarget.
Also, since this is a looped state, if MatchTarget is called after the targetTime, it will wait a whole cycle to reach it.
The jumps you see, they happen when you start moving the cube, making the matchTarget command active (since target not reached anymore) at a time that is a little under the targetTime.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment