I found this bug when upgrading from Unity 2018.4.3f8 to Unity 2019.2.11f1
Some of our UI image goes wrong. So I investigate it more and found it’s actually a bug as below test result.
Look like the problem is under the “X” and “W” parameters in Sprite-Editor panel.
(When open the sprite to edit multiple sprites sheet )
For more information.
This issue effect to a sprite-sheet that reduce import file size 1 step. (e.g. The original PNG file is 2048x2048 but set import file size at 1024 )
If we kept the file import as it original size this issue wouldn’t occur.
This issue cannot be found in Unity 2018.4.3f1 with the same setting.
Just found the root cause.
Root cause is Unity 2018 and Unity 2019 handling “outline” attributes (in *.meta of the image) differently.
Below is an example of that part in *.meta that cause the issue.
spriteSheet:
serializedVersion: 2
sprites:
- serializedVersion: 2
name: micro_sprite_bug2
rect:
serializedVersion: 2
x: 450
y: 486
width: 3
height: 72
alignment: 0
pivot: {x: 0.5, y: 0.5}
border: {x: 0, y: 0, z: 0, w: 0}
outline:
- - {x: -1.5, y: 193.5}
- {x: -1.5, y: -193.5}
- {x: 1.5, y: -193.5}
- {x: 1.5, y: 193.5}
physicsShape: []
tessellationDetail: 0
bones: []
spriteID: 13e0226f057b6a340a6989cf956bd2a3
internalID: -2601321181383065041
vertices: []
indices:
edges: []
weights: []
- serializedVersion: 2
name: micro_sprites_notbug2
rect:
serializedVersion: 2
x: 450
y: 486
width: 3
height: 72
alignment: 0
pivot: {x: 0.5, y: 0.5}
border: {x: 0, y: 0, z: 0, w: 0}
outline: []
physicsShape: []
tessellationDetail: 0
bones: []
spriteID: 8e27e670726f8364991a146d7cf547e6
internalID: -7939585974763437787
vertices: []
indices:
edges: []
weights: []
Just come to update the bug report progress.
I raise this bug via Help menu in Unity Editor.
The progress come to conclusion at my previous post of this topic.
But the Unity staff from Customer QA Team that I dealing with, he asking for reproduce step (from new project) even I give them a small example project and with the easiest example like in my previous post.
And I refuse to do that because it definitely a Unity’s QA task to dig down until find the root cause after this point.
I won’t spend my effort (which is actually a man hour of my company) to work as a QA for Unity organization like that (or this is how they saving their QA cost?)
Then when I stop response to him even he know that this issue can happen to many user that migrate their project from older Unity version, even he had all information that I post in previous comment. He close the case LoL.
So that’s how Unity Engine had so many bugs left (and so on) as we see today.