Request for multi-animation spine setup - with independent c

Bam

Request for multi-animation spine setup - with independent control

The objective is to have a two or more animations in the same spine file / project, while being able to control them independently of one another.
Take the following example:
We have a spine project with 3 states / animations (we’ll call them A, B and C)

Now consider that we want to produce a scene where we have this setup instanced 3 times. Normally / currently, we have to load the animation 3 times. Thus, we can apply the desired state for each of the three animations, independently of one another.

However, this comes with the negative aspect of having a draw call for each spine animation. Grid of three? Three draw calls. Grid of thirty? Thirty draw calls... 
In theory, I would wave a magic wand, and produce the following scenario:

I would make one spine project, have all three instances setup inside it, and have independent control over each one, therefore obtaining the same visual result, but with only one draw call.

Any wizards out there who can either:

Disprove the idea. It is impossible to do. No way to trigger one animation from the spine project, without affecting the state of another. Then I can just go and cry in 30 draw calls.
Or it is possible, and I just need to learn more, do some magic setup, which will enable this, and then I can laugh in 1 draw call ^_^

Thank you!

Nate

Bam wrote
Now consider that we want to produce a scene where we have this setup instanced 3 times. Normally / currently, we have to load the animation 3 times.

This appears to be where you've gone off the railroad tracks. You never need to load the same skeleton data multiple times. Please see the class diagram here:
Runtime Architecture - Spine Runtimes Guide: Class diagram
You can have any number of skeleton instances that all share the same skeleton data. The setup pose data is stateless (which includes all animations, skins, attachments, etc). Only the data in the "instance data" box in the diagram is created per skeleton instance.

Note you mentioned "animations" several times, but I think you meant "skeleton data". You never "load an animation", rather you load skeleton data which can have many animations.

Regarding draw calls, it depends on both your game toolkit and how you use textures. Ideally all your images fit in a single texture, then you are only limited by how the game toolkit of your choice works. Note you can have many different skeleton datas use a single texture atlas.