Search Issue Tracker
Fix In Review
Votes
0
Found in [Package]
1.4.4
Issue ID
1312198
Regression
Yes
Timeline frame selector field appears uneditable after selecting the Timeline in Hierarchy window and reopening project
Reproduction steps:
1. Create a new Unity project with a 3D template (or just add a Timeline package to any project)
2. Create a Timeline in the Assets folder and add it to the Scene and save the Scene
3. Double-click on Timeline in the Assets folder and select Timeline in the Hierarchy window
4. Right-click on the left side of Timeline Editor and create any Track
5. Try clicking on the frame selector field (has 0 as default) and write in some number and notice how it works
6. Select the Timeline in the Hierarchy window and click on the frame selector field again
7. Close the project and reopen it
8. Repeat steps 6-7 once again
9. Select the Timeline in the Hierarchy window and try clicking on the frame selector field
Expected result: The frame selector field is clickable and looks editable
Actual result: The frame selector field is not clickable, but you can still write in a number and change it
Reproducible with: 1.4.4 (2019.4.20f1, 2020.2.4f1), 1.4.6 (2020.2.4f1), 1.5.2 (2021.1.0b6), 1.6.0-pre.1 (2021.2.0a4)
Not reproducible with: 1.2.18 (2019.4.20f1), 1.4.3 (2019.4.20f1, 2020.2.4f1)
Couldn't test with: 2018.4 as the Timeline package is not available
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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment