Search Issue Tracker
Duplicate
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
- Crash on UnityPlayer!profiling::ProfilerManager::DisposeProfilerRecorder+0xa when Player gets relaunched and exited after running for a long amount of time
- [Input system] When releasing one touch and pressing a second touch during a single frame, the second touch is not translated into UI event line OnPointerDown by the InputSystemUIInputModule
- URP Samples - multiple "Attempting to resolve render surface" and other errors appear when setting Quality pipeline asset
- OnDemandRendering.willCurrentFrameRender returns incorrect values in the Player when UnityEngine.Rendering.OnDemandRendering.renderFrameInterval is greater than 1
- Root motion is not reapplied when transitioning from an animation without root motion to an animation with root motion
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