Description
What problem does this solve or what need does it fill?
Current AnimationTransitions component is know to only be able to transition from current main animation to other nodes, in this case the API doesnt match the AnimationPlayer component. Which in many scenarios plays multiple animations . In this case I believe AnimationTransitions, should transition between nodes, as it will give a intuitive mannerism to softly handle node transfers without too much weight shenanigans.
What solution would you like?
Create an additional method, that lets you transition among AnimationNodeIndex. Get rid of the idea of one sole ActiveAnimation that exists in AnimationTransitions as that doesnt match an animation graph logic, usually it can have multiple ActiveAnimations
What alternative(s) have you considered?
In the current API, one could actually create N animation players each one handling N animation transitions. For me this feel counter intutitive. As this relation, could be represented with one sole Component.
Additional context
We would get rid of this idea I think, but for that we would need to get rid of the MainAnimation abstraction