Texture Packer and Automator

Texture Packer has a command line tool, which means that you can run it as a shell script in Automator. This means that you can get sprites from the Automator and automatically build spritesheets using them.

Why would I want to do this? Why can’t i just use Texture Packer with all its lovely GUI?

Because well for me, I process the sprites first using Automator, before I pack them into spritesheets. Also this is a quick way to not set all the different Texture Packer settings each time (yes, I know you can use Save Defaults for settings).

But double-clicking on my Automator app, and then select my sprites, and wait for it (it’s actually pretty quick) to automagically spit out spritesheets is still faster (and it only requires like 2 to 3 clicks), and it even supports multipack (in case the sprites doesn’t fit in just one spritesheet)

This is my (partial) Automator workflow:

Screen Shot 2014-05-08 at 11.31.15 AM
Screen Shot 2014-05-08 at 11.31.45 AM

A big shout out and thank you to Andreas Lowe for replying to all questions on Twitter, and helping me whip out that Shell Script.

This Automator app requires the Pro version of Texture Packer as well.

That’s it!

 

Sorry for not posting anything since creating this new blog in January, that’s because I temporarily moved back home (hello, Manila).

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s