Slice tool creates many (around (100+)) slices at once

I am attempting to use the Slice tool to create frame by frame collider data on my animations, and export to JSON.

The Slice tool seems to be designed so that slices initially persist across all frames, while being able to move around in the other frames. So if I have a 2 frame anim and do a slice in the first frame, the subsequent changes in the first frame persist in the second.

However, if I then make changes in the second frame, the boxes get “desynched” to allow for moving slices. I assume this is an intended feature. The problem comes when deleting a slice; Aseprite tries to “resync” the slices, but something goes wrong in that process. This generates a corrupted slice that cannot be moved around; instead, click and drag seems to start creating hundreds of invisible slices on top of each other. Those slices are duplicated across all frames, smothering the entire file with slices that (as far as I know) can only be deleted by right-clicking. :cry:

My workaround for now is “don’t delete slices”. I tried breaking the slice tool with no deletions and was luckily, unsuccessful. But I live in fear :confounded:

I am on version 1.2.8 Windows 64 bit (Steam version). Here is a GIF showing how to reproduce:

(New member so I can’t post my other GIF, but basically it generates a huge JSON file haha)

I’m aware that this tool might not be of the utmost priority on the development path of Aseprite, and while a complete fix would be incredibly useful for me personally moving forward, at the moment at least having a “delete all slices” option would ensure that files can wiped clean in case of a disaster. Or maybe I’m dumb for not seeing the obvious workaround that fixes everything. :upside_down_face:

Thanks for taking the time to look through this issue! I ADORE Aseprite and recommend it to every artist I know! You rock!!! :smile:



I’ll take a look to this issue.

1 Like

I’m seeing the same or similar behavior on 1.2.32-x64.
Multiple actions seem to trigger creation of invisible duplicate slices

  • Create a slice in one frame, then select another frame
  • Moving a slice created on a different frame also triggers it
  • As @RayTeX described, when trying to move a corrupted slice which can’t move, it creates hundreds of duplicates. I saw this even without first trying to delete a slice.
  • If frames are deleted, the slices still reference deleted frames in the exported JSON file

It’s not clear what the all the conditions are that cause duplication and corruption since there is no visibility into the state of slices (even a basic list of existing slices would be helpful).

Has any investigation been made into this? it’s nearly unusable for my intended workflow as it is.

Probably related to #3122 and the fix that will appear in the next release v1.2.34.

Anyway there are plans to include slices in the timeline, but nothing done yet.