Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2019.3.15f1
2020.2
Issue ID
1254179
Regression
No
Sprite is packed inefficiently when using Tight Packing in the Sprite Atlas
How to reproduce:
1. Open the user's attached project
2. In the Project Window, select the Sprite Atlas (Assets > Sprites)
3. In the Inspector Window, click "Pack Preview"
4. Observe the packed Sprite Atlas
Expected result: Sprites are packed efficiently
Actual result: Some of the Sprites are packed inefficiently
Reproducible with: 2018.4.23f1, 2019.4.1f1, 2020.1.0b13, 2020.2.0a15
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (2020.2.X):
To ensure that packing does not take a long time (especially for larger projects and we also need to support Playmode), there are certain trade-offs and it may not always be possible to achieve most efficient packing especially for edge cases.