Cranktrain

I have a Spine skeleton that has a number of slots and skin placeholders, and lots of skins. Whenever I add a new skin to the skeleton, I have a few dozen new images to drag into the new skin, which means I have to:

1. Find the next slot I need an image for.
2. Scroll all the way down to images.
3. Find the specific image.
4. Click-and-drag the image, scrolling aaaall the way back up to the skeleton and release into the slot (that I have to find again).
5. Repeat 50 times.

The scrolling and searching is getting really, really tiresome.

Being able to have multiple Trees, one scrolled down to 'Images', and one scrolled up to the Skeleton itself would let me just drag and drop, left to right, and be done in a few minutes.

Is this or some other workflow available?
Аватара пользователя
Cranktrain
  • Сообщения: 58

Erikari

Hi! what if I told you you don't need to do this tiresome procedure as of Spine 3.8? Simply import the new json in the existing skeleton, and Spine will automatically add the new skin and populate the correct slots as long as the same nomenclature is used:
Import - Spine User Guide: Data
Аватара пользователя
Erikari

Erikari
  • Сообщения: 2009

Cranktrain

Erikari писал(а):Hi! what if I told you you don't need to do this tiresome procedure as of Spine 3.8?
I'd be very happy! And gladly upgrade my game to Spine 3.8 if so.

But first I need to check specifically what you mean when you say:
Erikari писал(а):Simply import the new json in the existing skeleton, and Spine will automatically add the new skin and populate the correct slots as long as the same nomenclature is used:
Import - Spine User Guide: Data
So what you're saying is that in Spine 3.8, using 'Import Data' into the existing skeleton means that if I have images in a file like this:

ExistingSkin/Head.png
ExistingSkin/Body.png
ExistingSkin/Weapon.png

And I add a new skin, then as long as I have named these images the same way but in their own folder:

BrandNewSkin/Head.png
BrandNewSkin/Body.png
BrandNewSkin/Weapon.png

Then wherever the original ExistingSkin/Head.png and so on are found in the existing skeleton, a new skin will place the BrandNewSkin/* variants in all the same slots/skin-placeholders... while also leaving all the ExistingSkin images positions/scales/hierarchy-positions all the same?

^ Because that's exactly what I'm after.
Аватара пользователя
Cranktrain
  • Сообщения: 58

Erikari

Well, it's not about the image as much as it is about populating the correct slot and then checking for the skin placeholder.
It will work this way and put images inside the correct slot, (I suggest specifying the slot by using the [slot] tag in photoshop) as long as the slot names match. Huge time saver! Test it out :D
(and make sure to have the up-to-date version of the script!)
spine-scripts/photoshop at master · EsotericSoftware/spine-scripts

You can see it in action briefly in the 3.8 features tour video here: Spine 3.8 features rundown - YouTube
Аватара пользователя
Erikari

Erikari
  • Сообщения: 2009


Вернуться в Editor