• RuntimesGodot

  • Converting spine .json to .skel for Godot 3.5.3

    英语

Hello!

I'm trying to convert a spine which uses .json to the format that uses .skel and I don't have the project anymore, only the exported file.

Using Windows Powershell and Esteric's spine command line, those were my steps:

  1. I used the old spine animation to create a spine project:
    & 'C:\Program Files\Spine\Spine.com' -u 3.7.xx -i old_spine.json -o old_spine.spine --import;
    When I opened this project, the animations were there but the images couldn't be found.

  2. With the spine project created, I created the export.json below to use as a configuration file
    {
    "class": "export-binary",
    "open": false,
    "extension": ".skel",
    "prettyPrint": false,
    "nonessential": true,
    "cleanUp": true,
    "packAtlas": null,
    "packSource": "attachments",
    "packTarget": "perskeleton",
    "warnings": true
    }

  3. And then used this command to create the .skel format:
    & 'C:\Program Files\Spine\Spine.com' -u 3.7.xx -i old_spine.spine -o . -e export.json ;
    At this step, the powershell terminal showed that the animation's images could not be found.

  4. After the conversion ended, I tried to use it on Godot 3.5.3 using the node "SpineSprite" but I got an error saying the .skel file could not be loaded.

Could anyone share a light in this predicament? =p

Related Discussions
...

Based on the steps you've outlined and the issues you're encountering, it seems like the primary problem is related to the missing images when converting from .json to .skel. When you import the .json file into Spine and the images cannot be found, it means that the Spine project is missing the necessary attachments for the animations. This issue carries over when you attempt to export to .skel, as the export process cannot link the animations to their respective images, leading to errors when trying to load the .skel file in Godot.

To resolve this issue, you need to ensure that the images referenced by the original .json file are available and correctly linked in the Spine project before exporting to .skel. Here's a revised approach:

  1. Recreate the Spine Project: When you import the .json file into Spine, make sure the images (attachments) used by the animations are placed in the correct directory expected by Spine. Typically, this would be in a folder named images located in the same directory as your .spine project file. The directory structure should match what was originally used when the .json was first exported.

  2. Relink Missing Images: After importing the .json and creating a new Spine project, manually relink any missing images through the Spine Editor. This might involve pointing to the correct image files within the Spine Editor if they are not automatically found.

  3. Export to .skel: Once all images are correctly linked and visible in the Spine Editor, proceed with your export to .skel using the configuration file as you've described. Ensure that the export version matches the Spine runtime version supported by your version of Godot.

  4. Import into Godot: With the .skel file and associated images (now correctly linked during the Spine export process), import these into your Godot project. Ensure that the Spine runtime version used for the export is compatible with the spine-godot runtime version in your Godot project.

Remember, the spine-godot runtime documentation emphasizes the importance of matching the Spine Editor version with the spine-godot runtime version for compatibility. If you're using Godot 3.5.3, ensure that the spine-godot runtime you're using is intended for that version of Godot and that your Spine exports are compatible with that runtime version.

    Spinebot

    Hm... a coworker needed those spine animations updated to a new version but in the json format.
    He used the same process with the images unlinked but in the end everything worked.
    Does this image link problem only occurs with the skel format?

      The skeleton data and images are mostly separate. For region attachments the image sizes are stored in the data, but otherwise everything else in the data is separate from the images. That it can't find images should just be a warning. At runtime you'll have course need the images.

      What you did looks right. You can also do it via the editor UI, but using the CLI is fine and can enable you to process many files this way automatically.

      What version of Spine does Godot 3.5.3 require? You export the binary data using 3.7.xx. If you are using the latest spine-godot runtime in the 4.1 branch, then it requires 4.1:
      EsotericSoftware/spine-runtimestree/4.1/spine-godot#spine-version
      The editor version used to export must match the runtime version:
      http://esotericsoftware.com/spine-versioning#Synchronizing-versions

      You can export the .spine project file for 4.1:

      & 'C:\Program Files\Spine\Spine.com' -u 4.1.xx -i old_spine.spine -o . -e export.json ;

      However, when upgrading a project, especially from such an old version, I suggest checking it in the editor UI to be sure the animations look correct.