Search Issue Tracker
Won't Fix
Won't Fix in 2022.3.X
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
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!
Resolution Note (2022.3.X):
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!