Search Issue Tracker
By Design
Votes
0
Found in
2018.3.5f1
2019.1.0b2
2019.2.0a4
2019.2.0a11
Issue ID
1143762
Regression
No
Timeline Preview displays object as active on the last frame of Activation Track after turning Preview off and on again
Steps to reproduce:
1. Open "SampleScene" from the attached project
2. Open Timeline window
3. Select "TimelineObject" in hierarchy
4. Go to a 300th frame (cube is disabled)
5. Turn Preview off and on
Actual result: Cube is enabled even though it's still 300th frame
Expected result: Cube is disabled as before
Reproducible: 2018.3.13f1, 2019.1.0f1, 2019.2.0a12
This Timeline behaviour was added in 2018.3.5f1 and 2019.1.0b2, 2019.2.0a4
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
- Shadows are not visible in Player when using DX12 with Forward+ or Deferred+ rendering in URP
- Rendering Debugger Playmode debug UI scrolling is jittery when using click and drag to scroll
- Frame Debugger Target Selection Search Results window becomes too tiny to even see the default “Editor” selection when there are no search results
- Async method in Play Mode being aborted when calling `new System.Windows.Forms.Form`
- Animator window Eye button on click visual does not cover the whole area of the button when clicked
Resolution Note (2021.1.X):
Timeline is inclusive on the first frame of a clip, and _exclusive_ on the last frame. This guarantees adjacent clips are never both active. In editor, scrubbing is allowed past the end of the timeline, so this is actually correct behaviour. At runtime, a 300 frame timeline is stopped before the 300th frame is reached (it runs from frame 0 to 299).