Search Issue Tracker
Won't Fix
Won't Fix in 6000.0.X
Votes
0
Found in
6000.0.20f1
Issue ID
UUM-84764
Regression
No
Scene is not rendered and appears black when the Custom Renderer Feature is utilized
How to reproduce:
1. Open the “URPBlurTest“ project
2. Open the “SampleScene“
3. Click on the PC_Renderer to open its Inspector (Assets → Setting → PC_Renderer)
4. In the Inspector, enable the Blur Renderer Feature
5. Observe the Game view
Expected result: Two cubes, blue and red, are visible and blurred
Actual result: Only black screen is visible
Reproducible in: 6000.0.20f1
Not reproducible in: 6000.0.23f1
Fixed in: 6000.0.21f1
Could not test with: 2021.3.45f1. 2022.3.50f1 (The Blur Renderer Feature is missing)
Reproducible on: Windows 10, Windows 11 (user’s)
Not reproducible on: No other environment tested
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:
Already fixed in 6000.0.23f1.
Resolution Note (6000.0.X):
Already fixed in 6000.0.23f1.