Search Issue Tracker
By Design
By Design in 2023.3.X
Votes
0
Found in
2022.3.12f1
2023.1.18f1
2023.2.0b15
2023.3.0a11
Issue ID
UUM-54334
Regression
No
GameObjects are not transparent in the Player when using a Shader with transparency
How to reproduce:
1. Build And Run the user’s attached “TranslucencyTest.zip” project
2. Observe the result
Expected result: Some GameObjects are transparent
Actual result: None of the GameObjects are transparent
Reproducible with: 2022.3.12f1, 2023.1.18f1, 2023.2.0b15, 2023.3.0a11
Could not test with: 2021.3.31f1 (transparency wasn’t working in the Editor)
Reproduced on:
macOS 13.5.2 (Intel)
Windows 11
VLNQA00358 - iPhone 12, 14.1 iOS
VLNQA00335, Samsung Galaxy S20+ 5G (SM-G986B), Android 10, CPU: Exynos 990, GPU: Mali-G77
Not reproducible on: No other environment tested
Note: not reproducible in the Editor
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 problem was solved by setting alpha values for both "_Alpha" and "_Color" in the shader
Resolution Note (2023.3.X):
This problem was solved by setting alpha values for both "_Alpha" and "_Color" in the shader