Harald Thank you very much, I will carefully review the content you mentioned. I indeed need to improve my English.

    Related Discussions
    ...

    Nate 我也尝试使用可视化界面的Pack功能参数如下：

      semgilo /Applications/Spine.app/Contents/MacOS/Spine -u "Spine 4.1.17 Enterprise" -i images -o ./pack -n spineboy-ess -p ./pack.json -j . -e ./export.json

      This looks wrong, -j . specifies the path to a directory, but you should enter a path to the project file, e.g. ./yourproject.spine

          Harald 我之前有尝试过，我现在又试了一次结果也是一样
          /Applications/Spine.app/Contents/MacOS/Spine -u "Spine 4.1.17 Enterprise" -i images -o ./pack -n spineboy-ess -p ./pack.json -j ./spineboy-ess.spine

              semgilo -u "Spine 4.1.17 Enterprise"

              The parameter of the -u option is wrong, it should be only "4.1.17" not "Spine 4.1.17 Enterprise".

              "$SPINE_EXE" -u "4.1.17" -i images -o ./pack -n spineboy-ess -p ./pack.json -j ./spineboy-ess.spine

              @semgilo After correcting the above parameter, unfortunately I could not reproduce any issue with your above pack.json and export.json files. When exporting the binary skeleton without an atlas and separately exporting the atlas using the pack.json file, then placing all separately exported assets in the same directory in Unity, everything was imported correctly. Nothing displayed incorrectly. What exact steps did you perform that led to your problem?

                  By the way, you can use three backticks "```" around code for a multi-line block of code, as your above posting looks as if every single line was enclosed with single backticks "`".

                  @semgilo Thinking about your screenshot: did you perhaps not copy both the spineboy.atlas.txt and spineboy.png atlas texture over together? Please note that the atlas textures and the atlas.txt file are an inseparable pair.

                    Harald
                    关键的一步是这个，在透明框上Mesh区域，并不会报错，是表现异常

                    用到下面的图片

                      Harald
                      我可以确定我是放在一起的，我做了很多实验，一开始是在我们的工程，后面就直接在示例工程，我可以还原出问题

                      "$SPINE_EXE" -u "4.1.17" -i images -o ./pack -n spineboy-ess -p ./pack.json -j ./spineboy-ess.spine

                      不幸地是问题还在，你有尝试在里面添加对应的Attachment，然后是Mesh类型的，Mesh框起来一大块透明区域，这个是问题的关键所在

                        • Nate

                        • Publicación n.º 15
                        • Publicación en inglés

                        Spine's CLI parameters are configuration, then an action. You can have multiple actions:

                        [config for action] [action] [config for action] [action]

                        Your command line is:

                         -i images -o ./pack -n spineboy-ess -p ./pack.json -j ./spineboy-ess.spine

                        The first action is that you pack:

                        -i images -o ./pack -n spineboy-ess -p ./pack.json

                        Then you specify -j, which is short for --project and gives the packer context so it can pack meshes intelligently. However, there is no action after the configuration:

                        -j ./spineboy-ess.spine

                        If you want the project context for your packing, it must come before the pack action -p:

                        -i images -o ./pack -n spineboy-ess -j ./spineboy-ess.spine -p ./pack.json

                          @Harald Nate 非常感谢，现在可以正常工作了，是这个顺序的问题。