Search Issue Tracker
Active
Votes
0
Found in
2021.3.30f1
2022.3.10f1
2023.1.15f1
2023.2.0b12
2023.3.0a7
Issue ID
UUM-52903
Regression
No
Time of the “AnimationClipPlayable” will not automatically advance to the next frame when setting the time of the “AnimationClipPlayable”
How to reproduce:
1. Open the user’s attached “Repro_latest.zip” project
2. Open “Test” Scene
3. Enter Play Mode
4. In the Hierarchy, select “SKM_Manny” GameObject
5. In the Inspector window, press the “Sync Once” button
6. Observe the Console window
Expected result: The results of GetTime in two consecutive PrepareFrame outputs are not equal
Actual result: The results of GetTime in two consecutive PrepareFrame outputs are equal
Reproducible with: 2021.3.30f1, 2022.3.10f1, 2023.1.15f1, 2023.2.0b12, 2023.3.0a7
Reproduced on: macOS 13.5.2 (Intel)
Not reproducible on: No other environment tested
Note: According to the rules of Playables, at this point, the `PrepareFrame` and `ProcessFrame` methods of the AnimationClipPlayable should not have been executed yet, so the impact caused by `SetTime` should theoretically be consumed in this frame and should not carry over to the next frame (user’s info)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on "block_merge_next" when entering PlayMode in a scene from the "POLYGON War Map - WWI - Low Poly 3D Art by Synty" package
- [Win ARM] URP projects fail to build that have a space in the name
- [Android][OpenGL]Soft Shadows contain artifacts when the OpenGL Graphics API is used
- The particle system prewarm flag is ignored when calling the Start function after the Stop function
- The Scene view flickers when moving around if there are visible Hair Shaders
Add comment