Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

1.2.16.2 frame numbering bug #2198

Closed
muldjord opened this issue Nov 22, 2019 · 3 comments
Closed

1.2.16.2 frame numbering bug #2198

muldjord opened this issue Nov 22, 2019 · 3 comments
Assignees
Milestone

Comments

@muldjord
Copy link

@muldjord muldjord commented Nov 22, 2019

Aseprite 1.2.16.2

With this version the "Default first frame" number is ignored. I always have the first frame as "0". After updating it is always "1" even though I've set it to "0". This used to work so it seems to be a regression in the newer versions.

Running on Windows 10 x64 through Steam version

@muldjord

This comment has been minimized.

Copy link
Author

@muldjord muldjord commented Nov 22, 2019

Did a bit more digging. It works when starting a new project, but not when I load a week old project. Seems to be no way to align the frames of loaded projects so it matches with the "Default first frame" number of "0" I've set.

@dacap dacap self-assigned this Nov 22, 2019
@dacap dacap added this to the v1.x-bugs milestone Nov 22, 2019
@dacap

This comment has been minimized.

Copy link
Member

@dacap dacap commented Nov 22, 2019

Thanks for reporting this @muldjord, I was going to put this bug report too but you are the same author. We'll try to fix it ASAP.

@muldjord

This comment has been minimized.

Copy link
Author

@muldjord muldjord commented Nov 22, 2019

Thank you! I appreciate it

@dacap dacap closed this in 6cab7b2 Dec 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.