Search Issue Tracker
Active
Votes
7
Found in
2019.4.7f1
2020.1.1f1
2020.2.0a20
Issue ID
1267918
Regression
No
[Memory Profiling] Texture Importer memory size does not match memory size shown in the profiler
Different sizes are shown for ASTC type textures between the Texture Importer Preview window and the Memory Profiler window
To reproduce:
1. Download attached "TextureTest.zip" project in Unity
2. Open "SampleScene" scene
3. Select "wall" Texture
4. In the Texture Preview Window notice the Size of the Image - it should be around 200 - 300 KB
5. Open Profiler and select Memory tab
6. Press "Take Sample Playmode" button
7. Inspect "Assets > Texture2D > wall" Memory Size
Expected results: The Size shown in the Texture Importer Preview window is similar to the Memory Profiler window
Actual results: The Size shown in the Memory Profiler window is almost twice as large as the Texture Importer Preview window
Notes:
- Checked only on macOS cause I don't have Windows machine with me
Reproduced on 2019.4.7f1, Unity 2020.1.1.f1 and 2020.2.0a20
Not reproduced on 2019.4.6, Unity 2020.1.0f1
Regression on Unity 2020.1.1.f1
Note:
This is partially "By Design". The Inspector Preview currently shows the file size on disk.
This is unclear and misleading and some texture compression sizes are just wrongly calculated right now, which is the bug part.
Comments (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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Peter77
Jun 09, 2021 15:15
Related forum thread:
https://forum.unity.com/threads/case-1339307-profiler-astc-texture-memory-cost-not-correct.1116484/