• Editor
  • Spine CLI Exporting maxBounds to true does not seem to be supported!

export JSON
{
"class": "export-png",
"exportType": "animation",
"skeletonType": "single",
"skeleton": "man",
"animationType": "all",
"animation": null,
"skinType": "current",
"skinNone": false,
"skin": null,
"maxBounds": true,
"renderImages": true,
"renderBones": false,
"renderOthers": false,
"scale": 500,
"fitWidth": 0,
"fitHeight": 0,
"enlarge": false,
"background": null,
"fps": 25,
"lastFrame": false,
"cropWidth": 0,
"cropHeight": 0,
"rangeStart": -1,
"rangeEnd": -1,
"packAtlas": null,
"compression": 5,
"bruteForce": false,
"quantize": false,
"quality": 100,
"speed": 4,
"dither": 0.5,
"maxColors": 256,
"pad": false,
"msaa": 0,
"smoothing": 8,
"renderSelection": false,
"cropX": 0,
"cropY": 0,
"warmUp": 0,
"output": "",
"id": -1,
"input": "",
"open": false
}

I can successfully export a PNG sequence of 455x500 frames in the software, but when using the CLI, the exported image is still cropped to 345x330, even though the json is set to "maxBounds": true.
Or am I misinterpreting the meaning of "maxBounds": true? Is there another option to set this value?

Spine --export-all --ignore-unknown -u 4.2.43 -i ‘path’ -o “path” -e ‘path’

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

    KimigaiiWuyi Based on my testing with Spineboy, when maxBounds is set to True, images are exported with the correct maximum boundary size even when exporting via the CLI. Would it be possible to provide us with the minimum Spine project file that reproduces the 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.

      Misaki After some testing on my part, it seems to be a problem with refreshing the image resource boundaries, I export directly using .spine without images and it's 345X330, but when I add images (atlas files), it's 455X500.
      I found this out when I was trying to send you guys the simple .spine files, and sadly, using the Unfortunately, using a simple .spine file doesn't seem to reproduce the problem, I have to attach the atlas file, but I can't send the internal private file!

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

        KimigaiiWuyi I may not fully understand your explanation, but I think it is correct behavior that the results differ between exporting without images and exporting with images. I think the boundary that prevents images from being cropped should be determined, so you need to export under the same conditions.

          Misaki I did have inconsistencies using the CLI and program export in exactly the same situation

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

            KimigaiiWuyi I see. I believe what you are saying, but unfortunately, we are still unable to reproduce the issue on our end. Therefore, we would need a project that can reliably reproduce the problem.
            If the issue persists even after most of the skeleton has been removed, we would greatly appreciate it if you could send us a simplified Spine project along with the images (with their contents obscured, for example, by blacking them out).