Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.3
2020.3.14f1
2021.1
2021.2
2022.1
Issue ID
1368927
Regression
No
Color transformation values behaves differently after performing arithmetic operations
How to reproduce it:
1. Open the attached project "New Unity Project (5).zip"
2. Load the "SampleScene"
3. Enter the Play Mode
4. Observe the Console logs
Expected results: "Integer1: 70" and "Integer2: 70" messages appear
Actual results: "Integer1: 70" and "Integer2: 69" messages appear
Reproducible with: 2019.4.31f1, 2020.3.20f1, 2021.1.24f1, 2021.2.0b14, 2022.1.0a12
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
Expected behaviour due to precision difference between constant folding (compile time) and actual multiplication (runtime)