Search Issue Tracker
By Design
Votes
0
Found in
2022.3.59f1
6000.0.41f1
6000.1.0b9
6000.2.0a6
Issue ID
UUM-99143
Regression
No
Incorrect opacity blending occurs when parent opacity is applied
Reproduction steps:
1. Open the attached “IN-95493” project
2. Open the “Scenes/SampleScene” Scene
3. Observe the “UIDocument” GameObject in the Game View
Expected result: The whole content is firstly merged into 1 texture and then the opacity of that texture is lowered
Actual result: Each child element will have its opacity individually adjusted
Reproducible with: 2022.3.59f1, 6000.0.41f1, 6000.1.0b9, 6000.2.0a6
Reproducible on: Windows 10, Windows 11 (user)
Not reproducible on: No other environments tested
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
Resolution Note:
This is by design. Each element applies its own opacity. We are planning to release a new feature (CSS Filters) that will help with this use case.