• Runtimes

  • Issue with premultipliedAlpha in Spine Animation on iOS

    английский

  • SShastri

    • Сообщение #1
    • Изменено
    • Это сообщение на английский

    We are currently working with Spine animations. The animator provided us with Spine version 4.2 and enabled premultipliedAlpha. The animation displays correctly and handles transparency on an Android project using the libGDX runtime. However, on our native iOS runtime project (UIKit & Metal), the same animation does not display transparency correctly and the background color shows as black when premultipliedAlpha is enabled.

    I have submitted this issue on GitHub issues-2586 but I haven’t received a useful response yet. Can anyone provide help or insight into this issue?

    Thank you for your assistance!

    Related Discussions
    ...

    The issue you're experiencing with premultiplied alpha on iOS could be due to several factors. Here are some steps and considerations based on similar issues discussed in the forums:

    1. Premultiplied Alpha Settings: Ensure that the premultiplied alpha settings are consistent between your Spine export and the runtime settings. If premultiplied alpha is enabled during export, it should also be enabled in the runtime. Refer to the Spine Texture Packer documentation for more details.

    2. Texture Import Settings: For iOS, make sure that the texture import settings are correctly configured. Specifically, check that Alpha is Transparency is enabled if you are using straight alpha textures. This setting can be found in the [Spine-Unity documentation](https://esotericsoftware.com/spine-unity#Advanced

    • Davide

    • Сообщение #3
    • Это сообщение на английский

    As I 've already replied in the other thread, the issue you reported is already under our consideration. Mario, who is following the issue is currently unable to respond to you due to some health issues. He will answer to you on the github issue as soon as he is back and operative 👍️

    11 дней спустя

    • SShastri

      • Сообщение #4
      • Это сообщение на английский

      Thank you for the update. However, the issue remains unresolved and I'm still experiencing the same problem. Could you please advise on the next steps or provide an alternative solution? I appreciate your help in this matter.