Search Issue Tracker
By Design
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
This problem was solved by setting alpha values for both "_Alpha" and "_Color" in the shader