Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.2.X
Votes
5
Found in
2019.4.12f1
2019.4.13f1
2020.1.0a15
2020.2
2021.1
Issue ID
1287864
Regression
Yes
Tiling and Offset values have no influnce on the image when using a Material with UI Shaders
How to reproduce:
1. Open the user's attached "TESTOFFSET" project
2. Open the Scene "SampleScene"
3. In the Hierarchy select the "Image" GameObject (a child of the "Canvas" GameObject)
4. Expand the TestMaterial Component and change the Offset variable
Expected results: The image on the "Image" GameObject in the Scene view becomes offset
Actual results: The image on the "Image" GameObject in the Scene view does not move at all
Reproducible with: 2019.4.12f1, 2019.4.14f1, 2020.1.0a15, 2020.1.13f1, 2020.2.0b11, 2021.1.0a5
Not reproducible with: 2018.4.28f1, 2019.4.11f1, 2020.1.0a1, 2020.1.0a14
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 (fix version 2021.1):
Fixed in 2021.1.0a8
Resolution Note (fix version 2020.2):
Fixed in 2020.2.2f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.18f1