@Mega1
Not sure if this is related but is a new Mac Air with the new M1 chip just bought less than a week ago
Could be that M1 is not supported with the Spine Plugin?
As for PhotoshopToSpine, it works on M1 Mac. (I use a Macbook Pro with the M1 chip.)
However, Illustrator to Spine has not been updated for about 4 years, so there is a possibility that we should update something for newer Illustrator versions. I'd like to make an issue ticket on github, so could you tell me what version of Illustrator you are using?

Also, have you tried to use PhotoshopToSpine via File - Scripts - Other Scripts - Choose jsx file?

---

@Kuro Kei
Thank you for your reporting, we reproduced the bug and I made an issue ticket for this problem:
https://github.com/EsotericSoftware/spine-editor/issues/608

However, if I delete the layer group that using [folder] tag, it can be exported. Also, the exported files can be imported to Spine Editor without any problem. Therefore, could you send us the PSD that the problem occurred via email ( contact@esotericsoftware.com)? We'd like to verify the PSD.

Misaki

• Posts: 769

Is there an export plug-in for Figma, similar to Photoshop to Spine script, Figma is an amazing design tool, I usually use it a lot .
kangpou
• Posts: 1

I'm afraid there's currently no such plugin. We are thinking about ways to make such plugin creation easier and more robust across a multitude of editing software. But that will take some time.

Mario

• Posts: 3091

Totally missed this thread, the new script does not apply Photoshop's adjustment layers on export like the previous version did. More details here http://esotericsoftware.com/forum/PhotoshopToSpine-script-does-not-apply-adjustment-layers-16606.

T.Fly()
• Posts: 16

Misaki wrote:As for PhotoshopToSpine, it works on M1 Mac. (I use a Macbook Pro with the M1 chip.)
However, Illustrator to Spine has not been updated for about 4 years, so there is a possibility that we should update something for newer Illustrator versions. I'd like to make an issue ticket on github, so could you tell me what version of Illustrator you are using?

Also, have you tried to use PhotoshopToSpine via File - Scripts - Other Scripts - Choose jsx file?
Hi @Misaki sorry for the late replay I don't get notifications from this forum when someone tags me

Hoh I see that explains why it doesn't work on illustrator

We use the latest version of Illustrator v26.0 it just came out

Also, for the Photoshop Spine plugging, it works perfectly with the latest photoshop version on the Mac M1 Chip
Though it has just a minor thing not sure if that is a bug or not but is not a big deal for us, is that if you open a project with one picture and the layer is locked and you try to export with the Spine plugin then it will show and error. To fix that you need to unlock the layer.
Is not a problem for us as it has an easy fix but I thought to let you know just in case.

Thank you very much for your help ))
Mega1
• Posts: 3

Hi, @Mega1
Thank you for your information, I'm glad to hear that you can run the script in the latest Photoshop!
However, I couldn’t reproduce the lock problem that you've reported to us. If you don’t mind, could you send us the PSD file via email? : contact@esotericsoftware.com

Regarding Illustrator, I’ve made an issue on GitHub according to your information :
https://github.com/EsotericSoftware/spine-editor/issues/611

Misaki

• Posts: 769

Hello,

I tried to use and debug the new script (v. 7.09) but I'm unable to run this successfully in both Photoshop 2020 (21.2.2) and Photoshop 2021 (22.0.0)...
The behavior is the same in both applications: Photoshop just crashes after clicking "Ok"/running the function "run".

I'm not aware of a way of using the AdobeExtendScriptToolkit debug functionality after the dialog appears so I used the old way of using alerts in multiple places of the script to see the behavior after running the "run" function. But it's being hard to see where exactly the problem is since I can run the script in the same PSD (I'm currently using a very simple PSD, which only contains a simple white layer and a color fill layer) two times and have a different behavior somehow (sometimes it triggers the alert that I put before the first definition of the "placeholders" variable and sometimes doesn't, for example.) I was even able to run it successfuly once or twice without Photoshop crashing.

I don't know if this helps in any way but I also have this warning: http://en.esotericsoftware.com/forum/Photoshop-to-Spine-Print-Error-14426

Is there a way for you guys to help me debug this or for me to help you guys try to figure out where the problem is?

Also, is there any way to make Photoshop work with Spine without the script?

Thank you so much,

Nigran
Nigran
• Posts: 2

Hi Nigran, sorry we missed your post! Photoshop crashing is unfortunately an Adobe problem. A script should never be able to crash their whole program. We'd be happy help find a workaround though. It sounds like you are on the right track to debug the problem. That it crashes in different places and even sometimes succeeds makes it extremely difficult to figure out.

Have you tried a simpler PSD? Just one layer, no color fill. Otherwise I'm not sure what else to try. You could try an older version of the script, like 6.13. You can try holding ctrl+alt+shift when starting Photoshop to reset all its the settings.

---

@Kuro Kei, we've fixed the problem you were having:
https://github.com/EsotericSoftware/spine-editor/issues/608

---

The latest Photoshop script has a new feature: an [overlay] tag! A layer with this tag is used as a clipping mask for all the layers below it. That means you can paint shadows/etc on an overlay layer and have them applied to all the layers below (only where there are pixels on those layers).

This was Nick's idea and he also has an alternative tool that can do it, so check that out here:
I made an ultimate export script alternative.

Nate

• Posts: 11946

Hi @Nate,

