Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.0.0-pre.4
Issue ID
DANB-480
Regression
No
Aseprite Sprite doesn't have the correct size when changing Import Mode to Sprite Sheet
How to reproduce:
1. Open the attached project “AsepriteBug”
2. Select the “SpriteTest” Asset
3. Change the Import Mode to the Sprite Sheet in the Inspector
4. Observe the size of the Sprite in the preview window
Expected result: The size is 16x16 and matches the original size of the Sprite
Actual result: The sprite becomes 32x32 and can’t be sliced properly
Reproducible with: 1.0.0-pre.4 (2021.3.25f1, 2022.2.20f1, 2023.1.0b16, 2023.2.0a14)
Couldn’t test with: 1.0.0-pre.1, 1.0.0-pre.3 (There is no Sprite Sheet Import Mode)
Reproducible on: Windows 11 Pro
Note: Also reproducible with the different sizes of the Sprite
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
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
Resolution Note:
We are adding a 4 pixel padding to every object, so they dont bleed into each other when we generate the sprite sheet. The sprite sheets are also always generated in power of two increments to support low end hardware.
The 4 pixel padding is something that we show in PSD Importer, and maybe something we should bring to the Aseprite Importer as well, so that users like yourself could bring down to 0 if you know you do not require that additional padding.