• Runtimes
  • Spine-cpp Promblem

  1. If you try to load an unidentified image by pressing Export to spine-cpp, the binary may be extracted incorrectly, resulting in a pointer location error and causing unintended operations

2.When there are attachment names with suffixes like (_1, _2, _3…), if extracted in Json Format,when Json Format is selected, the key value in the *.atlas file is 'leg6', and an index is appended to it. when Binary Format is selected, the key values in the *.atlas file are correctly output as 'leg6_1', 'leg6_2'. When actually loading, the index is not utilized at all, resulting in a failure to find the key and load the file when extracted in Json Format. This is causing continuous issues during internal testing.

I have attached detailed information and a sample project via email.

Related Discussions
...

Thanks for the preemptive email!

  1. Binary data and images are completely separate. Missing images should not affect the binary export. Your binary data was exported with 4.1.24 and I'm able to load it fine with the 4.1 Skeleton Viewer. I suspect you may be trying to load it with a 4.2 runtime, which won't work. The runtimes must match the version of the editor that exported the data:
    http://esotericsoftware.com/spine-versioning#Synchronizing-versions

  2. Most Spine users want to uncheck Indexes for the texture packer. That setting is for frame-by-frame animation, so all the regions will have the same name but different indexes. It's a texture packer feature, but you don't want to use it with your skeleton data.

    Nate


    Hello Nate, We used Version 4.1 when we build solution. Could you check this with 4.1 cpp runtime?

    My colleague, Mario, can check spine-cpp but unfortunately he's out today and may not be able to get to it until Monday. Since it works in the 4.1 skeleton viewer, it should work in spine-cpp. If it doesn't, it's a bug in spine-cpp and we'll be happy to fix it.

    Thanks for the repro via email. I'll reply here once this is fixed.

      شهر واحد لاحقا

      Mario Hi, Mario. Could you tell me when this will be fixed?

      Sorry for the late reply. I've fixed the first issue in spine-cpp in the 4.1 and 4.2-beta branches. The second issue is due to an incorrect texture packer setting. You can simply uncheck this checkbox for things to work: