Can Spine ver4.3 support Phaser 4.1 or runtime Spine-Phaser-v4?

analog2077

Davide

analog2077

We’ve already ported the Phaser runtimes to our 4.3-beta branch, but we haven’t released a package on npm or a CDN yet.
However, you can build a working version of the library from source.
Just switch to the 4.3-beta branch, go into spine-ts, then run npm i and npm run build.
You’ll find the build in spine-ts/spine-phaser-v4/dist.

Spinebot

Spine version 4.3 is not mentioned in the provided contexts, and there is no specific information about its compatibility with Phaser 4.1 or the spine-phaser-v4 runtime. However, the spine-phaser runtime is compatible with Spine 4.1, as indicated by the available documentation and examples. For the most accurate and up-to-date information, it would be best to check the official Spine Runtimes repository or the Esoteric Software website.

analog2077

Davide What about Spine version 4.2?

Davide

analog2077

All our official runtimes support latest stable version.

analog2077

However, I encountered a problem: importing JSON from version 4.1 works and runs fine in Phaser, but from version 4.2 onward, it fails — the object doesn't even appear in the preview.

Davide

analog2077

Are you sure you are using the laster phaser stable runtime?
Can you show here the version you are using?

analog2077

Sorry, I’m a beginner, so I’m not sure where to check the version. When I created the project, I allowed Phaser to install the runtime automatically.

Davide

analog2077

In that case, please read our documentation first.
Phaser built-in spine plugin is outdated and you should you the official one 🙂

analog2077

Davide Thanks for the suggestion. It looks like I’ve managed to fix the issue now. The problem happened because I tried opening a file made with version 4.1 using 4.2, then exported it as 4.2, which caused the issue. Anyway, thanks a lot again!

Davide

analog2077

Glad you solved it!
However, 4.1 projects opened and exported with Editor 4.2 to Runtime 4.2 should work. How did you solve the problem?
If it happens again, it would be appreciated if you could send us your project file at contact@esotericsoftware.com so we can identify the issue.