Search Issue Tracker
Fixed
Fixed in 6000.0.53f1, 6000.1.11f1, 6000.2.0b9, 6000.3.0a2
Votes
0
Found in
6000.0.51f1
6000.1.8f1
6000.2.0b6
6000.3.0a1
Issue ID
UUM-109463
Regression
No
Game view fails to render and becomes dark when the Screen Space Lens Flare Component's intensity is set to 1 and the Bloom Mip Bias is set to 0.
How to reproduce:
1. Open the “CustomRP“ project
2. Open the “SampleScene“
3. Navigate to the Default Volume Profile Asset (Assets → Settings → DefaultVolumeProfile)
4. In the Inspector, set the Screen Space Lens Flare intensity to a value greater than 0
5. Set the Bloom Mip Bias to 0
6. Observe the Game view
Expected result: The selected settings are applied and visible in the Game view
Actual result: The Game view becomes dark, and numerous errors are displayed in the Console (full errors are provided in the Notes section)
Reproducible with: 6000.0.51f1, 6000.1.8f1, 6000.2.0b6
Could not test with: 2022.3.63f1 (Screen Space Lens Flare feature is missing)
Reproducible on: Windows 10, Windows 11 (user’s)
Not reproducible on: no other environment tested
Notes:
- Render Graph Execution error
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)
- InvalidOperationException: Trying to write a resource twice in a pass. You can only write the same resource once within a pass (pass Blit Lens Flare Screen Space resource_BloomMipUp0).
UnityEngine.Rendering.RenderGraphModule.RenderGraphBuilders.ValidateWriteTo (UnityEngine.Rendering.RenderGraphModule.ResourceHandle& handle)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment