Search Issue Tracker
Active
Fixed in 2022.3.11f1, 2023.3.0a3
Under Consideration for 2023.2.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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment