@TheBiter Thanks for the detailed writeup. I just discovered that I overlooked that the test Timeline which I inspected had more animation clips following hidden to the right of the window (requiring scrolling), while I thought it had been the last clip already. My bad.
We have created an issue ticket here for this issue:
EsotericSoftware/spine-runtimes2318
We will get back to you here on the forum as soon as we have a fix to offer.
Thanks for reporting!
It's cool. I have a "good enough" workaround in the meantime to alleviate the behavior for our project.
I also just noticed a different issue with the latest spine timeline package v4.1.10 that is hard for me to properly explain. It might be a result of the fix I requested for nonlinear traversal but when I have sequential clips in the timeline now (without any clip mixing overlap), the first clip's animation reference is ignored and the one located in the following 2nd clip is used instead. This only happens for the first SpineAnimationStateClip in the sequence as any following 2nd or 3rd or 4th clip seems to behave as normal.
I'll be sending a sample reproduction project built upon my previous one with multiple playable directors and timeline assets in them to show off the behaviors in separate scenes. I've also bundled up the Clip End Mix Out Duration issue in there as well with the workarounds I've discovered in a separate scene.
Thanks again for being so quick and responsive.
It's cool. I have a "good enough" workaround in the meantime to alleviate the behavior for our project.
BTW: If you enable the clip option Don't pause with Director at your last clip, it will also mix out to the empty animation. Just in case that helps.
TheBiter I'll be sending a sample reproduction project built upon my previous one with multiple playable directors and timeline assets in them to show off the behaviors in separate scenes.
Sorry to hear you've encountered another problem. Thanks in advance for sending the reproduction project!
Harald BTW: If you enable the clip option Don't pause with Director at your last clip, it will also mix out to the empty animation. Just in case that helps.
AH! Yes, I'll keep that in mind. Thanks for the heads up.
Harald Sorry to hear you've encountered another problem. Thanks in advance for sending the reproduction project!
It's all good. I'm more concerned about other people grabbing the latest version and finding out they can't chain clips together.
@TheBiter We just fixed the newly intrduced issue with this commit.
New 4.1 and 4.2-beta UPM packages are available for download:
https://esotericsoftware.com/spine-unity-download
Thanks again for reporting!
We will now investigate the remaining Clip End Mix Out Duration issue.
Sorry for the delayed reply. So far in my tests with the new package and our non-linear timeline implementation, it all seems to be working great. I'm able to loop variable amount of times without issue and all the regular timelines are working fine as well. Thanks again for the fast turnaround!
I'll keep an eye out for the Clip End Mix Out Duration whenever you guys get that resolved. In the meantime our workaround is good enough. Many thanks!
@TheBiter We have just released an official bugfix for the Clip End Mix Out Duration issue. Timeline clips should now behave as the paramter names imply and follow the documentation again. Please let us know if this resolves the issue on your end as well. If you encounter anything else that behaves unexpectedly, please don't hesitate to let us know. Thanks again for reporting!
Updated 4.1 and 4.2-beta Spine Timeline UPM packages are available for download:
https://esotericsoftware.com/spine-unity-download
So in my testing reproduction project, I pulled down the latest package to test out the Clip End Mix Out Duration setting and it seems to work as expected now for the final clip, which is great.
I took a look at the logic that was changed and to me it looks a little confusing. Namely line 71 in SpineAnimationStateMixerBehaviour where it says bool isStoppedNotPaused = playable.GetGraph().IsPlaying(); // end of track was reached or graph stopped.
The observed behavior does seem to work as advertised but I just wanted to make sure this is the intended logic. From just reading the code one might assume the logic is reversed but with the way the timelines fire off the event timings, it's probably correct logic but just looks unintuitive.
Again thanks a bunch for the help! I believe all my issues have been resolved.
@TheBiter Thanks very much for the quick feedback, glad everything behaves as expected now!
TheBiter The observed behavior does seem to work as advertised but I just wanted to make sure this is the intended logic.
Thanks for taking a considerate look and sharing your concerns. The Unity Timeline API is unfortunately not always quite intuitive, as this example shows 
. Unfortunately OnBehaviourPause and OnGraphStop are both called in succession upon pausing or stopping the graph. The only way we found to distinguish whether these two successive calls are coming from a pause or stop event is that playable.GetGraph().IsPlaying() is returning false when paused and true when stopped.
Harald The only way we found to distinguish whether these two successive calls are coming from a pause or stop event is that playable.GetGraph().IsPlaying() is returning false when paused and true when stopped.
Haha I figured something strange like that was going on since I too have seen very unintuitive behavior when stepping through the timeline code. Thanks for all the help!
