Search Issue Tracker
Fixed in 2020.3.44f1
Fixed in 2020.3.X, 2021.3.X, 2022.2.X, 2023.1.X, 2023.1.0a14
Votes
0
Found in
2020.3.38f1
2021.3.8f1
2022.1.14f1
2022.2.0b6
2023.1.0a8
Issue ID
UUM-12321
Regression
No
Colors majorly change when the Volume Component's "Weight" property value changes from 0 to any small value
Reproduction steps:
- Open the attached project
- Select the “Volume” GameObject in the Hierarchy window
- Play around with the Volume Component’s “Weight” property slider in the Inspector window
- Observe the colors in the Scene View
Expected result: Colors majorly change when the Volume Component’s “Weight” property value changes from 0 to any small value
Actual result: Colors gradually change when the Volume Component’s “Weight” property value changes from 0 to 1
Reproducible with: 10.10.0 (2020.3.38f1), 12.1.7 (2021.3.8f1), 13.1.8 (2022.1.14f1), 14.0.3 (2022.2.0b6), 15.0.0 (2023.1.0a8)
Reproducible on: Windows 10 (21H2)
Comments (2)
-
Friedemann_A
Oct 24, 2025 09:17
This seems to still be happening in Unity 6
-
DavidNLN
Apr 02, 2023 17:17
This still happens in 2022.2.11 a small change for 0 to 0.000001 drastically changes the color curves, the rest of the overrides seem to work fine
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
- MissingReferenceException errors are thrown after entering Play mode when multiple Inspector windows are displaying different objects with Grid Layout Group component
- "Can't change name, category with the same name already exists" Error is logged when renaming a Category to a name with a trailing space in the VFX Graph Blackboard
- Delete does nothing on an in-use Custom Attribute when re-triggered after cancelling the deletion confirmation prompt in the VFX Graph Blackboard
- No Ellipses are used for the Visual Effect Graph Create Context Menu Option
- Crash on LaunchBugReporter when opening a specific project using DirectX 12
Resolution Note (fix version 2023.1):
Upon closer look it was found that the interpolation logic does work in a consistent and correct manner. The problem is the implicit default global volume which is invisible and can result in surprising interpolations.
Issue fixed by setting the default value (also the value for the implicit default global value) of color lookup contribution to 0.