pixi.js Pixi.js - Get Values of Container, Without Inheriting Z

[KanaX]

I'm fairly new to pixi.js and programming altogether.

I am making a plugin that parses the xml save file of a sprite animation program and recreates the result in a game engine.

The animation program uses bones for skeletal animations and the images (sprite parts) inherit the x, y, angle, scale_x, scale_y of the parent bone.

The main idea would be to create sprites for the bones and the images, set up the bone inheritance to make the skeleton animation work correctly and then addChild the image sprites to the respective bone sprites. The only problem is that along with the aforementioned values, my image sprites also inherit the z_index of their container. The spriter does not limit the z hierarchy of the images to that of the parent bones, meaning that the user can change their z.

I attempted to use worldTransform and worldAlpha for the parent bone values (keeping all the image sprites in a single container, thus controlling the z_index), but I am unable to get the parent bone's rotation.

So, I either need to get all the values of the container and apply them correctly on the image sprites, or keep the image sprites inside the container and find a way to change their world z.

Any suggestions would be appreciated and I thank you for your time.
 

 

[ivan.popelyshev]

Make bone structure separate, or just use https://github.com/pixijs/pixi-display/tree/layers (new branch of pixi-display) , it can sort elements in a subtree.

As a first implementation it will work fine: you need to put a Layer container inside your object and assign all the attachments z-index and parentLayer. Also your stage must be PIXI.display.Stage, anyway look through examples.

Then you can make separate structure of bones and transforms, like in https://github.com/pixijs/pixi-spine and https://github.com/EsotericSoftware/spine-runtimes/tree/3.6/spine-ts

[KanaX]

@ivan.popelyshev Anything I can do without external files?

[ivan.popelyshev]

PIXI does not have any built-in sorting tools. Use "display" for first working version because its easy to do, then study spine code and implement same approach in your plugin.

[KanaX]

@ivan.popelyshev After some tweaking and some help I managed to make your plugin work. Thank you for your help.

[ivan.popelyshev]

Good! Later, when you have enough time, you can figure out custom solution that'll be more performant.