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
- Crash on mono_log_write_logfile when more than one copy of bee_backend is running
- NativeList<T>.ParallelWriter.AddNoResize() causes memory corruption when used in a [BurstCompile] IJobParallelFor on Web builds
- Realtime reflection probe changes light strength when removing light sources using URP WebGL
- Objects near the screen edge are not culled when using GPU Occlusion Culling
- InvalidCastException is thrown when hovering over a Tilemap with a saved Random Brush pick containing empty cells
Add comment