Search Issue Tracker
By Design
Votes
6
Found in
2020.3.48f1
2021.3.25f1
2022.2.19f1
2023.1.0b14
2023.2.0a13
Issue ID
UUM-35141
Regression
No
Rendering artifacts when using Depth Mask shader in WebGL
How to reproduce:
1. Open the attached project "DepthMaskTest.zip"
2. Build And Run the project for WebGL Development Build
Expected results: No rendering artifacts in the WebGL Player
Actual results: Rendering artifacts seen in the WebGL Player
Reproducible with: 2020.3.48f1, 2021.3.25f1, 2022.2.19f1, 2023.1.0b14, 2023.2.0a13
Could not test with: 2023.2.0a14 (the Player hangs in the browser)
Reproducible on: Windows 10
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
- Inconsistent behaviour when interacting with different dropdown types with pointer events on parent Visual Element
- Hidden GameObjects won't re-enable when they have call "DontDestroyOnLoad" function
- Overlay Canvas are rendered on each split-screen camera when HDR is enabled
- [Android] The Player loses focus when using UnityEngine.Handheld.StartActivityIndicator() with Facebook SDK
- Build fails with "Building Library/Bee/artifacts/MacStandalonePlayerBuildProgram/gahcy/hj9mx3z/951.0 failed with output:..." errors when Scripting Backend is set to IL2CPP
Resolution Note:
By design: project's use of depth masking depends on strict objects rendering order. In this case the object rendering order is:
"Capsule","DepthMask",everything else.
Color buffer values withing the depth masked region are not initialized, because no other object passes ZTest, and the "Capsule" within is filling only a part of the masked area. So the remaining area within depth masked region remains uninitialized, and the values are undefined behaviour depending on GPU/drivers/devices.