Esoteric Software

[Erika]

We've created a new tutorial video to help you learn how to effectively use our Photoshop To Spine script, check it out!

[skarasuko]

Everything in the script seems to work in CS6 except for Ruler origin. Is there something I missed?

The result is everything being placed on the bottom right (default).

*Edit: Ah, I skipped that step where I had to drag from the top left corner of the ruler. Sorry.

[Nate]

Glad you figured it out! The guides are there because sometimes Photoshop can lose your ruler origin and without the guides it's difficult to place it exactly where it was.

[Mainstreet]

Can you give us some guidance on a recommended photoshop (or Krita which is what we use) layer structure? For example it seems like it might be something like

1. [skin] guy
   
   1. [bone] head
      
      1. [slot] neck
         
         1. nose
            
         2. eyes
            
         3. eyebrow
            
2. [skin] girl
   
   1. ... repeat of above ...

[skarasuko]

There is a problem in that set up, particularly the slot part. You cannot display more than one attachment in one slot.

[Mainstreet]

Basic Concepts

A slot can have any number of attachments, but only one attachment can be visible at any given time. A slot cannot have multiple attachments visible at the same time because the order those attachments are drawn would be undefined.

Presumably it just displays the first in line?

[Nate]

Spine would show the first attachment after you import the data, then you could choose which is visible, but only one attachment for a slot can be visible at any time. The thing is, you probably want to have the nose and eyes and eyebrow visible at the same time, so they should be in separate slots. You don't need to create a Photoshop group and use the [slot] tag unless you want multiple items in the same slot. If you just have a nose layer, the script will automatically create a slot called nose.

BTW, you don't have to put the tag at the beginning of the layer name. I like to put it at the end, eg guy [skin].

[Mainstreet]

Thanks Nate, yeah I like at the beginning.

How about this?

1. [skin] guy
   
   1. [bone] head
      
      1. nose
         
      2. hair
         
      3. eyebrow
         
      4. [slot] eye
         
         1. angry_eye
            
         2. happy_eye
            
         3. closed_eye
            
      
      
2. [skin] girl
   
   1. ... repeat of above ...

[Nate]

Looks good!

[Leesajohnson]

It is new for me. I will try to apply this option in Photoshop. Thank you to design a lovely video.

[Joncheen]

I keep getting an error that says: "Error importing skeleton, An error occurred while importing the skeleton. Please be sure to choose a valid skeleton JSON or binary file."
I've followed everything the video says about 10 times over now, any help would be greatly appreciated.

[Erika]

Hello, what version of the script are you using? with what version of Spine? My first thought is that there might be a mismatch causing this.

[Joncheen]

The spine version is 3.8.79, its the trial version.
The script is version 4.4.

[Erika]

Please update the script to the latest version as explained in the video, this should fix the issue (the latest is 4.7)

[Joncheen]

I'm sorry but I don't see anywhere in the video, the explanation of updating the script. Would it be difficult to just update the link to the latest version for the script?

---

Okay, so I saw that the script has been updated to 4.8, and that Spine has been updated to 3.8.82. I've downloaded both the new updates, and still for some reason I'm getting the same error message when I try to import the date from photoshop into spine.
I've also noticed that when I run the script in photoshop it's not turning any of the psd files into JSON files on my computer. It's storing all the images only as png.

[Nate]

We'll do that, thanks! Also here is a URL that will always give you the latest script file:
http://esotericsoftware.com/spine-scripts/PhotoshopToSpine.jsx

[Erika]

If the script didn't output a Json, what were you importing in Spine?

Make sure the script has the setting Write Spine JSON checked to ensure it will export a Json.
You can also check where the Json will be saved in the Json output path field.

[Nate]

I've also noticed that when I run the script in photoshop it's not turning any of the psd files into JSON files on my computer. It's storing all the images only as png.

Note that the script outputs one JSON file (if you have Write Spine JSON checked, as Erikari mentioned) and a number of PNG files (one per layer in your PSD). In Spine, you choose the JSON file to import, then you set the path under the Images node in the tree to where the PNG files are stored.

[Joncheen]

Yes I do have "Write Spine JSON" checked in the script setting.
On the script I can see the path for both the images folder and for the JSON file. I can find the images folder, but there's no sign of the JSON file.

Thank you so much for you guys help! btw

---

So yes just to sum it up after many tries. The script is just no producing a JSON file .

[Erika]

Just to be sure, the JSON should be saved outside of the images folder, at the path indicated in the script window, you checked the settings to export it, so if it's not there something may be interfering.

That sounds quite odd, could you screenshot your settings in photoshop? What OS are you using? Are you maybe saving this folder somewhere where your computer prevents the writing of certain files? A video or gif of the process would be very helpful.

[Joncheen]

So I finally did it! I got the script to make a JSON file and then imported it into spine!
Im not sure if it's a bug or this is what we're supposed to do every time, but the only way I got it to work was by clicking "save file as" in photoshop right before I ran the script.
By doing that the script recognised that the psd is in fact saved under a file name, and created a JSON under that file name.
Strange because I did'nt create a new name to save the file under, I just clicked the "save file as" button and then the computer made a new copy of it, as if the previous copy was'nt good enough. Heheheh

Well maybe im just computer stupid, or maybe the computer is stupid. But either way Im very happy that it works now, and i couldnt have done it without your guys guidance pointing me in the direction to look.

Thank You!

[Enzy]

Hello, I was curious if there is a layer limit to this script? I have been trying to run it in my Photoshop file and it's doing something. A JSON is made as well as an image folder but it doesn't export images and the JSON is basically blank. I tried running it on a different Photoshop file and it worked as intended. the only thing i can think of is there is either an error in my naming set up or there are just to many layers and it's timing out or something. I'm working with a character that has multiple skins which is why the layers are so high. I could potentially export out each skin separately i supposed but figured i would ask here first. Thanks!

[Erika]

Hello! There shouldn't be a layer limit, but perhaps there might be a tag or a layer style that it's slowing down/freezing the script?
If you want you can send us the file at contact@esotericsoftware.com to check, otherwise you can nail down what the cause is by deleting half of the layers (for example deleting halpf of the skin folders) and see in which half the problem happens. Then repeat until you find the culprit.
Or you can just export a subset of skins then import the rest later as you suggested

[Moetal]

Hello, is it possible for you to send me the version of the PhotoshopToSpine script before the 2/3 update? I am suspecting something in the latest script update broke compatibility with Photoshop CS2 since the previous script worked for me while the latest one does not.

[Erika]

Hello, you can find all script versions here: History for photoshop/PhotoshopToSpine.jsx - EsotericSoftware/spine-scripts

Find one you want to try, click on the last button of the row (which looks like this: < > , then go back in the photoshop folder and save the file as the tutorial shows.