Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.2.21f1
2023.1.0b18
Issue ID
UUM-36454
Regression
No
Texture generates noise when Compression is set to "High Quality"
How to reproduce:
1. Open the “Compression_Quality_Bug“ project
2. Open the “SampleScene”
3. Observe the Game view
Expected result: black silhouette texture has no noise
Actual result: black silhouette texture has noise
Reproduced with: 2022.1.0a1, 2022.2.21f1, 2023.1.0b18, 2023.2.0a15
Not reproduced with: 2020.3.48f1, 2023.2.0a16
Could not test with: 2021.1.0a1, 2021.3.26f1 (Could not resolve scripting errors)
Reproduced on: Windows 11
Notes:
1. Reproducible in Player
2. Not reproducible with “None”, “Low Quality”, and “Normal Quality” Compression settings
3. Reproducible in a new project → adding a Sprite with “High Quality” Compression asset to an Image Component and setting the Color field to 0R 0G 0B 255A
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
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
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.