Search Issue Tracker
Duplicate
Votes
7
Found in
2019.1.0a5
2019.1.0b8
2019.2
2019.3
Issue ID
1148483
Regression
Yes
Modifying "Image.sprite" of an existing Image, deforms it
Reproduction steps:
1. Open "IconRendering.zip" project
2. Enter Play mode
3. Wait until some Images are instantiated
4. Notice that some Images are deformed compared to the other ones
Expected Result: Images that have their "sprite" field modified, should not look different
Reproduced with: 2019.3.0a1, 2019.2.0a13, 2019.1.0f2, 2019.1.0b1, 2019.1.0a5
Did not reproduce on: 2019.1.0a4, 2019.1.0a3, 2019.1.0a2, 2019.1.0a1, 2018.3.14f1, 2017.4.26f1
Comments (3)
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
DezBoyle
Oct 20, 2019 21:36
duplicate of what?
ol1ph4nt
May 17, 2019 18:20
Having the same issue here and still happening on 2019.1.3f1.
What is this a duplicate of and when can we expect a fix?
LVermeulen
May 04, 2019 20:54
What is this a duplicate of?!? We are having this issue and now can't track it