このサイトを正しく表示するには、最新のブラウザを使用し、Javascriptを有効化してください。

Adding new skins to spine

Katarina Cz

Hello,
has something changed with adding a new skin in the new updated version of Spine ? We are constantly adding new skins to an existing document.

The way we did it:

run the script in photoshop
in spine: import data
choose to import .json to the existing skeleton
and new skin was created

Now we are doing the same thing but it behaves differently. It does not create new skin. It basically adds the new attachments to existing skin and it deletes some slots if I tick "replace" existing attachment.

My question is: How I add a new skin to the existing Spine document?

Thank you.
katarina

Erika

Hello, if you want to add new skin to the document and you don't want your existing images to be changed in the other skins, choose Ignore instead of Replace.

It is also important that the new skin doesn't have a name that matches other skins, or it will be detected as being the same skin by the script, which is what I suspect may have happened.

I tested the process of importing new skins in Spine and it worked fine for me on the latest Spine version. If you still encounter problems please send a zip that allows us to reproduce the problem you are experiencing to contact@esotericsoftware.com mentioning this topic.

Katarina Cz

Hey, I see what has happened.
We have two separated photoshop documents with "heads" and with "body characters". We exported the skins with the same skin naming, e.g. cartographer [skin] from heads and cartographer [skin] from body character folder....means all attachments are in the same folder.

So I guess this is the issue. Although the json scripts ("cha_cartographer_skin_pieces" and "heads") have different naming and also the skins naming in spine is different, "cartographer" and "face_cartographer" but comes from the same folder in Spine "cartographer". I assumed that they cannot be imported into the same folder, with the same naming?

Thank you.

Erika

New skins that share the same folder with the same naming in your Spine images folder will overwrite each other because that's how operating systems work. (you can't have two files with an identical name in the same folder on Windows).
The name of the json file shouldn't matter as much as the name of the skins in the files.

I hope you did figure out what is causing the issue, but in case you need further assistance you can email us the project + jsons + images pointing out which skins get an unwanted result from import to contact@esotericsoftware.com mentioning this thread, so I can have a deeper look at it.