Search Issue Tracker
Won't Fix
Won't Fix in 2022.3.X
Votes
0
Found in
2022.3.5f1
Issue ID
UUM-54209
Regression
No
Higher than expected memory for certain block sizes is used when using ASTC textures on iOS devices
How to reproduce:
1. Build and run for iOS with Development Build enabled.
2. Enable the Unity Memory Profiler.
3. On the Memory profiler, notice that the ASTC 5x5 texture reports 1.3 MB.
4. Go to Xcode and enable the Metal Debugger.
5. Find the ASTC 5x5 texture in the Metal debugger and notice it reports 2.02 MB.
Expected: Xcode reports 1.3 MB for the ASTC 5x5 texture
Actual result: Xcode reports 2.02 MB
Notes:
- CQA Testing was not done as per the request of the developers
- attaching the testbed metal project, which is compiled under xCode v14.2 which also reproduces the issue.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
fix will be on Apple's side
Resolution Note (2022.3.X):
fix will be on Apple's side