Search Issue Tracker
By Design
Votes
0
Found in
2017.4.12f1
Issue ID
1091653
Regression
No
Using a loop pose in an animation slightly affects the mid-point of the animation
How to reproduce:
1. Open the user-submitted project
2. Enter Play mode
3. Click on the "Bounce, with loop-pose" button and observe the animation
4. Click on the "Bounce, without loop-pose" button and again observe the animation
Expected result: Both animations are the same
Actual result: The animation with a loop pose is off and doesn't penetrate the plane object
Reproduced in: 2019.1.0a5, 2018.3.0b6, 2018.2.13f1, 2018.1.9f2, 2017.4.13f1
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Sprite Masks affect Sprite Renderers outside their range when a Light2D is present with specific Target Sorting Layers selected
- URP Lens Flare is rendered in the wrong position when Render Graph Compatibility Mode is enabled and Render Scaling is not 0
- Editor crashes on DrvPresentBuffers when loading RenderDoc while using OpenGLES 3.0 or OpenGLES 2.0 Graphics API
- [Test Runner] Incorrect name under Window > Panel after project restart
- [iOS] Crash when using fallback fonts created at runtime
Resolution Note:
This is the expected behaviour for loop pose, basically we compute the difference between the first frame and the last frame, then we add this difference progressively over the complete length of the animation, to assure that the first and last frames are the same.
This is why there is a loop light quality in the model importer, if the difference is too big the light will be red.