Search Issue Tracker
By Design
Votes
0
Found in [Package]
7.1.8
Issue ID
1237767
Regression
No
[URP] Bloom appears much brighter in Scene View compared to Game View
When rotating the directional light in Scene View or moving the camera around the bloom also flickers a lot. There are no changes to the effect when moving the light/camera in Game View.
To repro:
- download this small project
- open the Watershadersample scene
- notice the bloom is very poweful in scen view and is colouring the whole screen yellow
- in game Veiw, notice that the bloom looks ok.
Repoducible in 2020.1, 2020.2 and 2019.3
with URP: 7.1.8, 7.3.0, 8.0.1 and 9.0.1
Cannot test with 19.2 or earlier versions, as this particular project that reproduces the glitch cannot be opened in earlier versions.
Note! Cannot reproduce this when adding this user-made unity package to a new project made with the URP Template. This only reproduces when importing it to a new 3D project that's had the URP package added to it after the fact.
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:
There are 2 issues in this report:
(1) Bloom appears in sceneView but not gameView
This is because on RenderPipeline asset, user need to enable HDR checkbox.
(2) The weird yellow fullscreen color in sceneView
This is because in user's shader graph, the "Texture is active" has the negative value, and that negative value arrives output Albedo. Negative color values in render targets will have unexpected behavior, which is expected.