• EditorBugs

  • Issue with Exporting Binary File in Spine v.4.2.32

    英语

Hello everyone,

I've encountered a problem with exporting binary files in Spine version 4.2.32. It appears that the export as a binary file for skeletal animations (skeleton.skel) is no longer functioning correctly.

To verify the issue, I tried loading the exported binary file using Skeleton Viewer version 4.1.24, but unfortunately, it couldn't load the file. This confirms that there is indeed a problem with the export process in the latest version of Spine.

Has anyone else experienced this issue? Any suggestions or workarounds would be greatly appreciated!

Thanks in advance for your help.

Related Discussions
...

It seems like you are experiencing issues with exporting binary files in Spine version 4.2.32. Here are a few points and suggestions based on similar issues and solutions from the community:

  1. Version Compatibility: Ensure that the version of the Skeleton Viewer matches the version of Spine used to export the binary file. Binary files are very sensitive to version mismatches. For example, if you export with Spine 4.2.32, you should use the Skeleton Viewer of the same version.

  2. Re-exporting: Sometimes re-exporting the skeleton data can resolve issues. Make sure to use the exact same version of Spine for both exporting and viewing.

  3. Runtime Compatibility: If you are using a runtime (e.g., spine-unity, spine-libgdx), ensure that the runtime version matches the Spine editor version. For instance, if you export from Spine 4.2.32, you should use the corresponding 4.2 runtime.

  4. Known Issues and Fixes: There have been instances where bugs were identified and fixed in specific versions. For example, issues with binary export were fixed in various runtimes in the past. It might be worth checking if there are any updates or patches available for your current version.

  5. Alternative Export Formats: If the binary export continues to fail, consider using JSON export as a temporary workaround. JSON exports are generally more forgiving and might help you continue your work while the binary issue is being resolved.

  6. Contact Support: If the problem persists, you might want to send your project files to the support team for further investigation. They can provide more specific assistance and potentially identify any underlying issues with your project setup.

For more detailed troubleshooting, you can refer to the following resources:

I hope these suggestions help you resolve the issue!

I wanted to provide an update regarding the issue I previously mentioned. After downloading the correct version of Skeleton Viewer, I'm now able to view the skeleton.skel file properly.

However, I encountered another problem when trying to import the skeleton.skel file into Godot using the runner spine-godot version 4.2. It seems that the import process is not successful, and I receive the following error message: Error importing 'res://portraits/astrid/spine/skeleton.skel'

Has anyone else faced this issue, or does anyone have any suggestions on how to resolve it?

Thanks again for your assistance.

    Firegate I tried importing data exported from Spine 4.2.32 into Godot 4.2.2, but I was unable to reproduce the error related to the .skel file. In order to reproduce the problem, could you send the skeleton file that caused the import problem via email?: contact@esotericsoftware.com
    Please include the URL of this forum thread in the email so we know the context. Then we can take a look at what's wrong.

      Thank you for your response.

      I have sent all the files from the output folder via email as requested. These files include the skeleton file that caused the import problem.

      Thank you for your assistance.

        Firegate Thanks for sending the skeleton files so quickly! Indeed, when I imported them into Godot 4.2.2, I could not display the skeleton. As far as I tried, the skeleton cannot be displayed even in the SkeletonViewer, and importing it into Spine 4.2.32 via Import Data also failed. We will investigate the cause.