Search Issue Tracker
Fixed in 2020.2.9f1
Votes
1
Found in
2019.3.8f1
2019.4
2020.2
Issue ID
1239893
Regression
No
MinMaxGradient is stuck at its initial value in the Clip Inspector when used as an Animatable field of a Timeline clip
How to reproduce:
1. Open the attached "CleanProject.zip" project
2. Open the "SampleScene" Scene
3. Select the "PlayableDirector" GameObject -> Focus the CustomClip contained in the Timeline Window
4. Move the Timeline Playhead to preview clip property animations
Expected result: Both MinMaxCurve (float) and MinMaxGradient (color) value change
Actual result: MinMaxCurve value changes while MinMaxGradient's color is stuck at its initial value
Reproducible with: 2019.4.2f1, 2020.1.0b14, 2020.2.0a15
Notes:
- Could not reproduce in 2018.4.24f1, because of Timeline losing its values
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
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment