I found that the animation clip will copy the asesprite first frame as its last frame.
but when I have a transform meta layer, the last frame missing transform meta data.
I think if the last frame is the same as the first, the meta layer must automatic added as first frame.

here is my screenshot:

the result of missing transform meta layer of last frame, I got a weird behaviors , the transform curve not the correctly in the run mode, but seem ok in preview mode.

in preview mode:

editor scene or game scene

在aseprite中画的碰撞盒位置：

未使用@pivot时unity生成的碰撞盒位置：

使用@pivot时unity生成的碰撞盒位置：

导入设置:

看了源码，初步认为是MetaLayerBoxCollider代码中
var pivot = Vector2.Scale(ctx.settings.PivotRelativePos, new Vector2(ctx.file.width, ctx.file.height));
的PivotRelativePos值是customPivot的值，而不是MetaLayerPivot最后生成的Pivot的值。但我对程序基本一窍不通，不知道分析的是否正确。

Maybe use some rule like asmdef file (all files in a folder follows one setting)
or sprite atlas (both folder and single .ase can be selected in a list)

but anyways, current scheme of storing all settings reference in a global place is definetely bad

带位移的动画,特别是跳跃这种,因为跳起来以后下方的空白像素被去除了,所以工具生成的atlash中动画是不对的,只有单张导出整个canvas的时候,动画才和软件中表现一致,不知道这个问题作者怎么规避的,还有就是对texturepacker的支持, 暂时只能自己改一套了

It is not very satisfying to have to store file configs under a global folder. It is prefably placed in MetaSprite/Config folder for each project.

Some user might want to move MetaSprite folder somewhere else than Plugins folder, so we need means to detect where the plugin is placed.

So I can't figure out how to use @BoxCollider from the wiki...

Can anyone give me a more in-depth walk through or better yet a working example file I could look at?

Thank you for your time.

Hi, when generating the atlas each frame seems to have some random number for the x and y values of the pivot, I tried setting bottom center and custom (0.5, 0) but I still get different numbers for each frame.

Would it be possible to get some advice on how to extend the functionality of this so that I can create clips and atlases for every layer per tag in my .ase file?

I've loved this Aseprite importer and it solve most of my problem with the adition of a few I didn't have.
Unfortunatelly, my project has a very fine pixel tuned animation based on root motion. So, I would need to add transformation to the root motion translating the pivot position change into the animation. I have no problem in doing this as a last pass on the animation. However, if I try to add the translation on the imported animations it starts to behave oddly changing the sprite in some of the keyframes for the animation.
Is there anyway to set that in aseprite or add it later somehow?
If you could guide me through the code, I may be able to write this transformation based on the pivot change in a given loop myself.

There are (much) better packing algorithms other than shelf packing, such as skyline, subdividing etc. We can achieve higher space efficiency by optimizing atlas packing algorithm.

Shelve packing algorithm is vastly inefficient in texture space.
It's straightfowardly better to use a greedy large-to-small packing algorithm. We shall compare the difference before/after the algorithm change.

So, I have multiple tags for my walk cycle, like up, down, left and so on, they are not in the same place in the aesprite canvas, I think this results in this:

Later version of unity now provide a method of associating secondary textures with a sprite atlas. This can be used for normal maps, emissive maps, or even arbitrarily named texture bindings in a Shader Graph. More info can be found here.

I'm interested in adding support for these to MetaSprite, but I have a few questions regarding how to best do so.

I think adding a @secondary("binding name") meta directive would be a good approach. Each of these layers could written as a separate texture asset and then associated with the main atlas as a secondary texture with the provided binding name.

A few questions though:

1. Would it be best to provide two directives @secondary("Name") and @secondary-target("Name", "binding name") similar to sub images so that multiple layers could be combined into one secondary atlas? Was that the motivation behind using two in the case of sub images (I don't use this feature)?
2. I imagine it would be necessary to support secondary textures on sub images as well. What would be a good syntax for this?
3. MetaSprite will need to write secondary textures as separate assets. I see that sub-images already require this functionality and that I should be able to reuse part of that atlas serialization code. Is this correct? The sprite packing in the secondary texture needs to be exactly the same as the primary atlas. Is that possible?

Finally, thanks for the great importer!