Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.0.0
Issue ID
DANB-497
Regression
No
Aseprite Importer generates a wrong size and offset Texture 2D
How to reproduce:
1. Open the user-attached project “Bug Report Aseprite Importer”
2. Expand the “Stone Floor Tiles Import Settings” Asset in the Project window
3. Observe the “Stone Floor Tiles” Texture 2D
Expected result: The Texture 2D matches the size of the original Sprite
Actual result: The Texture 2D is bigger than the original Sprite and has an offset
Reproducible with: 1.0.0 (2021.3.27f1, 2022.3.3f1, 2023.1.1f1, 2023.2.0a21)
Reproducible on: Windows 11 Pro
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
- Inspector elements are rendered twice when the script component is added via drag-and-drop while the HideFlags.HideInInspector property is set
- Error "Light baking failed with error code 5 (Convergence data not available while rendering lightmaps)" thrown in Console when generating lighting for specific GameObjects
- Copy and Paste options for an Animation Property value are disabled in the Right click contextual menu
- Asset is not found when searching the Label "NewLabel" in Search Window
- "Compute dispatch: missing texture ID..." and "Compute dispatch: missing UAV ID..." warnings are thrown after changing the platform in High Definition 3D template
Resolution Note:
Hello!
Thank you for reporting this issue to us.
I had a look at the report, and what you are seeing is expected behaviour. When we generate the texture inside of Unity, we add two things:
- A 4 pixel padding between every item. This is to prevent pixel bleeding between Sprites.
- Size the texture up to a power of two size (rounding upwards). This is to account for lower end hardware, which require all textures to be in a power of two format.
Since the result is expected, we will close this bug as “Won’t fix“. However, I have also logged your feedback in our Aseprite Importer backlog, so that we can consider it in future package versions.
Thanks again for reporting the issue, and do let us know if you have any future issues or suggestions on how we can improve the Unity editor and runtime.
Happy developing!
Kind regards,
Ted Wikman
Senior Software Engineer, Gameplay
Unity Technologies