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
- 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