Animation copying from armature a to armature b for temporary usage.
In short armature a can play an animation from armature b if they have the same skeleton data.
This can be used to split animations in different files instead of keeping them all in a single project same way dragonbones did it:
This is great for games where the character has a lot of animations and animated clothes,weapons too and you dont want to load them all but only the ones he equipped or when you dont want to share a project with all your existing animations with a freelancer but give him an empty one with the skeleton base on it and he adds the animation u commissioned him for.
In short armature a finds the animation it wants to use from armature b and copies it's json to play it inside itself.
This is a repository of a fork of the spine-pixi runtime to make it work on PixiJS v8.
That's not the right place to discuss about this. You should open a thread on the Esoteric Software forum.
Animation copying from armature a to armature b for temporary usage. In short armature a can play an animation from armature b if they have the same skeleton data. This can be used to split animations in different files instead of keeping them all in a single project same way dragonbones did it:
This is great for games where the character has a lot of animations and animated clothes,weapons too and you dont want to load them all but only the ones he equipped or when you dont want to share a project with all your existing animations with a freelancer but give him an empty one with the skeleton base on it and he adds the animation u commissioned him for. In short armature a finds the animation it wants to use from armature b and copies it's json to play it inside itself.