Search Issue Tracker
By Design
Votes
0
Found in
6000.1.0b12
6000.2.0a8
Issue ID
UUM-101122
Regression
Yes
Pivot in Sprite Editor is not applied when using Aseprite asset with Tile Set import mode
Steps to reproduce:
- Open the attached project
- Select TestSprite asset and open Sprite Editor
- Select one of the Sprites
- Change the Pivot point
- Apply the changes
Actual results: Pivot point change is not applied and it returns to the custom state
Expected results: Pivot point change is applied
Reproducible with package version: 1.2.3
Not reproducible with package versions: 1.2.1, 1.2.2
Reproducible with versions: 6000.1.0b12, 6000.2.0a8(0ac7dd760774)
Not reproducible with versions: 6000.1.0b11(c7b7080a3879), 6000.2.0a1, 6000.2.0a7
Can’t test with versions: 2022.3.60f1, 6000.0.44f1 (Tile Set import mode for aseprite files is not available)
Tested on (OS): Ubuntu 24.04, macOS 15.3.2
Notes:
- Package-related regression introduced with 2D Aseprite Importer 1.2.3
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:
The Import Mode: Tile Set is there to bridge the gap between Aseprite file content and Unity's Tilemap system. The tile data coming from Aseprite is placed exactly the same way in a Tile Palette as they are in Aseprite, so there is no reason to change the pivot in Unity.