Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2020.2.X
Votes
0
Found in
2020.1
Issue ID
1293028
Regression
No
SpriteAtlas v2 generated textures do not retain ordering in the build
When making any changes to sprites or sprite atlas v2, the resulting generated texture atlases change their ordering in the final build output causing a large sweeping set of changes to the build resulting in very large amount of data to patch or redownload on many platforms.
Repro steps:
1. Download attached SpriteAtlasV2_in_shared_AssetBundle project
2. Run bundle script from "Bug Report > Execute" Menu dropdown
3. In AssetBundles window, select "Inspect" tab and Add Folder
4. Add Bundles > First and Second folder and compare preload tables
5. Refer to attached screenshot and verify atlas order in table
Expected Result: Sprite Atlas v2 texture ordering in table should be the same for both First and Second bundles
Actual Result: Sprite Atlas v2 texture ordering in table is different for both First and Second bundles
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 version 2021.1):
A fix for this issue will be available on Unity 2021.1.0a8 and above