Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2018.3.9f1
Issue ID
1142694
Regression
No
Converting RGB value to HSV and back to RGB returns wrong values
How to reproduce:
1. Open attached Unity project
2. Load scene "SampleScene"
3. Enter the Play mode
4. Notice Assertion failure in the Console window
Expected result: Converted 'b' value is 168. Assertion failure should not appear.
Actual result: Value before converting is 168. After converting to HSV and then back to RGB it changes to 167.
Reproduce with: 2019.2.0a10, 2019.1.0b10, 2018.3.12f1, 2017.4.25f1.
Notes:
This issue occurs with some specific values:
RGBA(0, 255, 168, 255): b value is converted to 167
RGBA(0, 168, 255, 255): g value is converted to 167
RGBA(0, 255, 169, 255): b value is converted to 168
Converting works properly with these values:
RGBA(0, 255, 167, 255)
RGBA(0, 167, 167, 255)
RGBA(0, 168, 168, 255)
RGBA(255, 168, 0, 255)
RGBA(0, 255, 170, 255)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment