Spine 4.2 imports PSDs directly, no Photoshop scripts needed
Spine PSD importer problem:
When a layer doesn't have a name, the spine considers its name to be incorrect and takes the name of its hierarchy.
Basically in affinity designer every form and curve have by default no name.
If i do (layer representation)
-[merge]spine
--------<rectangle> (no name)
--------<curve>
Spine say the "layer name is not a valid attachment name"
Because it process the name despite the [merge] tag
the forum seem bugged cant upload anything so i give a link of screenshot
https://mega.nz/folder/p6I2GAhT#016n5YURkACPkKqfAz_bcA
Awesome, straight from Clip studio will remove a whole step for me
Hey, have you re-modified the import script ?
From 4.2.26 to other the "/" in layer name doesnt work anymore for the skin folder.
[skin:chara/skin1]layer doesn't create sub-folder it only concatenate in spine a skin name
So [skin:chara/skin1] give charaskin1 for the skin name.
The [folder:x] tag doesn't seem to be working too.
Have a nice day
Hi valahaha,
Yes, we did some improvement to the PSD script and as you have noticed we worked on some name sanitization.
That is definitely the cause of the regression you reported about skins.
We enforced that skin names cannot contains "/", but in psd tags they actually can since the part before the "/" might represent the folders in which is contained.
We'll fix it in the next beta release.
Regarding the [folder:x] tag not working.
Can you provide an example of hierarchy in which the tag doesn't work. It seems to work on my side.
Thanks again for your collaboration
I have noticed when I export to psd using Krita the alpha inheritance (it acts like a mask) doesn't work. I tested it and this happens. Could this ever be fixed somehow without me needing to create a copy of the original file with all the layers merged? This isn't the best workflow because whenever I have to change something I need to create a new copy and re-merge everything. Or maybe is there a place in the roadmap to accept krita files as well?
eli_stergiouli
Thanks for reporting this.
Unfortunately Krita doesn't seem to export into the psd file the information about alpha inheritance.
If you open the psd using Photoshop or Krita itself, you'll notice that the information about alpha inheritance is lost.
We'll try to open an issue about that on kryta github since currently it's a problem on their side.
Regarding supporting directly kryta files, that will be difficult, but we're thinking about other file formats like ora and tiff.
Exporting in ora using Krita seems to preserve alpha inheritance.
There's not really such a thing as "features PSD supports". PSD supports ALL features of Photoshop. There are things Photoshop does that are unreasonable for other software reading a PSD to do, like linked PSDs, rasterizing vector, applying fancy filters, etc. Only a subset can reasonably be supported, and even then it's nasty because it's proprietary. Most apps just write pixel data to PSD and ignore everything else. PSD is popular, but it isn't good.
Yes, TIFF and/or ORA could be better interchange formats.
Davide a few days ago when I tried to export another project of mine to .ora and open it with gimp the alpha inheritance was lost. Maybe it was gimp's fault? Did you test it with another software? If Spine where to accept .ora files I would be very happy! Do you think this will be implemented in the future?
- 已编辑
eli_stergiouli
Gimp seems to have limited support for .ora unfortunately.
We're focusing on stabilizing physics, skin folders and PSD processing, and currently we have no particular plan on supporting new file formats. We just had a thought about it.
Regarding alpha inheritance not exported in PSD as a clipping mask I saw on Krita issue tracker that there are issues opened since 2015/2016 and they are silent. That's not good news. Maybe you can try to give a +1 on those issues.
I can understand how frustrating it can be to copy and merge everything. Maybe we can add a [clip]
tag to treat the layer as a clipping mask, but that would be very specific to Krita.
We'll think about it and see what we can do. If something reasonable can be done to support your use case, we'll let you know. ️