Using Sprite Swap with spritesheets

I'm trying to get a very simple setup running using the Sprite Library und Sprite Resolver Components. I have this spritesheet with two different character skins:


Now I want to make one single animation consisting of two frames. And then I want to be able to swap the sprites at runtime for the other skin. So I thought I could set up the Sprite Library like this:


Now I only need to change the category to switch my dark skin for the red one. But when I try to animate this, it doesn't work, as the category can't be changed separately anymore. It's now saved in one single Sprite Key. What happens is that I set up my animation for the dark skin, but then have no way of actually swapping to the red one. The animation will always pick the dark skin as it has a unique key.

The documentation makes it seem like this is exactly what the Sprite Resolver is supposed to be used for, but it just doesn't work. Why can't I just change the category separately? Or am I doing this wrong?

 

@Ted_Wikman
Thank you, this is exactly what I was looking for. I couldn't get it to work by changing the Sprite in the Sprite Renderer like the example shows, but it works when I change the Sprite Library Asset in the Sprite Library Component.

The workflow is pretty nice, but one thing I've noticed is that it got tedious pretty quickly. All of my spritesheets are set up in the exact same way, but I have to drag in the corresponding sprites for every single frame. What I would like to see is some kind of "Sprite Library Asset Override" or an inspector field where I can drag in a spritesheet that has the same layout as the original one, and the Sprite Library Asset is automatically filled with the correct sprites.

This could probably be solved with an Editor script, but something like this would speed up my workflow tremendously. I could just draw over an existing spritesheet in Photoshop and only have to drag in the texture once to set it up.

 

All right, thank you. While I'm at it here are two more things I've noticed:

1) I think it's really annoying that you have to set both tangents to constant in the animator. Now I understand why I have to do this, but it feels very clunky. I forgot this multiple times, and when I do I basically have to start over from scratch as the animation curve messes up the sprite keys.

I have no idea how to improve this, given how the animator interpolates between the values by default, but I can't understate how fiddly and error-prone this is. There's also no indicator anywhere other than somewhere in the documentation. When I first tried Sprite Swap, I thought it would make sense to animate the Sprite Resolver. So I chose the sprites and everything seemed to work, but then it just didn't. Took me a while to find out the animator was interpolating. From a user-standpoint it feels like I have to right-click on this tiny keyframe for some reason, go to "both tangents" for some reason and then choose "constant". And I have to do this after adding one single keyframe and before continuing with the others. It's just... weird.

If I had to suggest something - how about an "add sprites to animation" button in the Sprite Resolver? This could create keyframes for all sprites in the category (one each frame) and set their values to constant.


2) I think the Component names are pretty confusing. This again comes down to the workflow not being intuitive, but requiring the documentation to get anything to run. I created a Sprite Library Asset and added a Sprite Library to my character. If I hadn't read the tutorial I would've had no idea that I also need a Sprite Resolver. Inside the Editor there's no indication that my library is pretty much useless without it, and on top of that the Component looks like a generic script.

But then I began to wonder why we even need two different Components. The Sprite Library only has one single field and nothing else, that is then used by the Sprite Resolver. Why not just put that field in the Sprite Resolver itself? My suggestion would be: merge Sprite Library and Sprite Resolver component into one and call it "Sprite Library". I think that would be really self-explanatory. You add the Component and see it needs a Sprite Library Asset, so you create that and you'll immediately see the functionality in the inspector instead of having to search the documentation for this mysterious Sprite Resolver. There could even be a "create new Sprite Library Asset" on the Component if no asset has been assigned yet.


I hope this feedback helps.