Following tutorials online, I need to set up my Spine file with multiple skins on one rig, but the only way I can get the JSON import from photoshop to Spine to work is if the images for each part is in the root of the photoshop files, when I run the script, the JSON and all the parts are in a folder together. Obviously this wont work for skins since the skins need to be separated in some way.
If I use [skin] or [folder] in the photoshop file, then when I import, its not importing the art onto the stage in the correct positions, I can drag it from the tree onto the stage and manually position it, but its not ideal.
Can someone tell me where I'm messing up here.
To set up multiple skins in Spine using JSON import from Photoshop, ensure that your images are organized correctly in Photoshop. Use the [skin] tag to define different skins, and ensure that the layer names match across skins to reuse the same skin placeholder. When using the PhotoshopToSpine script, the images should be in subfolders corresponding to each skin, and the script should generate JSON and images that Spine can import. If the images are not positioned correctly, check that the images path in Spine matches the folder structure used in Photoshop. You can also manually adjust the images path in Spine if needed. For more detailed guidance, refer to the Spine User Guide on Image file lookup.
If I use [skin] or [folder] in the photoshop file, then when I import, its not importing the art onto the stage in the correct positions, I can drag it from the tree onto the stage and manually position it, but its not ideal.
This part sounds strange. Normally, the [skin] tag would be perfect for your purpose.
If you don't mind, could you send us your PSD file via email?: contact@esotericsoftware.com
Please include the URL of this forum thread in the email so we know the context. Then we can take a look at what's wrong.
NEV Thank you for sending us the PSB file! Since the file was a bit complex, I was unable to address all layers, but I have sent you a revised version via email with the groups and hierarchy corrected.
I'm not entirely sure if this was the issue you were facing, but placing a [folder] tag below a [skin] tag caused the attachment names to change. As a result, separate skin placeholders were created for each skin. This behavior is generally undesirable when using skins to switch appearances, as it would require you to manually change the attachments via animation or code in order to display the correct look.
If you want to organize image folders using a different hierarchy, I recommend specifying the path using only the [skin] tag. For example, writing [skin]A/B will save all layers in the B subfolder within the A folder. However, please note that this structure will also be reflected in the skin hierarchy within the Spine editor.
Additionally, you have consistently used the [slot] tag to define which slot each layer belongs to. However, when using the [skin] tag, layers with the same name under different skins are automatically grouped under the same slot. Therefore, unless you specifically need each attachment to have a unique name, the [slot] tag is generally unnecessary.
As for placement, there were no guide lines to indicate the origin. If you'd like the origin to be positioned at the character's feet, you can place a crosshair guide at that location, and then drag the canvas so that the crosshair aligns with the top-left corner of the ruler. This will set that point as (X:0, Y:0). This process is explained in the following video:
If you have any questions or issues, please feel free to ask.
Thanks for looking at it, but the issue still exists, even with your corrected PSD, when I import to Spine from the JSON from this new PSD, it still leaves me with an empty stage
I'm using the most recent Photoshop, Spine and PhotoshoptoSpine script too, totally stumped why the JSON isn't working as it should. Like I said there's no problem importing when its just the JSON in the same folder with the parts, but I need the skins to work
Just noticed there's a PSD import option so decided to try that and it worked no problem, there might be an issue with the script!
Thanks for your help!
NEV You just need to enable the skin. Once enabled, it should display correctly.:
You can use PSD import, but the script still works!
Chargement…
Une erreur est survenue lors du chargement de la version complète de ce site. Veuillez vider le cache de votre navigateur et rafraîchir cette page pour tenter de corriger cette erreur.