Blend Weirdness in Unity 3.5?

Guts

BinaryCats wrote
We have alpha in 3 days. We are just sticking with the bugs, and fixing what bugs we can.

The problem with downgrading is if your animator has made new animations and saved them in 3.5. as, and I may be wrong, I believe older runtimes will not support these animations (?), so you will have to downgrade spine, then do some magic to get the new animations in the older version of spine. As spine version 3.4 can not open 3.5 .spine files

I was actually using 3.5 editor with the older runtimes for quite some time. I got a warning whenever Unity imported skeleton data, but no actual bugs emerged in the game. (Your experience may vary :wait: )

I'm going to make a backup and take the plunge back to 3.4 after everything else I need to do is done.

BinaryCats

goodluck

Nate

You can just go back to the 3.4.02 AnimationState (with minimal changes) and continue using the 3.5 editor and the rest of the 3.5 runtimes.

December 13th, 2016, 11:56 pm

I gave the modifications I posted a whirl and it didn't work as intended. I tested it when I wrote it, so that's odd. Here's the fix:
https://gist.github.com/NathanSweet/3aaeb489c2e8cdca76b31f5ae87f2b8b

This is an experimental AnimationState which fixes dipping and disables multiple mixing from. See the Gist history to go from the master branch AnimationState, to one which fixes dipping, to one which also disables multiple mixing from.

You should not see dipping, but you will see snapping when interrupting a mix because there is no multiple mixing from. That snapping happened with the old AnimationState, so you should be no worse off. Hopefully this helps!

Pharan

Updated the C# version. same link. https://gist.github.com/pharan/cffdc3b2aee9288c9ca8b4ab94ee97d2

If you're not familiar with gist/github, make sure you click on Raw to get the plain text version instead of the formatted page. Makes for easier copying.

To use it, copy the contents of this version of AnimationState.cs, and use it to completely replace the contents of the AnimationState.cs in your project.

flashframe

Thanks for this. I will give it a try too!

Guts

Will report back after I get around to implementing this. Thank you!

flashframe

Hey, so I tried the edited version of AnimationState, and it does fix the dipping problem.

But I do also see snapping between some animations. I know you said it was there before Nate, but opening up my project with the old runtime I don't see it.

I think it might be because I spent a lot of time previously writing scripts with little quirks and workarounds to fix little problems like snapping, and now with the update some of these issues are redundant, but it seems other ones have popped up (or at least my workarounds don't work anymore). So I think I'm personally probably best off sticking with the old runtime and Spine 3.4x.

Would be great if you could find a solution to the Holy Grail: multiple mixing from AND no dip!

Thanks!

Nate

Thanks for trying it. It's expected to see snapping if you interrupt a mix. Are you seeing snapping at other times? Can you reproduce it in the Skeleton Viewer so I can see it?

BinaryCats

It still happens for us 🙁 on latest unity package. Do I need the experimental thing?

3.5+ Attachments And Mixing <- is the problem

19 Dec 2016, 10:51

oh.. I used the above animationstate.cs and it somewhat worked. The blend time looks very long now though compared to what it use to be :S :wonder:

Guts

My mixing issues have inexplicably vanished without addressing it. :wonder:
I must have inadvertently changed something in my implementation that phased out the emergence of the bug in my project. Maybe it was something to do with eliminating all uses of timeScale = 0...that was the only major thing I changed.

Carl

Experimental code is still dipping if you're swapping animations before mixing has finished. I'll put a minimum delay to animation swaps for now.

BinaryCats

I broke the experimental code IK Mix over Multiple Animations in Quick Succession

RemDust

Hi there !
We've been creating a LOT of animations in Spine Editor these last weeks and haven't been playing 'em runtime in Unity yet.
Can someone update me about the dipping/blending/whatever issue between animations, is it fixed now ??? ^^

BinaryCats

mostly fixed with the above code from pharan, only side effects seems to be my other post

Pharan

Note the experimental AnimationState.cs was updated to fix some glaring problems noted in bcat's thread.
If anyone is still experiencing weirdness since last time, please try the latest.

Here's the link again.
https://gist.github.com/pharan/cffdc3b2aee9288c9ca8b4ab94ee97d2

08 Mar 2017 3:46 pm

Updated the experimental AnimationState.cs again. This should have much better results.
Do give us feedback or report any weirdness.

BinaryCats

What does the update fix? Is it worth potentially breaking everything?

09 Mar 2017, 14:32

yeah.... that update is by far the worst update in spine history :s. It totally breaks our character. idle>jump>fall>idle looks like it keeps the fall position of the legs but with the key frames of the idle being applied.

Ill try to get a gif for you

09 Mar 2017, 14:40

previous experimental (expected result):
Loading Image

Newest:
Loading Image

09 Mar 2017, 14:42

looks like the iks don't get turned on

Nate

It's a cool limp effect! 😉

Phaaaaaaaran! :bang:

Pharan

It fixed the other guy's basic use problem. So amazing.
Setup pose effecting skeleton when mixing interrupted

Nate

We have now fixed the "dipping" problem by making multiple mixing optional and disabled by default. You can now choose between multiple mixing with the dipping problem (always smooth transitions, especially useful for long mix times), or no multiple mixing and no dipping problem (only mixes 2 animations at once, interrupting a mix with a new animation can cause a jump).

The commit is here:
Fixed the dipping problem by making multiple mixing optional and disa…@13c34e8

The documentation comment here explains the ramifications of the new setting:
spine-runtimes/AnimationState.java at 13c34e8751aedd48d7914c0e0ff58a322424c18e

Currently this is only in spine-libgdx in the 3.6-beta branch, but we'll get it ported to all other runtimes soon. It will stay in the 3.6-beta branch until the 3.6 release when it gets merged into master, that way 3.5 users don't get an unwelcome surprise from the significant change in behavior. However, it should work just fine with 3.5, so you can likely grab AnimationState from 3.6 and replace the same in 3.5 if you want.

BinaryCats

So the fix is to remove the feature? Lol

« Previous Page