Search Issue Tracker
In Progress
Fixed in 2022.3.11f1, 2023.3.0a3
Won't Fix in 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)
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (2023.2.X):
Closing as Won't fix due to 2023.2 reaching it's EOL.