Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.0.0
Issue ID
1198142
Regression
No
Images that support transparency are not sliced accurately when slicing Type is set to Automatic in Sprite Editor
How to reproduce:
1. Open user's attached '1198142-Automatic-Slicing.zip' project
2. Select Assets -> Textures -> spritesheet
3. Open Sprite Editor in the Inspector
4. Select Slice dropdown and click Slice button
Expected result: "" and "-" signs are sliced into separate sprites
Actual result: "" and "-" signs are sliced into one sprite
Reproducible with: 2017.4.35f1, 2018.4.13f1, 2019.2.14f1 (1.0.0), 2019.3.0f1 (1.0.0), 2020.1.0a14 (1.0.0)
Notes:
- 2017.4, 2018.4 Sprite Editor is not included in the package
- Reproducible with PNG, PSD image formats
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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Resolution Note:
The Sprite Editor attempts to automatically slice and locate Sprites with a minimum threshold size of at least 4 pixels. This is to ensure that small artifacts in the texture (less than 4 pixels in size) will not result in unwarranted Sprites being created.
For this issue, the minus sign Sprite is less than the minimum threshold required for automated slicing. This causes it to be grouped up with the prior plus sign Sprite. To adjust this, please manually create the Sprites for both the plus and minus sign in the Sprite Editor after slicing the other Sprites.