Search Issue Tracker
By Design
Votes
0
Found in [Package]
6.9.0, 7.1.1
Issue ID
1183326
Regression
No
Scene and Game windows turn black when GameObject with custom shader graph is rendered and 'Bloom' is enabled
How to reproduce:
1. Open the attached 'Scene View Test.zip' project
2. In the Hierarchy window select 'Environment'
3. Drag the mouse over the Scene window and press 'f'
Expected result: scene window does not turn black
Actual result: scene window turns black
Reproducible with: 2019.2.7f1 (6.9.0, 6.9.1), 2019.3.0b4, 2020.1.0a5 (7.0.1, 7.1.1)
Could not test with: 2017.4.32f1, 2018.4.9f1 due to project & shader graph errors
Note: reproduced only with the provided custom shader and 'Bloom' has to enabled in 'default_rendering_settings_profile'
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Resolution Note:
The reason why the window turns black when the custom shader graph is rendered is that the shader produces a NaN value and bloom spreads it.