Phaser Mesh2D in spine-phaser-v4

Davide

We're excited to announce a major upgrade to spine-phaser-v4!
Learn more about spine-phaser-v4 on our blog.

EpiKnightz

I don't know what I'm doing wrong but running the v4 renderer benchmark example:

the engine just doesn't batch any draw at all for me. Even when using spine-webgl there were at least some batch

I've clone a fresh new spine runtimes repo, confirm that I'm on spine-ts 4.3 branch (even higher than release 4.3.11), npm i, confirm that's I'm using phaser 4.2.1, yet the test show nothing like the blog draw call batch demo. Can you support me finding out what's wrong?

Edit: Disable slot object bring draws number similar to spine-webgl renderer (103). Still, that nowhere near what it supposed to be, isn't it?

Edit 2: If I change the animation to walk, then it was batched to 1 correctly. What's the different between those 2 animations that cause batching break?

Davide

EpiKnightz

The portal animation uses the additive blend modes. Phaser does not batch normal and additive blend modes together, while spine-webgl does.
Also, the portal animation ha a clipping attachment and if you use the slot object + slot clipping option, the slot object (that is a Phaser game object) is clipped using the stencil buffer and that requires additional draw calls.
That's a pretty isolated case and as you can see using the walk animation the Phaser Mesh2D renderer batches as expected.