SpriteAtlases keep changing their hash without sprites changing, polluting source control

I have the same problem in Unity 2019.3.0f6. Every time I play the project, a new atlas is created for my sprites. And I noticed that this problem also generated a size of 3.6 GB of the "AtlasCache" folder. I was able to reduce this size to 6Mb by deleting the "Library" folder and re-porting the project. But that did not stop Unity from generating new Atlas each time it was played in the Editor.
I use Anima2D in my project, I don't know if it can be related.

 

I'm not sure but is possible Anima2D is responsible for this behaviour. I think Anima2D modify Sprite data everytime at I press play or in Editor.
whatever, this problem don't happen in version 2019.2.8f1
Thankyou

 

Hi Venkify, I found the problem in my project. Is a conflict from Anima2D and 2D Animations plugins. I was creating a Sprite Mesh from Anima2D and a Skin in Skinning Editor from same Sprite. It´s forced the Editor to create a new Sprite Atlas everytime.
Sorry, It´s my fault.
Very Thankyou for atenction.

 

Hi, in Unity 2018.4.16 SpriteAtlas got rid of the Hash record and now when we build on different machines, our AssetBundle has a different name in the texture of the atlas, which leads to a change in its MD5 Hash. How should I be in this case?

 

I'm using Unity 2018.4.22f1 and Unity keeps changing the "totalSpriteSurfaceArea" when I switch between different build targets.



Could you please fix that changing the build target does not modify the .spriteatlas asset in the "Asset" directory, but its data in the "Library" directory only?

This is a problem when you work in a team and not everybody is on the same build target. Then the .spriteatlas assets appear changed in version control and everybody commits the changes over and over again, basically overwriting each other every single commit. Very uncool.

Please fix. Thank you!

 

Necro time.
I don't have time to jump on setting up a repro in trying to setup a specific state for an issue that is still happening halfway through 2021, but I would like to mention it still appears to be happening.

v2020.3.2f1
PlasticSCM keeps catching the changes....we did away with Collab, but it too used to catch this frequently.

Changing platforms is probably the best bet for repro this. I understand it repacks the atlases on platform switches, or seems to, but only some of the files (not all atlases) seem to run into this issue.

No override settings on the current selected platform (or ones switched from: win32/64) either. WebGL has an override but we don't platform switch to that; related?

To be clear, this doesn't only happen on platform switches. It happens hitting play randomly, and then suddenly pending changes in commit, when absolutely nothing asset-related other than CS code has been changed.

Anyways, we're used to this by now for years so I just wanted to chime in on this one that it still appears to happen if anyone ends up looking further into it.