Search Issue Tracker
Won't Fix
Won't Fix in 1.21.X
Votes
0
Found in [Package]
1.21.10
Issue ID
ADDR-3333
Regression
No
[Addressables] Binary catalog is much larger than the old .json catalog
How to reproduce:
1. Open the attached project “TestBinaryCatalog3.zip“
2. Make sure Addressables 1.21.2 is installed
3. Build Addressables (Window -> Asset Management -> Addressables -> Group)
4. Navigate to “Library\com.unity.addressables\aa\Windows” to see the size of catalog.json (should be 176KB)
5. Update Addressables to 1.21.10
6. Build Addressables again
7. Navigate to “Library\com.unity.addressables\aa\Windows” to see the size of catalog.bin
Expected result: The catalog.bin file is smaller in size than catalog.json file
Actual result: The catalog.bin file takes up more space than catalog.json file (220KB > 176KB)
Reproducible with: 1.21.8, 1.21.10 (2020.3.47f1, 2021.3.23f1, 2022.2.16f1, 2023.1.0b13, 2023.2.0a11)
Not reproducible with: 1.21.3 and lower (2020.3.47f1, 2021.3.23f1, 2022.2.16f1, 2023.1.0b13, 2023.2.0a11) - Binary Cataloging is not introduced
Reproduced on: Windows 11 Pro
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:
There are no fixes planned for this Bug
Resolution Note (1.21.X):
There are no fixes planned for this Bug
Resolution Note (1.21.X):
This issue is fixed in 2.0, but will not be fixed in 1.21 due to the necessary API changes.