Этот сайт лучше всего просматривать в современном браузере с включённым JavaScript.

Color/Alpha is not playing on runtime

warmanw

I encountered this issue 3 times with 3 different projects clients ask to remove color/alpha animations(interpolations) because it is not being played on runtime

Can someone please explain how to overcome that, because animating without color/alpha is a huge limitation

Davide

warmanw

Which runtimes are your clients using?
In general, simple color tinting is supported by all runtimes, while dark color tinting is not universally supported.
For example, spine-pixi supports all Spine features, whereas spine-haxe does not support premultiplied alpha atlases or tint black.
This information is usually outlined in the initial section of the runtime documentation page.

Spinebot

To address the issue of color/alpha animations not playing correctly at runtime, there are several potential solutions and considerations based on the context provided:

Premultiplied Alpha: Ensure that your images are exported with premultiplied alpha if your runtime requires it. This is a common requirement for proper blending, as seen in the cocos2d-x 3.1 runtime example. If premultiplied alpha is used, make sure it is also enabled in the runtime settings.
Runtime Settings: Check if the runtime you are using supports color/alpha animations and if there are specific settings that need to be enabled. For example, in some cases, you might need to disable options like "Cull Transparent Mesh" in Unity to ensure that transparent attachments are rendered correctly, as mentioned in the Default animation doesn't work context.
Animation Keys: Verify that color/alpha keys are correctly set in your animations. Sometimes, keys might be inadvertently removed during export if "Animation Cleanup" is enabled, which removes keys identical to the setup pose. Disabling this option might help, as suggested in the Mix duration not working context.
Shader and Rendering Pipeline: Ensure that the shaders and rendering pipeline used in your runtime are compatible with the color/alpha animations. Issues with shaders not being set correctly can lead to blending problems, as noted in the Blending issues context.
Debugging and Testing: If the problem persists, consider debugging the runtime to verify that alpha values are being applied correctly. This can involve checking the animation timelines and ensuring that the correct values are being used, as mentioned in the Monogame - Alpha not working context.

By addressing these areas, you should be able to overcome the limitations and ensure that color/alpha animations play correctly at runtime.

warmanw

Davide current one is using spine player I also had one using phaser. we dont use PMA because it was creating dark edges. now I suggested them to use it to see if at least alpha issue goes away

Davide

It should work on those runtimes. Can you send a repro project?

warmanw

premultiply alpha fixed the issue so what runtime does not support alpha animation?

Misaki

warmanw There are quite a few runtimes that we publish, and the support status of the same runtime can also vary depending on how it is implemented. For example, in the case of spine-phaser, all Spine features are supported if you are using the Phaser WebGL renderer, but if you are using the Canvas renderer, meshes, tint black and blend modes are not supported. It is recommended that you check the documentation for the runtime you intend to use.

Davide

warmanw

As I was trying to explain earlier, slot color/alpha animation is supported across all runtimes.
I’d really like to help, but I haven’t quite understood your issue yet. If you’re experiencing a problem with a specific issue and you are able to reproduce it, it would be much easier to assist if you could show the exact issue.

warmanw

Davide The thing is most of the time this request comes directly from the clients "hey dont use alpha animation our engine doesn't render it" and I am not the one who can help them to find the issue they already decided to not use it and we move forward. (phaser runtime - spine 4.2.36)

Once I've received a request from a client to never set alpha 0% instead use 1% if I want to make it transparent(3.8.53)

However for this project where we use spine player client asked me initially to fix black edges I turned off premultiplied alpha instead I should have asked them to turn PMA on their side. now it works fine thanks to your advice @Davide

Davide

warmanw

Thanks for your quick reply!

I’m glad you resolved the black edge issue. Generally, "black edge issues" occur when PMA textures aren’t interpreted as PMA by the runtime. If your clients are using a runtime that doesn’t support PMA, you can export assets with straight alpha (PMA off); this will prevent black edges from appearing too. The only limitation in this case is that blend modes won’t be available.

As for the alpha issue with the Phaser runtime, that’s unusual. The spine-phaser (and spine-player) runtimes rely on spine-webgl, which supports all Spine features and has no known issues. If your client is interested in addressing this, they’re welcome to reach out on the forum or by email. We’d be more than happy to ensure you’re both able to use all Spine features.

Mario

@warmanw you can also always redirect your clients directly to us either here on the forum or via email (contact@esotericsoftware.com). It doesn't make sense for you to try and figure out technical issues for them.