Search Issue Tracker
Active
Under Consideration for 6000.2.X
Votes
1
Found in
2022.3.63f1
6000.0.51f1
6000.1.8f1
6000.2.0b6
Issue ID
UUM-109311
Regression
No
Wrong opacity of a transparent Material when Render Queue is set lower than 2501
Reproduction steps:
1. Open the attached “DepthShadow6000“ project
2. Open the “DepthShadowDemo“ Scene
3. In the Game View, observe the “Plane“ GameObject
Expected result: The “Plane” GameObject is transparent
Actual result: The GameObject is opaque
Reproducible with: 2022.3.63f1, 6000.0.51f1, 6000.1.8f1, 6000.2.0b6
Reproducible on: macOS Sequoia 15.5 (M1 Max), Windows 11
Not reproducible on: No other environments tested
Workaround: In the “DecalCatcher” Material options, set the Render Queue to 2501 or more
Comments (1)
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
DevDunk
Jul 01, 2025 07:34
This is required to be fixed for a new Unity Asset