Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.39f1
2021.3.30f1
2022.3.9f1
2023.1.13f1
2023.2.0b9
2023.3.0a5
Issue ID
UUM-48893
Regression
No
MipMaps get removed from textures when using EditorUtility.CompressTexture
Reproduction steps:
1. Open project “TextureCompress.zip”
2. Expand "washing_machine.glb" subassets in the Project window and select the “Texture_1” texture
3. Observe the texture having MipMaps (slider at the top right corner of the texture) through the Inspector
4. Select "washing_machine.glb" in the Project window
5. Select any of the options for “Compression\Texture Compression” in the Inspector and click Apply
Expected result: EditorUtility.CompressTexture keeps the same MipMaps
Actual result: the textures don’t have MipMaps anymore
Reproducible with: 2021.3.30f1, 2022.3.9f1, 2023.1.13f1, 2023.2.0b9, 2023.3.0a5
Reproducible on: macOS Ventura 13.2.1 (Intel)
Not reproducible on: no other environment tested
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
- [VFX] Custom HLSL with 'int' parameter, without the 'in/out/inout' access modifier is not supported
- [Windows] Lens Flare doesn't work in the Lens Flare Showroom URP Sample Scene
- Crash on ujob_execute_job while using OverlapBoxCommand when collisions are more than maxHits
- The validity of the multiple handles can behave differently based on the load/release operations order, when multiple Addressables.LoadAssetAsync and Addressables.Release are used to load and release the same Addressable Asset
- Dynamic text is rendered in the background when it is inside the <font> tag
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.