Official 2D Animation is out of preview for 2019.3

Thank You!

i updated the package and everything started fine, the PSB files processed in earlier versions of the package were re-imported, everything works.

Ok, I'm trying to import from scratch...

But ... I don't understand ...
-In my old files I did not see the "single identifier" - "Sprite Key hash", that you discussed above
"Сategories" and "Labels" are still visible there
-And the library component shows them and the spriteswapper changes, but ...

-How to set all this with the newly imported PSB-file, considering the changes?

from changelog:
"[6.0.0-pre.1] - 2020-11-02

Changed

• Sprite Swap related features moved out of experimental namespace
• Removed editing of Sprite Swap feature in Skinning Module
• Updated Sprite Swap workflow focusing on Project Window and Inspector "

Ok... see an opportunity to create a SpriteLibrary, add a Category, give it a name
add Entry point... wait ...
Wait...
Previously, this could be done by selecting the "Convert Group / Layer to Category" item from context menu, _automatically_
but now?

Is it really just to manually name the Сategories and distribute sprites to the desired fields? 0_o
ALL these variants of sprites that will change, -manually?

No-no ... This can't be!..
Looking into the documentation ...
Oh... it looks like it hasn't been updated yet ...

 

I beg your pardon - English is not my native language, and relying entirely on Google translate - as you can see, leads to misunderstandings.
I will try to describe everything in detail and formulate it as correctly as possible.
But it will take a little time ...

Thank you for your participation!

 

@Ted_Wikman,
Thanks for pointing me to the RuntimeSwap example! The SpriteLibrary.AddOverride API works great, and I've been able to successfully restructure around it.

While I'm here -- I know there's been talk about bringing in SpriteSwap support for sprites with different bone hierarchies. Is that something that's on the roadmap? I just wanted to echo how useful it would be to be able to swap in different components with fundamentally different structures (i.e. a cape for a set of wings, as a contrived example) using a native interface.

 

How is 2D Animation package "is ready for use" if it's performance is ass (like, a lot of ass) without an experimental package that isn't even listed when you enable experimental packages and you have to reference it with a direct link, and then it still doesn't work?.. </end angry forum post>

 

Nope, I just wanted to make an angry forum post at the moment of emotional frustration. No constructive feedback yet!

 

Hi!

Is there a way to automate "bone creation" and "auto geometry" via scripting? I want to create bones with exact length and distance from other bones, which is impossible to do with a mouse manually

 

Thanks I'll check the SpritePostProcess script

For improvement, it would be great if you can add some snapping functionality for rotation and length of bones. For e.g rotating at 15, 30, 45 degree

I have different circular sprites with different sizes and I want them to have
- bones with an exact difference of 45 degree
- bones with exact same length for each sprite

Thanks and have a nice day!

 

Getting this error when we downgraded unity from 2021 to 2020:


Can't seem to resolve this, please help.

 

Can you allow a certain padding size for reslicing, because otherwise there will be sharp edges when mipmapping, which will introduce unnecessary aliasing.
Exaggerated effect:





Also can you add a toggle in the PSDImporter editor to always use the name matching layer id validation? Adding the line

useOldID = true;

and saving (then after Unity reverted the file, saving the change again to keep it temporarily) meant that I could add a layer in Affinity Designer without breaking the skinning data:

 

I wanted to tint specific parts of a character, so I made this to easily transfer skin data from one sprite to another. There are 2 modes:

• Copy all the data over
• Similar to Blender's Data Transfer modifier using nearest-face-interpolated: replace each vertex's bone weights with the nearest bone weights in the source sprite.

It should also be able to transfer skin data across files.

I think it might be useful for you guys:
https://github.com/Steffenvy/Sprite-Skin-Transfer

 

Do you plan to implement the 2D equivalent of dual quaternion skinning?

 

I find the skinning UI a bit daunting. I'm used to complex animation ui's in 3d software, but when we enter the unity skinning editor, you can't click on any of the sprites, and each icon requires a rollover hover to see what it does, even so with no sprite selected on the sprite sheet, it seems no buttons do anything.

It's not very user friendly.

Actually I found the version from a few iterations ago with all the options as text was much more user friendly.

Even so, the default state is no sprites can be clicked. Feels like it is broken, but one needs to click random buttons to make things spring to life. Would appreciate this being far more verbose in UX, minimalistic has it's place and maybe in a complex animation interface minimalism isn't required.

 

Ah ok that explains a lot thanks! Maybe the interface needs an expand button to do the same command? I can't actually do shift + ` on my keyboard, as ` requires shift as it's on the same key as @ (SHIFT-JIS keyboard) - we can't activate text mode on non-us keyboards.


(I was able to reassign in shortcuts though )

 

Non-character question;

Is it possible to assign bones to multiple sprites on the same sprite sheet for different purposes? Like a bunch of trees for example? 3 trees on 1 sprite sheet with their own bones or do they need to be on separate sprite sheets each? I'm trying this and not having much luck.

 

If you give them different root bones and they're separate layers in photoshop, you should be good to go.

 

cc @Ted_Wikman

Looks like it's fine, I just needed to double click on the sprites!

 

I think I have found a bug with the Sprite Resolver.

This is what happens, I'm using Unity 2020.3.20f1 (+ latest 2DAnimation package):

1. Manual sprite swap works fine:
If you change a Sprite Resolver label manually (via editor-clicks) during runtime, the sprite is updated like so:

(Here you can see me swapping leg-outlines on this creature, and it's working nicely).

2. Sprite swap via script doesn't update sprite visually:
If you swap a Sprite Resolver Label via script during runtime, the Sprite Resolver will show that the new label is active, but it won't show up in the actual game, see this example:

(Here I've made a script that swaps to the "straight" leg-style at Start().
You can see the leg Sprite Resolver highlights as if the straight one is indeed active after the script is run, but what is shown in the game is the other more dog-like leg-style (as if the swap never happened)). In other words the Sprite Resolver did not update the sprite in game.)

For some reason changing a Sprite-resolver label via script won't update. Does anyone else have this problem, and knows how to fix it?
I'm thinking that it might be best if I report this as an official bug.

Thanks in advance!

Edit: I filed an official bug-report, you can find the link here:
https://fogbugz.unity3d.com/default.asp?1339554_016fr9mcm2gk6qml
if anyone knows a temp-fix I would love to know it!

 

Hello Ted,

Thank you so much for your quick and detailed reply! I feel embarassed that I reported a bug that was just an error in my code. I apologize for this.

You were absolutely right, as soon as I swapped the string it works just as intended.


I think part of why I didn't notice that my code was wrong was because there was no warning message when I used the wrong string. If something like "The label does not exist" popped up in the Console I think I may have spotted it.
Also I think another part is that in the editor (probably going back to the default sprite) the "Tootlet" label became highlighted, along with its sprite, so it looked like it had worked. This seems like it was just bad luck because I only have 2 sprites, and was trying to change to the first one.


This mistake/issue may not be common enough to consider adding a warning-message, but I just wanted to share how I missed it in case it's helpful! Adding a warning to make it explicit that an "error" is occurring could possibly alert users.

Again, I'm so grateful for your help. Thank you so much.
I'm sorry I reported the bug when it was my own mistake!

Hope you have a wonderful day!
Hulda

 

Those are some excellent points!

And indeed that was the thing that made me think it was a bug (that the editor had highlighted the "Label" category and the Sprite corresponding to "Tootlet" in the "Sprite Resolver" script, but these weren't shown in game). You can see it happening in the video I uploaded above (screenshot below):


Here the dog-like leg is active, but the script shows the straight "Tootlet" leg + highlights the "Tootlet"-sprite as active after the wrong string was passed.

Running the script with the bad string in the project I uploaded (in the bug-report) should replicate this happening.

It seems the Sprite Resolver just automatically highlights the "first" option in the Sprite-library if it can't resolve a string? And that the highlight then doesn't update/match what is shown in game? If this behaviour was tweaked (maybe highlights matched what's shown in game for example) I think that would help!

Also the bool-idea I think also sounds so useful for debugging-purposes (among others applications).

Thanks again : ) I have a lot of love for this asset!
Hulda

 

Should I make a new bug-report that more specifically points to that behaviour?
If it'd be helpful I'll be happy to do so

 

Thanks for putting in a fix so quickly and for informing me, that's awesome!
The Sprite Swap is such an awesome tool. I'm very happy that I had a part (even though it was a very tiny part) in finding a bug so it could be fixed

Have a great weekend!