Thank You!!!

i had this affected to me but noticed that game maker is not up to date on there part also, dammit my animations would've looked smoother and "fresh" but got to work around that and see if i can actually get it similar to what i had before.

This "beta" plan sounds perfect.

hey
well impossible to get the 3.2.01 , and the line don't seems to work on my mac, can you tell me when you'r planing to update the unity & csharp ?

we'll probably need to delay our project, wild waiting for it.
cheers

great !

Hi Guys,

We are trying to update spine runtimes and new codes throwing exception while reading old data

Error causes when missing vertexCount for bounding box in JSON file. I assume it will be easy to add in new codes to skip if no "vertexCount"

thanks !!
i got importer error out of rang in unity with version 3.3.05
i back to 3.2.01 and have a try.

hey @Nate, thx for spine-unity
the last thing we need is the spine-csharp update, cheers

Hey, Mario here, your friendly runtime elf. You can check out the csharp-update-3.3.0 branch on the runtime github repository GitHub - EsotericSoftware/spine-runtimes at csharp-update-3.3.0

Should be ready for general consumption tomorrow. spine-csharp is fully updated, spine-unity is currently being touched by Pharan.

Hi, what is the usual period for the runtimes to catch up with the editor? Specifically cocos2d-x.

Thanks

The spine-c runtime update is in progress, it should be done at the beginning of next week.

Sorry to bump this so late, but I have a question.

Do the latest versions of Spine allow you to now pick any previous version to rollback to?

I remember a while ago it was the case that you could not rollback unless you had previously had that version installed and it was backed up the updates folder. Also I remember something about updating to a new launcher meant you also could not go back to older versions.

Could anyone clarify please?

The current launcher allows you to download and rollback all the way back to 2.1.27. You don't need the previous version installed to do that.

There is a known issue where it crashes on launch the first time you rollback to 2.1.27 but it will run normally after that.

Pharan wrote

The current launcher allows you to download and rollback all the way back to 2.1.27. You don't need the previous version installed to do that.

There is a known issue where it crashes on launch the first time you rollback to 2.1.27 but it will run normally after that.

Thanks for the reply Pharan. very helpful!

Do you know if it is possible to go back beyond 2.1.27 if you have the older original update files currently backed up and copy them over to the correct place?

Hey guys, I have a series of animations that were created with version 2.1.27 for Starling
With the latest Spine version (3.4?) could I still roll back to 2.1.27 and then carefully port each animation to the latest Spine version?
Or maybe you could make a recommendation on upgrading my animations so I don't put myself in a difficult position with the latest Starling build.

Thanks for the help
Patrick

@[obrisani korisnik]

The best thing you can do is first make a backup if your project files. Since when you open your projects with the latest version of Spine and save you will no longer be able to open them with Spine 2.1.27. Most of your animations should be intact, however please note that FlipX/Y keys are no longer available. Instead flipping is achieved by scaling negatively on either X or Y.
As long as you remember to make a backup of your 2.1.27 project files before saving again with the latest version you will not find yourself in a position where you are unable to recover animation data.

I hope this helps!

oh I see...ok thanks. I'll be sure to have my backups.
Thanks Shiu!