• Runtimes

  • Need some Tech support for upgrade to 3.8

    anglais

My company developed with Spine 3.7 but for using UE4 UMG need to upgrade to 3.8 now.
There is some issues that needs tech support to make decision to upgrade 3.8

  1. Backwards compatibility is not guaranteed when opening 3.7 work in 3.8 environment.
    In case of Flip, when upgrade from 3.6 to 3.7 the mechanism changed but not guaranteed backwards compatibility.
    and 3.8 changed Flip mechanism again but still not guaranteed backwards compatibility.
    I have over 1,000 spine files with 3.7 so if there is no tech support I need to fix that one by one.

  2. When import a project, transform's value changed.
    In 3.7 there is no problem when move child bone from project A to project B, in 3.8 transform's value changed.
    Even if transform's value in parent bone is same but after moving transform's value in child bone changed.

  3. Like as issue #1, Cannot load json file with version 3.7 on version 3.8

Because of these issues Cannot release engine update internally. and If can't resolve these issues, develop process will holding until resource porting done.

Please give me some tech support or guide to solve this situation.

Related Discussions
...

Glad to help!

1) I don't understand. "flip" was removed from Spine in 3.0.00 (replaced with negative scale). It has not been changed since. We do not make such behavioral changes lightly, but removing flip was necessary. Moving from 3.7 to 3.8 should not change any of your skeletons or animations.

2) Are you sure you have the same axes selected (local, parent, or world) in both cases? If so we'll need steps to reproduce this so we can see the problem. For example, maybe you can tell us what steps to take to see the problem with the spineboy project, or you can email steps to take using your project file: contact@esotericsoftware.com

3) Compatibility is done at the Spine project file level. Newer versions of Spine can always open older Spine projects (ie Spine has backward compatibility). Older versions of Spine cannot open newer Spine projects (ie Spine does not have forward compatibility).

Spine does not have any compatibility for JSON or binary data: you should always use the same Spine version that matches the JSON or binary data you are importing. Spine does not support opening JSON or binary data from other versions of Spine. In practice sometimes it will work, but this is a coincidence and not officially supported.

You should not keep JSON or binary data and expect to import it into newer versions of Spine. Instead, keep the Spine projects which can always be opened by newer versions of Spine.

If you do have old JSON or binary data, to bring it into a newer Spine version you'll need to first import it into the old version of Spine, save a project file, then open the project file with the newer version of Spine.

Hi Nate

I sent a e-mail for issue #2.
and Thank you for other feedbacks =)

Thank you

Got the email and videos for #2, thanks. Import Project appears to work just fine, but there seems to be a problem in 3.8 when dragging a bone from one skeleton to another skeleton. We will look into this and get back to you ASAP!

We've fixed the problem in 3.8.22-beta, thanks for reporting!