krutovig

Hi.

We have I think pretty usual situation: we don't know the version of runtime integrated in project because person who did it is not with us. So, here is the question: how to know which version do we use? All we know that the last update was at May 1, 2019.
krutovig
  • Mesajlar: 30

Erika

Hello, what runtime are you using?

A way to discover the version used at runtime may be to open one of the json/skel files and at the beginning of the file look for the field:
"spine":"3.6.53"
Where the number indicates the Spine version used to export it.

The next step would be to downgrade Spine to match that same version:
Settings - Spine User Guide: Version
Kullanıcı avatarı
Erika

Erikari
  • Mesajlar: 3064

krutovig

"Where the number indicates the Spine version used to export it."
but we need to know the runtime version, not the version of exported animation

---

The thing is: animator worked on project before used different versions of Spine. And we can't just saw the version of old exports because they are different. We need to know what exactly runtime version we have to be sure which version of Spine won't conflict with it.
krutovig
  • Mesajlar: 30

Nate

The version is not embedded in the Spine Runtimes code. You could look at the commit dates and find May 1, 2019, but I wonder where you got that date and if it would really be the exact commit you have. Short of checking out versions from Git and comparing with the Spine Runtimes code you have, there isn't a way to know the exact Git commit that you have. However, this is likely not needed. You can look at the version of the exported data, as Erika described, then use the latest runtime that matches that version. For example, if your data was exported with 3.6.20 then the 3.6 Git branch has the latest runtime for your data.

An alternative would be to export your projects with the latest editor and update your app to use the latest runtimes.

---

I see your additional post now. The latest 3.6 (for example) runtimes will work with exports from any 3.6 version of the editor. If you data was exported with very different editor versions, eg 3.5 and 3.6 then you should export them with the same editor version (at least major dot minor version).

If you don't have the project files for your data exports, you can import them into the same version of Spine they were exported from, then save a project file. You can then open that project file in any newer version of Spine. If you have many projects, you can do this from the command line:
Spine 3.8 released - mesh tracing, polygon packing, and more
Kullanıcı avatarı
Nate

Nate
  • Mesajlar: 11863

krutovig

Nate yazdı:The version is not embedded in the Spine Runtimes code. You could look at the commit dates and find May 1, 2019, but I wonder where you got that date and if it would really be the exact commit you have. Short of checking out versions from Git and comparing with the Spine Runtimes code you have, there isn't a way to know the exact Git commit that you have. However, this is likely not needed. You can look at the version of the exported data, as Erika described, then use the latest runtime that matches that version. For example, if your data was exported with 3.6.20 then the 3.6 Git branch has the latest runtime for your data.

An alternative would be to export your projects with the latest editor and update your app to use the latest runtimes.

---

I see your additional post now. The latest 3.6 (for example) runtimes will work with exports from any 3.6 version of the editor. If you data was exported with very different editor versions, eg 3.5 and 3.6 then you should export them with the same editor version (at least major dot minor version).

If you don't have the project files for your data exports, you can import them into the same version of Spine they were exported from, then save a project file. You can then open that project file in any newer version of Spine. If you have many projects, you can do this from the command line:
Spine 3.8 released - mesh tracing, polygon packing, and more
So you're saying that if I have 3.8 runtime every Spine version 3.8.--- will fit it? And we can update spine with new updates coming without fear to get some conflicts?
krutovig
  • Mesajlar: 30

Nate

Yes, that is the idea. When we do a non-beta editor release, it means that all the runtimes we provide have been updated to use data from that release. We continue to do fixes in patch versions for some time (where the version numbers are in the format: major.minor.patch), but we don't make breaking changes. It is pretty safe to get patch updates and sometimes they have important fixes that you'll likely want. If the major or minor version changes, then you'll very likely need to export your data again (so keep the project files!) and it may require a little more work in your code to update to the latest runtimes.
Kullanıcı avatarı
Nate

Nate
  • Mesajlar: 11863

krutovig

thanks for the answer
krutovig
  • Mesajlar: 30

MungBeans

Not sure if this is related, but what I do to find out what version the Spine file was originally created from, is the following

1) Load Spine with the latest version
2) Try to save a copy of the file

What will happen is a message will appear warning you that you will overwrite the older version and it will also tell what the old version that Spine file was made from. :grinteeth:
MungBeans
  • Mesajlar: 3


Dön Runtimes