Search Issue Tracker
By Design
By Design in 2023.1.X
Votes
1
Found in
2021.3.26f1
2022.3.0f1
2023.1.0b19
Issue ID
UUM-37112
Regression
No
[WebGL] Blit with Custom Shader is not rendered in Player
Reproduction steps:
1. Open the attached “WebGL_URP_CustomShaderBugDemo.zip“ project
2. Change platform to WebGL
3. Build And Run the project
4. Observe the Player window
Expected result: All images are rendered
Actual result: Images under “Blit with custom shader“ are not rendered
Reproducible with: 12.1.11 (2021.3.26f1), 14.0.7 (2022.3.0f1), 15.0.5 (2023.1.0b19)
Could not test with: 16.0.1 (2023.2.0a17) (Errors in the Console)
Reproduced on: Windows 10
Not reproduced on: macOS Ventura 13.3.1 (Intel)
Notes:
- Could not test with HDRP (Broken Shaders)
- Not reproducible with Standalone Player
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
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
- Icon section shows incomplete message and unusable check box in Build Profiles and Player Settings window instead of “Not applicable for this platform” for Dedicated Server Platform
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
Resolution Note:
By design: Custom shader used for blit does not specify ZTest Always, therefore is uses ZTest Lequal. The render texture is not cleared before blit, so the depth buffer values are undefined, and the blit simply fails ztest depending on the render texture contents.
Resolution Note (2023.1.X):
By design: Custom shader used for blit does not specify ZTest Always, therefore is uses ZTest Lequal. The render texture is not cleared before blit, so the depth buffer values are undefined, and the blit simply fails ztest depending on the render texture contents.