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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment