• Editor

  • Good workflow for photoshop 2 Spine?

    영어

Hey quick quesiton on how y'all would approach this

Say you're creating animations in spine which are fed trough photoshop exported with the plugin so it would be e.g.

[skin] Bob
-[bone] face

eyes

nose
-[bone]chest

[skin] Sally
-[bone] face

eyes

nose
-[bone]chest

Etc
But now the art director wants a new skin, "I want skin David, which also has 3 eyes instead of 2 and an extra jacket bone"

Would you edit the same psd and export out just the new character with the new bone data and asset info?
Would you manually import all the new assets to spine and adjust the assets there?
I guess I'm asking mainly because unless I'm missing something the photoshop 2 Spine flow is only good for initial setup, because if you need to make any adjustments it would create a brand new json on export so in spine if you import it you'd lose all your animation data you already had after importing the previous one right? Or am I forgetting something obvious

Trying to think of a good way to do a workflow which lets me make changes to the psd and i dont needto manually re import all the assets in spine and readjust thus defeating the purspose of the script. If anyone has any suggestions let me know!

Thank you!

Related Discussions
...

Hi lucky! (ah, nice nickname 😃 )
If you haven't already, have a look at this video first, which goes over the basics:

Once done, let's go over the workflow of adding a new skin. It's actually really easy!
You can choose to keep everything in the same file, then export with the script, and import new data in Photoshop:
Import - Spine User Guide: Data

Image removed due to the lack of support for HTTPS. | Show Anyway

As you can see from the above screenshot, you can choose to import in the same skeleton! And if you choose to ignore the existing attachments, You'll get all the new slots under the root, the new images of the new skins in the correct slots, and the old images with their nice meshes and whatnot left unharmed.

If you plan to add multiple skins in the future, it doesn't really make a difference to keep everything in the same file or spread across multiple files, so for the sake of making the script run faster to export only the new images, you can have a new file to store the new images in as well 😃

This feature was introduced in version 3.8 so if you didn't know about it this may be why! Please let me know if anything requires further clarification.