• EditorBugs
  • Json export and import issue.

Hi im just start using spine for over 1 month now.
Im currently work on Spine 4.2.09-beta same as Dev.

So i recieved a character already rig by the Dev with the basic animation. My jobs is to work on accessories animation base on the existed animation from the character. All i did was just add 1 more bone to the exist skeleton and bind/weight the accessories for animation. i dont use any constraint at all. After i have done with my work i send my spine file and an export JSON.

Here is the setting i use to export JSON

But when dev use my JSON ( i think ) they report back that it missing the accessories that i have done. when they send there JSON to me, i open it up and import my JSON back in it to test if it still have the same issue... the result show as they said i dont see my accessories anywhere. i check the tree for it slot and attachment and it is still there but no where to be see on the work screen, and the bone i add for that accessories was not where it suppose to be and move almost to the 0, 0 axis.

Since the dev and me are first time using Spine so both party still try to find what happend.
thanks for reading i hope i can find an answer for this.

  • Misaki님이 이에 답장했습니다.
    Related Discussions
    ...

    Based on the contexts provided and your description, it seems like the issue might be related to version mismatches or incorrect export settings. When exporting and importing JSON files in Spine, it's crucial that both parties (you and the developer) are using compatible versions of Spine and have correctly set up the export settings. The contexts suggest various potential issues, such as missing animation events, incorrect skeleton data, or problems with attachments not being properly imported or exported.

    One common theme across several contexts is the importance of ensuring that the Spine Editor version matches the Spine Runtimes version being used for development. For example, if you are using Spine 4.2.09-beta, the developer should also use a runtime compatible with this version. Additionally, when exporting, make sure that all necessary data is included in the JSON file, such as attachments and animations. If you're adding new bones and attachments, ensure that these are correctly referenced in the JSON file and that no data is missing.

    Given that the accessories and the new bone you added are not appearing as expected, it's possible that there was an issue with the export process, such as missing data or incorrect settings. It's also possible that the developer's runtime version might not fully support the features used in your Spine version, especially if you're both using a beta version, which might have specific compatibility considerations.

    To troubleshoot, double-check that both you and the developer are using fully compatible versions of Spine and its runtimes. Also, review your export settings to ensure that all necessary data is included. If the problem persists, consider exporting the project again and verifying that all attachments and bones are correctly set up in Spine before exporting.

    LukeSan Thank you for reporting this issue. 4.2.09-beta is a fairly old version of 4.2-beta, and it has a lot of bug fixes, so could you please try the latest 4.2-beta to see if it fixes the problem? While Spinebot has responded about version matches, it is always safe to update your patch version, so we recommend that you always use the latest patch version. If you continue to experience this problem with the latest 4.2-beta, please let us know again.