[3.24.1] Spine: Infinity x, y, width and height problem

[kittykatattack]

Hi Everyone!

I hope someone out there can help debug a problem I’m currently having using Spine in 3.24.1 (Using plugins/spine/dist/SpinePlugin.min.js)

It seems to be installed fine, and the spine objects load in the Scene without errors, but they don’t display. Their displayOriginX, displayOriginY, width and height values are Infinity or -Infinity

I’m aware that spine object need to be exported with Spine 3.8 or higher, which these assets are (3.8.99). I’m having this problem both with my spine assets and assets from the Phaser example files which I’m loading into my game.That means I’m probably doing something wrong on my side… but I don’t know what.

If anyone out there has seen this before and some idea where I should look, please let me know

[Milton]

Still seems a version mismatch.
I’ve tried this version with 3.24.1, works for me.

[kittykatattack]

@Milton That worked, thanks so much!! I would never have been able to figure that our without your help!!! So it seems that the version of the Spine plugin that comes with 3.14.1 is actually the incorrect one(?).

I’m getting a different (better?) error now: “Slot not found: name”. This might be because:

• Our version of Spine is wrong. We’re using Spine 3.8.95, which I understand is the version to use with Phaser (https://photonstorm.github.io/phaser3-docs/SpinePlugin.html ) But, is this the version to use with the working SpinePlugin.min.js posted above? (Although peripherally related, it seems that the “Slot not found: name” error might be related to a version mismatch… https://www.html5gamedevs.com/topic/43549-error-with-spine-version-3860/)

• There might be something wrong with our Spine source files - although Spine is not giving us any errors.

Any insights helpful! And, I’ll continue to debug…

[Milton]

I think you need pre 3.8.

[kittykatattack]

@Milton Thanks, we’ve just tried with Spine 3.7.94. Everything now loads fine with no errors, but the spine object doesn’t display on screen. All its values (x, y, width, height etc) seem normal, but displayOriginX and displayOriginY seems strangely different.

… Will keep debugging… I’m sure I’ll get it sooner or later!

[kittykatattack]

Just a little update. Our new animations are breaking when we try and re-export them using 3.7.94, but I was actually able to open and view a 3.7.94 test animation by modifying the spineboy code from the Phaser examples. (No luck yet though getting it to display in our actual game - see post above.)

That’s promising, but even if we do manage to get 3.7.94 to work we’re trying to avoid down-versioning our existing Spine animations as doing that will be quite time consuming. So, I’m back at trying to get the 3.8.95 runtime working again. I took a look at the the examples in Phaser 3.34.1, but noticed they don’t actually seem to work?

Phaser 3 Examples

Running the spine-boy 3.8.95 locally also generates this error:

So I’m wondering - can anyone confirm that Spine animations exported with Spine 3.8.95 actually work in Phaser 3.24.1?

[Milton]

I’m pretty sure the answer is no. It seems these days Discord is the better chance of getting an answer…

[kittykatattack]

@Milton Thanks, I will dig around on Discord

[kittykatattack]

Hey Everyone, I was able to fix this problem!

It turns out the animations I was loading were using named skins, none of which were named “default”. So, immediately after loading the animation, I set the skin name explicitly, like this: spineAnimation.setSkinByName("nameOfSkin"); That was it! My spine animations now all work just fine using Spine 3.8.99 and Phaser 3.50.1

[kittykatattack]

I stand corrected!!!

Even though setting the skin caused the animation to display, I’m still seeing -Infinity and NaN values on displayOriginX and displayOriginY . I thought it might still be OK, until I noticed if I tried to create physics body from the spine object, the body’s x and y values NaN and the body won’t display.

Back to the drawing board on this one!

[kittykatattack]

… I figured it out!

Spine animations that have skins, MUST have a skin called “default”. If they don’t they’ll get these errors.

Is this a Phaser “bug”…?

[kittykatattack]

Further update, just for reference. In chatting with my animator, it doesn’t look like the Spine application lets you specifically name an skin as “default”. So, as far I can tell, this would have to be done by manually updating the exported JSON.