• Bugs

  • Spine fails to import multiple skin data from Photosho .json

    anglais
Related Discussions
...

In Photoshop, I was working on updating multiple art assets for a couple of my skins in Spine. When I export both skins at the same time onto the .json and import that data into Spine, one skin will update correctly and the other will not and art assets seem to 'explode'/offset from their original origin point.

Steps to Repro:
1) Choose two skins that you want to export together in Photoshop
2) Once those skins are active and all other skins and layers are hidden, run the Photoshop to Spine export script
3) Once Photoshop is done, open up Spine and set one of the skins you updated to be active
4) Reimport the the .json and choose to replace assets.
5) Once that is done, the current skin you're on should import correctly
6) Now activate the second skin you exported from Photoshop and reimported at the same time as the first skin. You should see art assets off their original rotation point and be offset to the left and right of the character. If you redo the steps above with this second skin active, the assets will correctly fix themselves. However, if you then switch to the other skin that you first imported, those assets are now offset.

I did however find a work around and that involves exporting one skin at a time and importing one skin at a time into Spine.
Steps to Repro:
1) Deactivate all the skins you want to export except for one.
2) Once that skin is active and all others are inactive, run the Photoshop to Spine export script.
3) When that is done, open Spine and activate the skin you want to update.
4) Reimport the .json and replace assets.
5) That skin should be updated correctly.
6) Save and close Spine and repeat steps 1-4 for all skins you want to update.

Is this a bug or am I missing a step/setting somewhere when I want to import and update multiple skin assets at the same time?

Software:
Spine 3.8.87
Photoshop CC

Hello Cathy,

I tried your steps, but could not reproduce the error with the info you've given me. Could you please add this info?

  • What version of the script are you running? I suggest using the latest just in case. spine-scripts/photoshop at master · EsotericSoftware/spine-scripts
  • If you used the latest version of the script, did you get this same problem?
  • What were your export settings from Photoshop? Could you post a screenshot? (I have a feeling that Trim whitespace might be the culprit here but I can't be sure.)
  • When you export your updated image assets, do you export them in your Spine project's images folder or copy them later?
  • When you write "Reimport" at point 4 you are actually importing the Json for the first time, right?

I'll try again to repro once you give me more information. If I won't succeed, I will have to ask you to send us a reproduction project (PSD + problematic project and images) to our email at contact@esotericsoftware.com

Hey Erika!

I updated to the latest script and are still getting the same results. 🙁 Here is some more info you asked for:

  • I am running PhotoshopToSpine v4.9
    -
    -When I export my image assets out of photoshop, I export them directly into Spine's image folder. The folder Spine looks into to grab all assets that are mentioned in the .json file.
    -No, I am reimporting the same .json when ever I need to update images and/or add new images to my spine file.

Thanks!
-Cathy

Hello Cathy, I have been using the same settings, so I am afraid I will need a repro project. Please send us a reproduction project (PSD + problematic project and images) to our email at contact@esotericsoftware.com mentioning this thread.

Hey Erika, Will do! Thanks! 🙂