Search Issue Tracker
Fixed in 2022.3.11f1
Fixed in 2022.2.X, 2022.3.X, 2023.3.X
Votes
1
Found in
2022.2.19f1
Issue ID
UUM-35591
Regression
No
_BlitScaleBias is 0,0,0,0 on custom fullscreen shader on FullScreenPassRendererFeature
If you open FrameDebugger and look at the FullScreenPassRendererFeature, _{}BlitScaleBias{} is 0,0,0,0.
Steps:
- Download and open attached project (URP_FullscreenShader-1.zip)
- Make sure SceneView is not opened
- Open SampleScene, observe GameView
See attached videos for repro.
Actual:
- GameView shows all white.
- In 2022.2.10f1, if you open SceneView and go back to GameView, the rendering is correct.
- In 2022.2.19f1, if you open SceneView, nothing happens, both SceneView and GameView still white
Expected:
- Without opening SceneView, GameView shows inverted skybox color with a cube
Reproducible:
2022.2.19f1 (still white even opening SceneView)
2022.2.10f1 (start to render correctly if opening SceneView)
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
Add comment