Bug Sprite Atlas is constantly changing serialized assets and logs warnings

I set the project settings to "Sprite Packer Mode - Sprite Atlas V1 - Enabled for Builds", because I don't want anyone on the team waiting for sprite packing while importing assets or testing in the editor. At build time, I expect the sprites to be packed. I also expect that I don't hear from the Sprite Packer until the build.

However, in our current project in Unity 2020.1.11, we constantly see this warning:

Code (CSharp):

1. Invalid sprite atlas asset encountered when matching atlas for sprite MySpriteName. Please repack all your sprite atlases.

And I also see a lot of version control noise. When I make a change to a PSD file, the sprite atlas that references this file is changed like so:



And I see the mentioned warning. So, ok, even though I don't want to, let me hit the "Pack Preview" button on all atlases and go for coffee.

Now the warning disappears, but now I have changed serialized data:



This result must be two different bugs, right? First, I shouldn't be forced to pack sprite atlases in the editor when the setting says "build only" and second, the "Pack Preview" button should only be a preview to check the layout and not actually be saved to version-controlled assets. Because otherwise, as it is now, we are causing constant merge conflicts and warnings for nothing.

In my ideal workflow, the atlases are created during the automatic asset import pipeline, which we've set up. Here I can also add objects for packing. However, I want the sprite packing system to not save any packed data or muck around until a build is triggered. Once the build is over I also expect my version-controlled files to be clean. Sometimes I really get the feeling that only single devs are using Unity and it makes me sad because all of these features could be really great, saving me tons of time, if only they wouldn't get in the way of teams working together.

I don't like to rant, so please give me some hope, that I'm doing something wrong or this is being fixed already!

 

I seem to be getting some random resets on my sprite atlases as well, which is what it looks like is happening to you.

I have no idea what the heck is going on here but my settings are set to "Sprite Packer Mode - Sprite Atlas V1 - Always Enabled"

 

I'm seeing this now in 2022 when switching platform. Was not fixed in spriteatlas v2?

 

Funny that this has a recent answer. I am seeing this for a sprite that I generate in an asset post processor

 

Bug IN-67688

 

Thank you for getting back to us on the issue, much appreciated

I've seen your reply here too https://forum.unity.com/threads/inv...tching-atlas-for-sprite.1542080/#post-9628643 and I will try to create an repro project.

To elaborate. I am creating a Sprite asset in an asset post processor which takes the UVs of a regular Mesh (from a fbx file) and builds a sprite from it which is then added to the import context. This works flawlessly except for that warning which pops up after the sprite has been assigned to the atlas and a new import of the fbx file is triggered. I suspect that the data of the sprite briefly gets invalid while it is recreated but the atlas still has some reference to it.