Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
1
Found in
2019.3.0a11
2020.1.0a1
2020.1.0a3
Issue ID
1182374
Regression
No
[UIR] UIElements Runtime - Colors are too light in the Game View in linear color space
How to reproduce:
1. Open the attached 'Builder.zip' project
2. Open 'SampleScene' Scene
3. Drag NewUI.uss from Project Browser to VisualAssetTree field in Builder's Viewport Window
4. Enter Play Mode
Expected result: Play Mode's color match the color in the UI Builder
Actual result: Play Mode's color is lighter than the color displayed in UI Builder
This only happens in linear color space.
Reproducible with: 2019.3.0b4 (UI Builder 0.7.0), 2020.1.0a5 (UI Builder 0.7.0)
Could not test: 2017.4.32f1, 2019.4.9f1 package is not introduced, 2019.2.7f1, 2019.3.0a10 and earlier due to errors
Comments (2)
-
GuillaumeLeplang
Dec 19, 2019 19:33
Also present in UIBuilder 0.10.0-preview
-
GuillaumeLeplang
Dec 19, 2019 19:24
I just noticed a similar issue (Unity 2019.3.0f1 / UIBuilder 0.9.0-preview)
I added a white pixel, with a tint :
-unity-background-image-tint-color: rgb(93, 34, 128);But on my side, it's lighter in the inspector and at runtime than in UIBuilder.
Actually, the color is correct in UIBuilder (I tested those values in Photoshop to see the difference)
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
- Diagnostics logs are missing, duplicated, or out of order when viewing Player sessions in Cloud Diagnostics
- Prefab Overrides “Apply” button is too big and overlaps with the context menu’s outline
- Prefab Overrides “No Overrides” text is too large, and the the Context Menu of the Parent GameObject has a lot of empty space when opened
- “Screen position out of view frustum...” errors are thrown when zooming out in the Scene view after creating UI GameObject
- CurveTexture is not being released when unloading AssetBundle containing a Scene with ColorCurves post-processing component in Global Volume
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a24
Resolution Note (fix version 2019.3):
Fixed in: 2019.3.7f1