Search Issue Tracker
Active
Under Consideration for 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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on GameObject::QueryComponentByType when opening a project
- "Object reference not set to an instance of an object" is thrown when destroying a GameObject with a Camera Component
- [Android] The error message "OPENGL NATIVE PLUG-IN ERROR: GL_OUT_OF_MEMORY:" is thrown when the video is playing
- [IL2CPP] Build fails with the error "[1mcannot convert 'Nullable_1_tEA06D91799914C5C8830F83CE2A8395868C14F02' to 'int32_t' (aka 'int') without a conversion operator" when IL2CPP is used as the Scripting Backend
- Rigidbody interpolation is performed after the next frame's FixedUpdate() when using Rigidbody2D
Add comment