Search Issue Tracker
Fixed
Fixed in 2022.3.69f1, 6000.0.61f1, 6000.2.10f1, 6000.3.0b8, 6000.4.0a3
Votes
3
Found in
2022.3.67f2
6000.0.59f1
6000.2.7f1
6000.3.0b4
6000.4.0a1
Issue ID
UUM-121056
Regression
Yes
Incorrect color values are saved for Swatches when using HDR Color Picker
Reproduction steps:
1. Open the attached “IN-118429.zip” project
2. Open the “SampleScene”
3. From the Hierarchy, select the “HDR” GameObject
4. In the Inspector, click on the “Hdr Color” color bar to open the HDR Color window
5. Choose any bright color for better visibility
6. Save the color as a Swatch (click on the Add New Preset button)
7. Select the same saved Swatch
8. Observe the color
Expected result: The color value does not change
Actual result: The color value changes
Reproducible with: 6000.0.36f1, 6000.0.59f1, 6000.2.7f1, 6000.3.0b4, 6000.4.0a1
Not reproducible with: 6000.0.35f1
Reproducible on: Windows 11
Not reproducible on: no other environments tested
Notes:
- The more Swatches are created from the same color, the whiter/more washed out it becomes, eventually sometimes just turning white completely
- Does not reproduce with non-HDR color picker
Comments (2)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
unity_DQp3A9yKqAUEyA
Oct 27, 2025 05:44
Reproducible with: 2022.3.62f2
Reproducible on: Windows 11
Please consider patching this in 2022.3.X current stable. Thank you.
ysalmi
Oct 07, 2025 19:21
Original reporter here, please consider patching this in 6000.2.X current stable. Thank you.