Search Issue Tracker
Won't Fix
Votes
1
Found in
2020.3.37f1
2021.3.6f1
2022.1.10f1
2022.2.0b2
2023.1.0a4
2023.2.0a1
Issue ID
UUM-9847
Regression
No
[TextureCompression] RGBA compression formats cause artifacts in the image with a transparent layer
Reproduction steps:
# Open the user attached project
# Observe the Game view
Expected result: The image does not have artifacts
Actual result: The image has artifacts
Reproducible with: 2020.3.37f1, 2021.3.6f1, 2022.1.10f1, 2022.2.0b2, 2023.1.0a4
Reproduced on: Windows 10
Note: The supposed look of the image could be seen in the preview for the “256x256” asset in the Assets folder. “RGBA compression formats” are formats that can be found in Import Settings for the “256x256” asset and are containing “RGBA” or “RGB(A)” in its name. Also, the image format used for testing is .png
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [XR] Input is not registered and headset view is headlocked after entering Play Mode with Meta XR SDK on 6000.0.0b16 and higher
- Crash on RtlLookupFunctionEntry when using 10 or more GameObjects with Articulation Body component in the scene
- Polygons are created on the opposite side of the Sprite when the Sprite boundaries are above the edge of the Texture
- Render Graph Viewer Resource list becomes shrunk after using a filter that yields no results
- [Android] [Vulkan] "VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT" not added on some Android devices in "com.unity3d.player.UnityPlayerActivity/2D Colour Attachement"
Resolution Note:
Thank you for reporting a bug to Unity.
The issue originates from some fully transparent pixels getting a very small non-zero alpha value, resulting in their (potentially undefined) color to bleed through. This occurs only with the BC7 encoder and with specific texture content.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.