> sprite sheet with cropped frames is literally only a few kb larger then one that does not.
> That depends on how your graphics are created. E.g. if you have a character that is dodging and attacking with a sword it might be a *big* difference if frames are cropped or not.
Then you would save some memory and the sword (possibly with arm too) on it own image. This would be for a large sword anyway. As there would definitely be a large amount of transparent image if it was all in one.
> exture Packer creates bloated pngs
> Currently the file size is about 15% bigger then when using opting. This will be fixed with the 3.0.0 release.
Sometimes even higher but can then be loaded and saved out of another program to reduce.
> lso, never have your character or object change positions in your sprite sheet, per frames. Any change in position should be done by code or game editor function.
> You have several cases with animations where this is exactly not what you want to do. You want to keep the anchor point steady while the animation moves around it...You have to be kidding me? Animating by code will save more space then within frames. Anything can be animated in a frame but x/y coordinates, zooming, rotating, and so forth is much better by code.
I see what you're both trying to say here. I think it's a common mistake to try to move an object using animations, and it most often wont work. But if you have, say, a little power up that orbits around your character yet is purely an effect (it doesn't shoot or shield damage or anything), then it's better to move it via animations, for instance:
<img src="http://media.giantbomb.com/uploads/0/1264/199592-son2_32_super.gif" border="0" />
the little balls rotating around robotnik (dr. eggman for some of you) are best implemented as animations, not as actually changing positions via code.