Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.10f1
Issue ID
UUM-49333
Regression
No
_BlitScaleBias is not set when using a custom shader
How to reproduce:
1. Open the attached “TrueBlitterBug.zip“ project
2. Open the “SampleScene“ Scene
3. Observe the Game view
Expected result: GameObjects are visible
Actual result: The Game view is dark
Reproducible with: 2022.3.10f1
Couldn’t test with: 2021.3.30f1, 2023.1.14f1, 2023.2.0b10, 2023.3.0a6 (“UniversalRenderer is missing RendererFeatures“ error in the Console)
Reproducible on: macOS 13.4.1 Ventura (Intel)
Not reproducible on: No other environment tested
Notes:
- Issue reproducible in Player
- _BlitMipLevel is set and _BlitScaleBias is not set, so UV calculation using _BlitScaleBias cannot be performed correctly
- Setting Shader.SetGlobalVector() values to “"_BlitScaleBias", new Vector4(1f,1f,0f,0f)“ minimally solves the issue
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:
We are unable to repro the issue with the latest 2022.3 version.
If the issue is still happening, please re-open this bug and add your current Unity version.
Thanks!