• Content Count

  • Joined

  • Last visited

  1. Thanks for the answer. If i'm right : X canvas means X PIXI.App ?? _______________________________________________________________________________ Wow, thank you VM for this huge example. I have never heard anything about PIXI.Runners. They look insane. It requires me to modify my global algorythm, but will for sure give me better comprehension of the code. I have a question about PIXI.runners. It says "A Runner is a highly performant and simple alternative to signals". How do they really work in an app. Are they something like WebWorkers ? How are they so "highly performant" ?
  2. Hi, I wonder what would be the best choice to manage multiple layers (some are mainly static, some are moving each frame). The layers are in fact the z index. Each layer contains approximatly 1k to 2k textures Example : [Z index 0] Background (Static) [Z index 1] Elements (Moving) [Z index 3] Foreground (Static) [Z index 4] Elements (Moving) ... more and more I have two options but can't find exactly which one would be the best. The goal is to be the most efficient for the client rendering action. I'm pretty new to Pixi and i maybe missed a magic component for my need 🤞 Solution 1 : Each z index is on a container and the stage renders all containers each frame Solution 2 : Manage multiple canvas and each canvas refers to a specific z index. Only edited stages are rendered each frame Solution 3 : Any other solution ? 😁 Thank you