Search Issue Tracker
Fixed
Fixed in 1.7.7, 1.8.8
Votes
0
Found in [Package]
1.7.6
1.8.7
Issue ID
TB-317
Regression
No
TimelineAsset.SetStandardFrameRate() throwing errors due to a typographical error in TimelineAsset.cs when the method is utilized
How to reproduce:
1. Create an empty project
2. In the Project window, locate the Packages folder
3. Navigate to “Packages > Timeline > Runtime > TimelineAsset.cs”
4. After opening TimelineAsset.cs using any code editor software, navigate to line 86
5. Observe the code editor window
Expected result: rate.IsValid() is checking if StandardFrameRates are not defined properly
Actual result: rate.IsValid() is catching properly defined StandardFrameRates
Reproducible in: 1.7.6 (2021.3.46f1, 2022.3.54f1), 1.8.7 (2021.3.46f1, 2022.3.54f1, 6000.0.30f1, 6000.1.0a7)
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environments tested
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
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Resolution Note (fix version 1.7.7):
Verified in branch staging/2022.3-1.7
using 2022.3.54f1