-
Notifications
You must be signed in to change notification settings - Fork 49
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
Edit Sprite metadata #9
Comments
The importer has a pivot field, but this will set the same pivot to all the sprites. You would like to edit the pivot for every single frame? |
Ideally yes, or at least on a per-animation basis. I can work around this enlarging the canvas in Aseprite. That results in the textures being a bit larger than necessary, though. I'm more concerned with generally editing the emitted assets. For example, it's impossible to add animation events or set sprite borders. I wonder if we can additively apply metadata to the assets without letting the user mess with the actual aseprite-defined values like animation timings or art. |
I'm currently working on this issue. A preview of this can be found on the sprite-importer branch: https://github.com/martinhodler/unity-aseprite-importer/tree/sprite-editor |
I've tried |
Problem
When generating sprites from the importer, I don't see any way to manipulate the pivot of the generated sprites.
Solution
I'd like to be able to edit sprite pivots the same way that unity enables for other image imports. Even if it's not possible to do visually it could at least be exposed as a Vector2 field.
Alternatives
Since the generated sprites and animations are read-only, I'm not sure if any alternative exists. (Maybe I could hack the meta file myself?)
Additional context
This is the sprite editor I'm referring to. It'd also be helpful to expose the other fields here also. I do occasionally use sprite borders or rename sprites, for instance.
By the way, I love this importer. Thanks for your work on it.
The text was updated successfully, but these errors were encountered: