#Texturepacker export png install
#Texturepacker export png update
#Texturepacker export png skin

If all has gone correctly, you should now have something like this in the folder with the JSON: IMPORTANT! Make sure that the atlas name you give is the same as the name you gave the JSON file on export. You can now click on the Pack button to create your texture pages and atlas file (note that you can click the Settings button first if you want to set the texture page size, or any other things related to the final texture page output). The Input Folder should point to where you have your base images saved (as explained at the top of this article), while the Output Folder should point to the location of the exported JSON file. To open the Texture Packer, go to the Spine menu (click the top left in Spine) and select Texture Packer. Take note of the export location, as weВЎll be directing the texture packer to that location now.

When exporting, it is important to note that we only want the JSON file, and not any textures, so make sure that the Pack option is unchecked: tps in GUI or command line and use it over.

#Texturepacker export png install

5-minute setup: Install command line client and integrate TexturePacker into your build easily. The next thing to do is open Spine and export the sprite that want to use these images for the texture (we'll pack them in a moment). PNG Portable network graphics TGA Targa Image File JPG Joint Photographic Experts Group TIFF Tagged image file format BMP Bitmap. Tools like TexturePacker add an option to pre-multiply with black automatically for png export, btw. This type of premultiplication is often done by the programmer during runtime - but depending on the tools (and developer you may have to do it yourself. Voila, a premultiplied anti-aliased version. In the case of our Spine goblin, we'd have something like this: Now delete the original, and save as a png. To correctly create texture pages in this way, you first need to have your base images stored with a folder structure that permits them to be interpreted as different texture pages.

#Texturepacker export png skin

It has a male skin, a female skin and attachments, and you'd want each of these skins to have their own texture page. An example we'll use in the images below is the Spine 'Goblin'. However, it is often the case that you will want your texture pages ordered in a specific way so that the images are stored in a logical order and don't create too many texture swaps with one sprite having to swap between two texture pages to be drawn correctly. NOTE: Spine texture pages are specific to that Spine spriteВ and pages cannot be shared between different sprites or any other assets in a GameMaker Studio 2 project. In general, all this means for you is that when you import a Spine JSON file that has 2 or more texture pages, then GameMaker Studio 2 will automatically detect this and add all of them as part of the sprite data, and then you can switch skins as normal in your project, even if the skins are on different texture pages.

#Texturepacker export png update

With the 2.2.2 update to GameMaker Studio 2, general Spine support was improved and as part of that you can now import Spine sprites with multiple texture pages.