Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2017.4
2018.4
2019.2
2019.2.6f1
2019.3
2020.1
Issue ID
1196890
Regression
No
[Memory Profiler] Different sizes are shown for ASTC textures between the Texture Importer window and the Memory Profiler window
Different sizes are shown for ASTC type textures between the Texture Importer Preview window and the Memory Profiler window
Reproduction steps:
1. Open "TextureTest.zip" project
2. Select "wall" Texture
3. In the Texture Preview Window notice the Size of the Image
4. Open the Memory Profiler
5. Take Sample Playmode
6. "Assets" -> "Texture2D" -> "wall"
Expected Result: The Size shown in the Texture Importer Preview window is similar to the Memory Profiler window
Actual Result: The Size shown in the Memory Profiler window is almost twice as large as the Texture Importer Preview window
Reproduced with: 2020.1.0a13, 2019.3.0b11, 2019.2.13f1, 2018.4.13f1, 2017.4.35f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment