• Bugs

  • Atlas data is incorrect with 3.8 compatibility

    английский

  • GGamerXP

    • Сообщение #1
    • Изменено
    • Это сообщение на английский
    Related Discussions
    ...

    • GGamerXP

      • Сообщение #2
      • Это сообщение на английский

      When exporting skeleton from 4.0+ Spine using 3.8 compatibility (cause our Spine importer for Unity works only with 3.8- format) - atlas packing data is incorrect when using padding - all positions are off for same amount of pixels as padding. When disabling padding - it becomes OK. When not using compatibility - it also gives correct atlas data.

      To confirm it:

      1. Open ex_3.8_padding.zip
      2. Open text.png in PS or other graphical software.
      3. Open test.atlas.txt and check ShapeB's xy values: 138, 4. This position will be:
        https://gyazo.com/0dc0f5b46a2d48d0e670677943919154
        which is incorrect - it should be 2 pixels higher, at the edge. All other positions are somehow off as well.
      4. You can check all other archives and all positions there are correct, only 3.8 compatibility export is off.

      • Harald

      • Сообщение #3
      • Это сообщение на английский

      Please note that selecting a lower version like 3.8 during json export from 4.0 or newer is not for use at runtime in any game engine, as described here:

      http://esotericsoftware.com/spine-export#Version написал

      Exporting to older versions is intended only as a last resort to partially recover work when a project was accidentally saved with a newer version of Spine. See recovering work for more information.

      So please set your Spine version to 3.8, import your 3.8 json file and re-export the project to receive a 3.8 export usable by any runtimes.

      10 дней спустя

      • Nate

      • Сообщение #4
      • Это сообщение на английский

      What Harald said applies to data export (JSON and binary), but I realize you are only concerned with the texture packer output, even though you are also exporting data. Note you can also run the packer separately if you like, without exporting data. To get < 4.0 compatible output, check Legacy output. When exporting data < 4.0, the packer pretends this was checked, even if it wasn't.

      I see the differences you explained. We've fixed the problem in 4.0.46. Sorry for the wait!