• Announcements

  • Spine 4.2 imports PSDs directly, no Photoshop scripts needed

valahaha
The problem you reported has been fixed with the latest beta.
Thanks again for reporting this problem and let us know if there's some other malfunctions importing PSD generated by Affinity Designer 😃

      Related Discussions
      ...

      Davide

      Nice it work well
      Thanks for the amazing opportunities to use this my workflow at best💓

        Davide

        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

            valahaha

            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 🙂

                Davide

                Yes, that just im happy to report thing that doesnt work in my project.



                    valahaha

                    Ok, I see. It's folder in combinatino with skins.
                    Currently the skin tag is always prepended, then folder is applied, regardless order in the PSD.
                    While in the photoshop script this does respect the order.

                    Thanks again and we'll try to fix this too in the next release 👍️

                      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?

                      test.zip
                      657kB

                        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.

                            Davide Having open standards available would be amazing. Really not a fan of import being based only on a proprietary standard, which FOSS software has to reverse engineer so there always will be issues around that.

                                T.Fly()
                                Like importing TIFFs as well?
                                Are there any open formats that support the same features that PSD does?

                                  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. 👍️

                                          你好，关于原点，我想说说我的想法。
                                          希望原点图层除了包括[origin]的命名规则外，我认为以这个图层的左上角第一个像素作为原点会好一些，原因是：
                                          1）无需手动去寻找中心在哪。
                                          2）我可以画一个方框，这个方框的左上角为原点，右下角为画布的角落，用绘图软件中的Ctrl + T 来检查这个如此是否被移动过，以此判断原点是否正确。如果是图层中心为原点，则不容易被检查出来

                                          关于直接导入PSD相关的功能，我还有一个小小的建议。希望能有一些命令可以让图层不会导入到spine中，例如带有“[no]” 命令的 图层 或 图层组 都不会被导入到spine，这样可以节省很多“删除不必要内容”的时间，同时又可以在PSD文件中留下这些内容。（这些内容可能是备用的，也可能有其他用途）

                                            toven

                                            You can already ignore layers or entire groups using the [ignore] tag.

                                            Currently, the origin is set using the first X and Y guides found in the PSD or in the center of the canvas if guides are missing. Unfortunately, not all software that exports in PSD format stores guides in the file.
                                            This is why we were considering adding support for an [origin] tag. When we implement it, we will take your suggestions into consideration.

                                              To use the center of a layer for the origin, I expected someone to draw an X, so the center of the X is the origin.

                                              Davide It would be amazing if you could include a [clip] tag in the future! I hope someday you have some time to do that. thanks for trying to help!

                                                  habahu 我明白了，谢谢你的解答，能否改进一下psd导入功能，比如增加一个自动合并剪贴蒙版的选项。

                                                  This has been implemented v4-2-38-beta.
                                                  Now clipping masks are merged with the layer or group below as if they were contained into a [merge] tag.