Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

everytime i record it will crash the whole aseprite app and my recent work wont show up on the recent view

Sorry to hear that things aren’t going so well. I’ll try to help in any way I can but cannot guarantee I’m able to figure out a solution.

What version of Aseprite are you running? Are you using the most recent version of this plugin? Do you have any other plugins/extensions running? If you are using the automatic snapshot functionality, what interval are you recording at? How big is the file you are working on?

Aseprite v1.2.34.1 x64 interval is 3 and the files are mostly 64pixel 

Please try the most recent version of the plugin, the changes introduced may have resolved your issues.

It worked thank you so much!

(+2)

I made a fork today that:

- Fixed crashes with Selection Tool + Move Tool

- Removed the annoying popup save dialog

- Defaulted snapshot interval to 1 (instead of 3)

- Nicer output file names

https://github.com/thomaseding/aseprite-record

Feel free to yank some/all of the new content from this and bring it into the main project.

I also wrote a post processor that will collapse sequences of identical output files. It will also rename things in proper order, letting you hand-delete bad recorded frames (such as an accidental paint fill). It's still pretty rough on the edges (wrote it today), so I don't have a link for it up yet.

Oh wow, that’s quite an update. I’ll give it a read through and let you know if I pull it back into the main project.

Just a heads up, I’ve pulled in your updates to the project with a minor tweak to maintain compatibility with existing snapshot files & added documentation for a migration path for anyone who may try to use the update with said existing snapshot.

Awesome. Sorry for the C-like Lua... I've never read or written Lua before and couldn't be bothered to read a tutorial :)


Also it looks like you beat me to a backward compatibility shim. Perhaps we should shove the version number into a metadata file such as  `foo__record/_version.txt`.

No worries about the C-like Lua, I hadn’t really written any Lua prior to this extension so a lot of it was learned on the fly.

I did managed to squeeze out the compatibility shim, I think it’ll resolve any possible issues that may arise.

Regarding a version file, I don’t imagine it’ll be necessary as I tend to aim to keep things backwards compatible - and based on the nature of the utility I would figure people won’t tend to go back to previous snapshots once they’re done with their piece. Something to think about though, like tracking more meta data if necessary.