The exported images feature a black border

maxliu

Improvement: As previously stated, even after deselecting the limited resource option, exported images still have a black border present. Prior to this issue, there was no occurrence of a black shadow border when deselecting the limited resource button, yet it has suddenly appeared today.

Harald

@maxliu Likely you have enabled Premultiply alpha
upon export (the default). This needs to be matched on the runtime side in your game toolkit as well, if supported (e.g. for spine-unity see here). If it's not supported by your runtime according to the respective runtime documentation, please disable Premultiply alpha.

If you have Premultiply alpha disabled already, please provide more information about your export settings and whether the above image is a screenshot inside your game toolkit of of the raw atlas image png file.

maxliu

Thank you for your response. My project is not being used in Unity.
The following image is the original PNG file used by Spine. However, after exporting it, a black border is added to the blurred pixels at the edges. Previously, this issue could be avoided by disabling the finite resources, but yesterday, even deactivating them did not prevent the appearance of the black border.

Misaki

maxliu Please ensure Premultiply alpha unchecked in the texture packer settings dialog:

I am not sure what you mean by "the finite resources" because there is no term exactly the same as it in Spine. We would appreciate it if you could show us a screenshot of it.

maxliu

Thank you for your response. I am glad to hear that you have identified the root cause of the issue. Simply selecting this checkbox should resolve it.

Misaki

maxliu Yes, that is the Premultiply alpha! 🙂

Harald

@maxliu Glad it helped.

Misaki I am not sure what you mean by "the finite resources" because there is no term exactly the same as it in Spine.

I assume that finite resources is a translation of the Limit memory option, since this is the closest match.

maxliu

Thank you for your response. It is indeed as you have described, and I have identified the root cause of the issue. Simply selecting this checkbox should resolve it.