• EditorBugs
  • Binary + JPEG export bug

Problem statement

Describe: 1) what you have tried, 2) what you expected, and 3) what actually happened.

Give step-by-step instructions so we can reproduce the problem, if possible.

Editor information

Tell us your Spine Editor version.

4.1.x
4.2.x

Post your entire spine.log file here (or attach it), if you got any error messages.

Hi,

This is specifically about the exporting of binary outputs. Not sure if JSON output is affected. It's when you're exporting JPEGs, so if you export your project to its directory that you usually save in, it doesn't replace the JPEGs generated, rather, it keeps adding new JPEG files with a higher number count.

Example:

If the output dir has:

test.skel
test.atlas
test.jpeg
test_2.jpeg

and if you simply export again, you'll end up with:

test.skel
test.atlas
test.jpeg
test_2.jpeg
test_3.jpeg
test_4.jpeg

Where as, the expected output should be:

test.skel
test.atlas
test.jpeg
test_2.jpeg

  • Misaki ответили на это сообщение.
    Related Discussions
    ...

    bapho Thank you for reporting the problem! I was able to reproduce the issue you are describing. It certainly looks like a bug that was overlooked for a long time because not many people put the atlas in JPEG format. As far as I have tested, this problem can be reproduced when exporting in JSON format. However, this problem does not seem to occur when using the texture packer to pack only the atlas. If this problem of saving a separate JPEG image bothers you, you may want to use the texture packer until a fix for this problem is available.
    I will create an issue ticket for this problem.

    I have created an issue ticket here: EsotericSoftware/spine-editor824
    We apologize for the inconvenience, but please wait until we have resolved this issue.

    Hi Misaki,

    Thanks for that! I find the JPEG option useful if you don't need transparency, and if conserving space is a priority.