Hi all!
I'm trying to do a version downgrade from 4.1 to 3.8.
I've tried to export jason file from 4.1 to 3.8 compatibility mode. Unfortunately, I can't import it into spine 3.8, and weird errors appear during the export. For example, "Welcome data download failed, server error: 410"
spine project version downgrade from 4.1 to 3.8
17日 後
Apparently, the only way to do this is the following:
4.1spine export to 4.0 json,
4.0 spine import 4.0 json export 3.8,
3.8 spine import 3.8 json.
obaz No, that is not correct because Spine 4.1 can export JSON files as the format for 3.8, 3.7 or 3.6 by choosing the desired version in the Version option: http://esotericsoftware.com/spine-export#Version
If you exported the JSON file in 4.1 with Version set to 3.8, you should be able to import that JSON file in 3.8. If you prefer, you can send us your Spine project via email so that we can see what the problem is: contact@esotericsoftware.com
Note that you will potentially lose data when downgrading from 4.1 to 3.8. If you use any of the features introduced after 3.8, the resulting json file exported from 4.1 will not contain that data. 3.8 doesn't know how to handle new features.
3ヶ月 後
- 編集済み
Mario Misaki
Thank you Mario for the explanation on this. By any chance is there a way to keep the 4.1 or 4.0 features in a 3.8 exported version. My Development team is saying that they have to use Phaser v6 and 3.8 is the only version that is supported.
Our Art team has unfortunately done all artwork in 4.1 so certain features namely sequencing have been removed and all animations are now linear with NO rotations
Or would you perhaps know a solution to get Phaser v6 with your runtime to work with either 4.0 or preferably 4.1?
Please help if you can or advice is greatly appreciated.
Thank you in advance
Our Art team has unfortunately done all artwork in 4.1 so certain features namely sequencing have been removed and all animations are now linear with NO rotations
Yes, that is the expected behavior when downgrading Spine projects from 4.1 to 3.8.
Or would you perhaps know a solution to get Phaser v6 with your runtime to work with either 4.0 or preferably 4.1?
Perhaps your development team is using the Phaser runtime made by a third party, but actually, an official spine-phaser runtime made by Mario has been released recently. It is compatible with Spine 4.1: https://github.com/EsotericSoftware/spine-runtimes/tree/4.1/spine-ts/spine-phaser
Unfortunately, the documentation has not been ready yet, so that is why we have not yet officially announced the release. If you have any questions with the official spine-phaser runtime, please feel free to ask them to us.
Our Phaser Runtime will be released this week. You can view the docs for it here:
https://esotericsoftware.com/spine-phaser
There are also tons of examples which are direct translations of the Phaser Spine plugin examples:
https://github.com/EsotericSoftware/spine-runtimes/tree/4.1/spine-ts/spine-phaser/example
I'll finish up the docs this week and release spine-phaser officially.
Mario
Thank you again Mario
Just had a long call to Dev team and would this new release be compatible with Phaser v3.55 now?
They are moving onto Phaser v3.6, but our build needs a serious overhaul as this I am told will be compatible with Spine v 4.0 and up.
Apologies on the incorrect Phaser version 6 in my previous message ^ This was a typo
Thank you in advance Spine team!
Yes, it is compatible with Phaser +v3.55 including 3.6.
You can run the examples yourself and switch out the Phaser version in the .html files, like here:
https://github.com/EsotericSoftware/spine-runtimes/blob/4.1/spine-ts/spine-phaser/example/arcade-physics-example.html#L8