-
Notifications
You must be signed in to change notification settings - Fork 233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The alpha channel is painted black during compression #464
Comments
I don't think this is a compressor problem (or at least, if it was, it no longer reproduces with the latest release). What version of the compressor are you using? Can you share the input texture and the generated output astc file? Decompressing with the command line seems to give the right result on a transparent PNG I have locally:
|
In Unity when you import the texture what is the "Alpha Source" option set to in the import settings? I think that needs to be set to "Input Texture Alpha", with the "Alpha Is Transparency" option ticked. |
@solidpixel
I built
Sorry I can't attach astc file to github comment here.
When I import astc file to Unity, that setting "Alpha Is Transparency" is not available. When I import original png, "Alpha Is Transparency" is available. |
As you pointed out, the "Alpha Is Transparency" setting seems to toggle between transparent and black in Unity. Please wait a little while before trying to check via the application in production, and if it is transparent I will close this issue. |
A local check would be to decompress the |
Solved! I import the astc image into my application and confirmed that it is transparent without any problems. |
Great, thanks for confirming. Closing. |
The transparent areas are blacked out, when an image with transparent areas (sample.png) is compressed with the following command.
How can I solve this problem?
The following images are comparing images before and after conversion on Unity.
※ Sry, If this is a problem with the Unity settings.
original image (png)
encoded image (astc)
The text was updated successfully, but these errors were encountered: