Search Issue Tracker
Active
Under Consideration for 1.7.X, 1.8.X
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Animation Clip with Legacy enabled does not play when Time.timeScale is set to 0 despite Update mode set to "Unscaled time"
- Rename is enabled on subfolder empty space - "Can't rename to empty name" warning
- SamplerState Property Missing Anisotropic Filtering
- Visual glitches when using Handles API
- The RGBA color values are inconsistent when comparing two identical colors set in the Inspector
Add comment