Phaser - Switching from Phaser Spine plugin to Esoteric Spine plugin issues

defmech

We've converting a project to use the Esoteric Spine plugin for Phaser rather than the Phaser Spine plugin. All has gone well except we're seeing some visual differences. Possibly to do with premultipliedAlpha.

With the Phaser Spine plugin we'd use spineGameObject.preMultipliedAlpha = true. This is not supported with the Esoteric Spine plugin but we are passing true as the premultipliedAlpha parameter when calling scene.load.spineAtlas().

The differences we're seeing are hard edges on spineGameObjects. See image below.

Any help appreciated.

Cheers,
Defmech

Misaki

defmech Hmmm, I cannot see the image you attached. Could you upload the image directly to this forum? You can drag and drop the image onto the form or use the Upload button:

defmech

Here is the image. Note the outline on the bottom part.

Misaki

defmech Thank you for showing us the image! This is certainly the line you see when the texture atlas is output as a PMA image, but is not correctly rendered as a PMA at runtime. From your description, I think your implementation should be correct, but without seeing the actual code, it seems hard to know what is wrong. Could you please email us a minimal project that can reproduce the problem?: contact@esotericsoftware.com

Please include the URL of this forum thread in the email so we know the context. Then we can take a look at what's wrong.

Mario

@defmech there shouldn't be any need to explicitley configure PMA. The PMA setting is stored in the .atlas file and the spine-phaser runtime interprets that. All our spine-phaser examples use PMA and work as intended. As Misaki said, we'll need your Spine project and a minimal repro to figure out why it is not working in your case.