• Editor
  • is there any equivalent of this code for .skel instead of .json?

i was going through the forum looking for any option that can help me and i found this code to convert a json file from one version to another. I wanted to know if there is an equivalent for .skel files, apparently it is easier.

Spine -u 3.6.53 -i skeleton-3.6.json -o skeleton.spine
Spine -u 3.8.93 -i skeleton.spine -o skeleton-3.8.json -e export-settings.json

Related Discussions
...

what I want to do is convert a .skel from version 3.6.53 to version 3.8

  • -u is the update version.
  • -i is the input file.
  • -o is the output file.

You need another parameter to tell Spine what operation to perform on the input and output files. To bring skeleton data into a project file, you want to use import. I don't remember if 3.6.53 supports the import CLI parameter. If it doesn't, you'll have to perform that step using the editor UI.

Your second command looks OK, assuming you have an export-settings.json that does what you want. However, why would you use 3.8.93? You should use 3.8.99. Even better would be to use 4.1, as there are years of development and thousands of fixes and improvements since 3.8.

  • Kel님이 이에 답장했습니다.

    oh, 3.8.93 is just an example I found here on the forum, and so I was looking for a way to do that with .skel files

    Spine -u 3.6.53 -i tiese.skel -o tiese.spine
    Nate
    would it be ok like this?

    If it's wrong, how can I continue to make that file tiese.skel become a tiese.spine?

    Spine -u 3.6.53 -i tiese.skel -o tiese.spine
    You have the version, input file, output file, but where is the operation you are performing?
    Spine -u 3.6.53 -i tiese.skel -o tiese.spine --import