Skip to content

Fix slices issues preferring just one slice keyframe#5580

Merged
dacap merged 2 commits into
aseprite:betafrom
dacap:fix-slices
Dec 9, 2025
Merged

Fix slices issues preferring just one slice keyframe#5580
dacap merged 2 commits into
aseprite:betafrom
dacap:fix-slices

Conversation

@dacap

@dacap dacap commented Dec 9, 2025

Copy link
Copy Markdown
Member

Avoids the creation of new slice keyframes by default, which is a confusing behavior (at least until we don't have a proper animated slice support).

Anyway we should probably forget the idea of animated slices, and leave that for hitbox layers (#5347). It makes more sense to have static slices (a "fixed portion of the sprite to be exported").

Fix #2284, fix #5125, fix #5578

dacap added 2 commits December 9, 2025 17:34
Added a new option to go back to the old behavior (creating new key
slices per frame), but we'll try to keep just one slice key.
@dacap dacap self-assigned this Dec 9, 2025
@dacap dacap changed the title Fix slices issues to prefer just one slice keyframe Fix slices issues preferring just one slice keyframe Dec 9, 2025
@aseprite-bot

Copy link
Copy Markdown
Collaborator

clang-tidy review says "All clean, LGTM! 👍"

@dacap dacap merged commit 054ccda into aseprite:beta Dec 9, 2025
12 checks passed
@dacap dacap deleted the fix-slices branch December 9, 2025 21:45
@npinochet npinochet mentioned this pull request Dec 22, 2025
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Selecting a slice flags the file as modified Slices behave weirdly over the multiple frames Slices get corrupted when edited before their frame

2 participants