Thanks a lot for the reply and for trying to help!

I downloaded the 6.13 version and tried it, together with the version I already had (I saw in your comment that there's a new version now, I still need to try it) just to check it once again, and I'm glad to say that it somehow works nicely now! I don't know why since no version changed but that's great news, it never crashed again.

Below are the notes I have, it always had the same behaviour in both versions from what I have noticed:
• The images I have clipped to folders are exported as a full black image
• The error "The command 'Merge Layers' is not currently available" appears sometimes. When that happens I just need to manually merge the layers. It seems to only happen when a layer is clipped to another one

Both cases are fine since Spine, from what I know, is just to animate and I don't think that will be an issue since clipped layers usually happen for static images (in my experience at least.) I think that those things outside the animation itself are never to be made inside Spine. In any case the last version, with the "[Overlay]" tag, might help with that already.
(Please correct me if I said anything wrong)

TL;DR: It seems like I have no issues right now! Thank you and continue your great work

Best Regards,

Nigran
Nigran
• Posts: 2

We'll chalk it up as a mystery I guess! I'm glad it's working though.

Nate

• Posts: 11946

What contributes the most to the script execution speed? The CPU?
T.Fly()
• Posts: 16

Yes, it's mainly the CPU that determines the script execution speed. Also avoid network drives whenever possible.

You can try a bit of voodoo: run the script then minimize the window, or at least focus a different window so Photoshop is in the background. This can sometimes allow the script to run maybe 10% faster.

The problem with the script running quickly on any computer is Photoshop -- it's a giant piece of junk. The scripting works but is barely documented and the normal APIs provided are terribly slow. We rewrote the script using the lowest level APIs available and we came up with many tricks to gain a little speed here and there. It's still not fast, but it's as fast as Photoshop can be.

Nate

• Posts: 11946

Hello
this script is so handy. Really essential to work effectively.
I just notice that the [overlay] tag doesn't work properly with layers nested in [folder]>[slot]>[merge] folders. The background of the pngs should be transparent, and it's not. Other than that, it's perfect. (Photoshop CC2019, MacOSX)
Edit : it's random, sometimes it works, sometimes not.
Edit2 : works well when folders [folder] and [slot] are expanded in Photoshop.

Tomateche
• Posts: 34

@Tomateche Hello, thank you for reporting the issue. Unfortunately, I could not reproduce the issue you described. I created a PSD like this based on your report:
overlay-tag-test-psd.png

However, I was able to export it without any problems whether I expand or collapse the folders(groups).
attachmentA.png

I have attached the PSD here, so that you can see if this one can be exported without any problems:
overlay-tag-test.zip

We would appreciate it if you let us know what the differences are between this and your PSD.
You do not have the required permissions to view the files attached to this post.

Misaki

• Posts: 769

Hello Misaki
Well, the main difference is that my PSD contains more than 150 layers and multiple [slot] and [merge] folders in a single [folder] folder. (your .ZIP is empty)

---

What efficient advice would you give me if, after importing into Spine, I want to update or add some photoshop layers (in [slot]) and re-import them with the script? Should I export all layers again and only import changes/new into Spine?

Tomateche
• Posts: 34

Oh, I'm sorry that I missed to contain the psd into the zip file! I have tried to add two more sets of slots and attachments but still no problems. I have attached the psd as a zip file again so you can check it here.
overlay-tag-test.zip

What efficient advice would you give me if, after importing into Spine, I want to update or add some photoshop layers (in [slot]) and re-import them with the script? Should I export all layers again and only import changes/new into Spine?
It is not necessary to export all layers. You can export only the layers you want to export by hiding irrelevant layers and enabling Ignore hidden layers in PhotoshopToSpine. Spine provides the following options on the Import Data window:
Import - Spine User Guide: Import into an existing skeleton
import-data-existing.png

To replace existing attachments, check Replace, then click the Import button.
You do not have the required permissions to view the files attached to this post.

Misaki

• Posts: 769

Note you can also export everything from Photoshop, then when importing into Spine choose Ignore for Existing attachments. This way you don't have to hide things in Photoshop, but the export takes longer.

Nate

• Posts: 11946

Thanks for your replies Misaki and Nate,
when I export in two times, it works well. Probably my photoshop file which is too big, with too many layers. Or my computer, a little too old...

Tomateche
• Posts: 34

Hmm, if the problem occurs again, please let us know. Thank you for getting back to us!

Misaki

• Posts: 769

It looks like the script doesn't clear memory after it's finished running:

The memory remains taken until I close Photoshop entirely. After opening the file again the usage looks a bit more reasonable:

Photoshop: 22.5.6 (I couldn't run the script on the latest 23 version - something about an invalid layer name)
OS: Windows 10 Home
T.Fly()
• Posts: 16

Photoshop should not hold on to memory after the script completes. I'm afraid that is out of our control.

The script should run on the latest Photoshop. If you can provide the error you get, maybe we can fix it.

Nate

• Posts: 11946

Hello.
This script is perfect and make life easier...except for the choice for the path of json/images folder.
It would be handy to browse in our personnal folders than type the path.
Q: for now, how can I choose a folder that is located somewhere else on my hard drive than the location of the photoshop file (above the ./ default location)?
Thanks

Tomateche
• Posts: 34

You can put in the full path, eg C:\path\to\folder. I use a clipboard history tool that allows me to copy a file, then paste its path.

Nate

• Posts: 11946