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

Feature Request: Exporting Animation Sheets/Sequences #14

Open
Brian151 opened this issue Sep 29, 2015 · 2 comments
Open

Feature Request: Exporting Animation Sheets/Sequences #14

Brian151 opened this issue Sep 29, 2015 · 2 comments

Comments

@Brian151
Copy link

gif exporting is only really useful for preview purposes, at best, and the color limitations of .gif also can essentially, destroy certain sprites...so even its preview capabilities are limited!

This program is pretty nice, but some more export options really are needed...badly.
Not all engines or developers are going to support, or be willing to support the format this program uses, and you really should consider that.

Right now, I cannot do anything useful with my animations.

@darkFunction
Copy link
Owner

It exports as XML which you are free to convert to another format, or use directly in your game engine. The gif export is simply bonus functionality.

If you care to support other engines it's either a matter of updating the program to output the format or simply converting from XML, which is potentially the easier solution.

I appreciate this is frustrating but this is open source software provided completely for free and developed on my own time, I simply do not have the time or resources to support many different engine formats. Pull requests are very welcome!

@Brian151
Copy link
Author

the problem is besides parsing the XML, the parts then need to be rotated and such...
Generally if someone wants to create an animation sheet for their animation, they want nothing to do with the code required to do so. (especially when it involves manipulating a bunch of smaller images)
They might even lack that kind of experience...

animation sheets can be supported by nearly any engine, and the code to parse one is much, much easier to write than the code to parse and animate animations saved in your formats.

Seeing as you already have a live preview (that even scales/pans at user's whim, having your program export whatever is currently being rendered to a png image sequence or single png sprite sheet really shouldn't be that hard...

I understand this, but this is no small issue to be having with animating software. This is the kind of thing that almost certainly guarantees it would fail as a commercial product. Not to be threatening or rude, but yeah... unless the code, in the format/language they're using is already present for them to just import/copy/whatever , most developers are going to choose another option before they even consider using yet another file/data format. Even WITH that code just handed to them, they may still look for other solutions.

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

No branches or pull requests

2 participants