Hi!

Today, I have update my runtime to latest version on Git (2.5 up from 2.3). Everything was working fine before the update but now my code for mixing animations seems to be broken (code that I did like a year ago). Please, take a look:

void runAnimation(SkeletonAnimation *skeleton, int trackIndex, const string &animation, bool loop, bool mix, float mixTime)
{
    string current = "";
    spTrackEntry *entry = skeleton->getCurrent(trackIndex);
    if(entry != nullptr)
        current = entry->animation->name;

if(current == "" || !mix)
{
    skeleton->setAnimation(trackIndex, animation, loop)
}
else
{
    skeleton->setMix(current, animation, mixTime);
    skeleton->setAnimation(trackIndex, animation, loop);
}
}

Currently, it seems that setMix function is not working as intended because it is interpolating between the setup pose and 'animation' instead of doing it between 'current' and 'animation'. I want to clarify again that my code was working prior the update. Please, can you take a look and tell me if this is ok? In case it is working as intended, can you explain me how my code should look?

Thanks in advance!!

Regards,
fryderyk

Hi again!

I have noticed another rare behaviour after updating.

We have a character that has a run animation (which moves the right arm) playing on trackIndex 0, I will call it "A" animation. When there is some user input, it plays a right arm animation on trackIndex 1, I will call it "B" animation. Before the update, everything was working as I expected. The A animation plays correctly, then a B animation is triggered by user which overrides the A animation for the right arm (because it has a greater index) and when the B animation is finished, the right arm recovers its animation from the A animation.

However, after updating, when B animation finishes, the right arm doesn't keep playing A animation anymore. The arm just keeps the state of last keyframes of B so the right arm doesn't move anymore by A animation. I don't know if the new AnimationState is built to work like that or there is any bug concerning this... like I said in the first post, if the new behaviour is correct, can you tell me how can I reproduce the old one?

Thanks in advance!!

Regards,
fryderyk

Ohh I see, so now we have a more powerful AnimationState. That's nice!

Eagerly waiting for the commit to choose between behaviours, so we will be able to switch to the old one and not having to rework anything. Keep up the good work!!

Regards,
fryderyk

Good and not so good news.

First issue has gone, yoohoo!

Second issue is still there. I have commented the setMix line (so there is no mixing at all) and the problem continues so it is not a problem about the setMix function. Any ideas?

Thanks!!

Regards,
fryderyk

Thanks Nate! That's exactly what I needed. Sorry for misundertanding the new API

Anyways I can see a bit of flickering between animations if I do

entry->trackEnd = entry->animation->duration;

I tried with this

entry->trackEnd = entry->animation->duration + 0.1f;

and the flickering disappeared but it's more a nasty workaround than a nice solution... Do you have a cleaner way to do it?

Again, I have to thank all Spine team for the nice support to us developers
Good job mates!

Regards,
fryderyk

Sorry for the delay Nate, weekend is sacred for me!

I have to record it with my phone because it is only a frame but the setup pose can be seen between animation "A" and "B" if I run this code:

spTrackEntry *entry = skeleton->setAnimation(index, "A", false);
entry->trackEnd = entry->animation->duration;
skeleton->addAnimation(index, "B", false);

The result is: A plays correctly, setup pose plays for 1 frame, B plays correctly.

I know the second line is not necessary in this case but this is a simplified version of my code. On real version, when A animation is set to play, I don't know if a B animation is going to be played so I must be sure that track is cleared when A animation is done (if not I have the "fixed arm" case I explained on the other post).

Any ideas?

Regards,
fryderyk

Thanks Nate!! That fix seems to solve all my animation issues!

Regards,
fryderyk