Search Issue Tracker
Fixed in 2020.3.44f1, 2021.3.15f1, 2022.2.0f1, 2023.1.0a14
Colors majorly change when the Volume Component's "Weight" property value changes from 0 to any small value
# 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)
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- The terrain appears darker when "Per-pixel Normal" is enabled
- [Linux] Editor assertion causes Test Runner to fail when executing it in Batch Mode
- Color selection by the mouse cursor is still enabled when the "Esc" button is pressed
- Game view becomes black and the Scene window becomes grey, “ArgumentOutOfRangeException” errors and “Render Pipeline error” warnings appear after changing the name or deleting URP/HDRP global settings file
- Transform Component is not accessible inside the Player when RuntimeInitializeOnLoadMethod is used
Resolution Note (fix version 2023.1.0a14):
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.