Search Issue Tracker
By Design
Votes
0
Found in
6000.0.54f1
Issue ID
UUM-111654
Regression
No
SpriteRenderer has wrong input color when associated material uses SRPBatcher
How to reproduce
1. Extract and open the attached “IN-107982.zip” project
2. Observe the Game View
Expected result: All squares are coloured
Actual result: Only non-SRP squares are coloured
Reproducible with:
6000.0.54f1
Could not test with: 2023.3.0b10, 6000.1.12f1, 6000.2.0b10, 6000.3.0a2 (Shaders used are highly customized, upgrading and downgrading causes unfixable compilation errors)
Reproducible on: MacOS 15.5 (Silicon)
, Windows 11
Not reproducible on: No other environment tested
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
For 2D Renderers in URP, if SRP-Batcher is active, Color is in unity_SpriteColor (UnityPerDraw) and Vertex Color is White
If SRP-Batcher is inactive or Shader is not SRP-Batcher compatible, Dynamic_Batching is used. unity_SpriteColor is white and color is now in Vertex Color
To fix the shaders, please use an appropriate function to get the Sprite Color.