Search Issue Tracker
Duplicate
Duplicate in 2023.2.X
Votes
0
Found in
2020.3.44f1
2021.3.16f1
2022.2.2f1
2023.1.0a25
2023.2.0a1
Issue ID
UUM-22820
Regression
Yes
Texture2D file size increases when the Texture Shape is set to 3D/2D Array
Reproduction steps:
1. Open the attached project “TextureProject”
2. Open the “Assets/New Scene.unity” scene
3. Select the “Assets/Texture.png” in the Project Window
4. In the Inspector Window, observe the Texture size in the thumbnail preview
5. Change the Texture Shape to “3D/2D Array”
6. Observe the new Texture size in the thumbnail preview
{}Expected result{}: Texture2D file size is 3.0MB
{}Actual result{}: Texture2D file size is 7.0MB
{}Reproducible with{}: 2020.3.35f1, 2020.3.44f1, 2021.3.16f1, 2022.2.2f1, 2023.1.0a25
{}Not Reproducible with{}: 2020.3.34f1
{}Reproducible on{}: Intel macOS 13.0.1
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
null
Duplicate of another internal issue: PROFB-1: [Memory Profiling] Texture Importer memory size does not match memory size shown in the profiler
Resolution Note (2023.2.X):
null
Duplicate of another internal issue: PROFB-1: [Memory Profiling] Texture Importer memory size does not match memory size shown in the profiler