Search Issue Tracker
Won't Fix
Votes
2
Found in
2021.3.43f1
2022.3.45f1
6000.0.16f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
Issue ID
UUM-79063
Regression
No
[16k Textures] The Texture is black on Mip 0 when the ASTC 6x6, 10x10, 12x12 image format is selected
Reproduction steps:
1. Open the “ReproProject“ project
2. Select the “Assets/Images/map.png“ image in the Project window
3. Select the iOS settings and mark the “Override” checkbox for the compression in the Inspector window
4. Change the Format to “RGB(A) Compressed ASTC 12x12 block” in the Inspector window
5. Press the “Apply” button in the Inspector window
6. Observe the Preview in the Inspector window
Expected result: The Preview is the same as the image
Actual result: The Preview is black
Reproducible with: 2021.3.43f1, 2022.3.45f1, 6000.0.16f1
Reproducible on: Windows 11 Pro (22H2)
Not reproducible on: macOS Sonoma 14.6.1 (M1 Pro)
Notes:
1. Also reproduces with the “RGB(A) Compressed ASTC 10x10 block”, and RGB(A) Compressed ASTC 6x6 block” Formats
2. Does not reproduce with the “RGB(A) Compressed ASTC 8x8 block” Format
3. Only the "0" Mip is affected
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
Thank you for reporting a bug to Unity.
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.