Cheemsandfriends
commented
1 year ago Idk if my input may be of help, but from my knowledge of Adobe Animate export:
Animate's spritesheet ignores the position of the symbol that may have on stage (if the spritesheet was exported on the stage, otherwise ig Animate would ignore this) and ignores the inline position of the shape stored in the symbol. This way, frame referencing the symbol's frame isn't unnecessarily big due to a convenient way to offset the animation it is currently displaying.
Also that the amount of animations that can be included in the spritesheet dont have any correlation at all, so if you make a person in idle mode and walking, these two wont care about one another, only the frames that make the whole animation of the walk for example will have frame offset correlation, sort of speak.
I may be wrong but this is what I believe this is the reason why Animate atlases (spritesheets) may need offset sometimes.
In March, we added frame offset modifiers for atlases, and I'm curious as to why they are needed. It seems like ASEprite atlases work fine, but Animate atlases have issues.
if you could provide FLA files that require code offsets, when exported, please provide them here. I'm trying to see if maybe we aren't parsing the files correctly, of - if adobe is fucking up - we can procedurally work around it. I don't think you can embed a fla in github comments so please either link to a file in a public repo, or use google drive so I'm not downloading suspicious zips.