Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.5.0-preview.5
Issue ID
1284417
Regression
No
Timeline frame pausing is inaccurate at low framerates
Reproduction steps:
1. Open user's attached project "TimelineFrameTests.zip" and scene "SampleScene"
2. In Hierarchy window, select "Timeline" GameObject
3. Enter Play Mode
4. Observe Timeline window
5. In case timeline pauses at frame 176, exit play mode and repeat steps 2-5
Expected result: Timeline pauses at frame 176
Actual result: Timeline pauses at frame 177
Reproducible with: 1.5.0-preview.5 (2019.4.12f1, 2020.1.9f1, 2020.2.0b8, 2021.1.0a1)
Could not test with: 2018.4.28f1 (script errors break project)
Note:
The bug occurs more often the lower the frame rate is.
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
- A frame spike occurs when Physics Simulation Mode is switched from Script to FixedUpdate
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
- No audio is played when Playbable Mixer is changed at runtime
- Editor hangs when painting Details containing 2D Mesh on Terrain
- No audio is played when TimelinePlayable has one output
Resolution Note:
Timeline is sampled based on the frame rate. It rarely samples 'on frame'. Signals trigger when the time crosses the signal boundary, so this is expected behaviour and not considered a bug.
A workaround for this issue is to set the playableDirector wrap mode to hold, and set the root Playable duration to the time of the signal. That will prevent timeline from going past the signal time. When the signal triggers, change the duration to the next signal, or the timeline duration if there are no more signals.