Search the Community
Showing results for tags 'containers'.
Found 5 results
-
I could replicate this issue in this CodePen https://codepen.io/mariogarranz/pen/Yzqjboj In this example I create one ParticleEmitterManager and it into a Container that had its scale modified. Then I add 3 ParticleEmitters to this ParticleEmitterManager, all of them with the exact same settings, but everytime a new ParticleEmitter is added, some offset is added to its positioning and scaling, so in the end you can see all 3 of them in different spots and scales. This seems like a bug to me, but maybe I got something wrong? My game uses a container with a scale for the board of the game and it's being impossible to have the particles display properly over it, unless I use 1 ParticleEmitterManager for each ParticleEmitter, which seems too overkill. -
Been working with Pixijs for a month of so now and haven't found a good way of identifying sprites or containers in other containers. How do you get or adjust sprites and containers within containers? I'm been looking at: .getChildbyName but what name? And .getChildAt but how do i identify it amongst many other objects that could be returned? is there a design pattern I'm missing here, or a built in id for each created sprite that I can use to lookup or a name that I can assign? Cheers.
-
Hi, I have 3 containers containing only square sprites as children of stage. Starting from the 3rd, every new container I add is offset by 8,8 visually but all of their properties say they aren't. To achieve the expected result I have to set the position of the 3rd Container to -8,-8 or else the black shape is offset. When I check getGlobalPosition of the container or the sprites in it they tell me they're not offset when they clearly are. (game.layers is just a POJO that contains references to the containers)
-
Hi, So finally Phaser 3 is going to provide containers? I am a bit confused about it, I remember that to keep a flat display list is a design desition that allows a lot of performance and simplicity. At the same time, we need something like containers or bones, something like a transformation tree. In this Phaser 3 google group I mentioned it: https://groups.google.com/forum/#!topic/phaser3-dev/jNb_9i0_EpE ...and proposed something like Joints, this was the Richard answer: So, if now containers are introduced, how much is it going to affect the internal Phaser 3 implementation? Is it going to affect performance? is it going to use two different display list, one flat and other nested? Why are we considering containers again? Best regards, Arian
-
Hey guys, just a really quick question on containers. I see that you can use a PIXI.particles.ParticleContainer. In the documentation is says that it doesn't support features such as tinting, alpha, masking etc.. However, as this class is extending from the normal Container, I am curious as to what is different, and how it achieves this. Thanks, Nick
