Particle Emitter Enhancement

Alaiz · October 3, 2022, 9:48pm

I propose in the case of life cycle of the particle emitter instead of having a life cycle with two stages (Start and End) we could have a life cycle with several stages according to our needs

Peek 07-07-2022 14-423

I showed an example but it can also apply to color, opacity, and size.
Of course you don’t have to do the same thing, you can also use the collision mask of the sprite object as a template to create a new stage in the life cycle of the particle, as shown in the graphic below. Peek 07-07-2022 14-51

davy · December 27, 2022, 1:19pm

Particles are rendered with a PIXI plugin.
The documentation gives an example of configuration. The properties can be set the same way as your mockup.

Note that the documentation example uses the V3 configuration but GDevelop currently uses the V2 configuration:

github.com

4ian/GDevelop/blob/master/Extensions/ParticleSystem/particleemitterobject-pixi-renderer.ts#L71


      
          
          
// Render the texture from graphics using the PIXI Renderer.
          // TODO: could be optimized by generating the texture only once per object type,
          // instead of at each object creation.
          const pixiRenderer = instanceContainer
            .getGame()
            .getRenderer()
            .getPIXIRenderer();
          //@ts-expect-error Pixi has wrong type definitions for this method
          texture = pixiRenderer.generateTexture(graphics);
          const config = {
            color: {
              list: [
                {
                  value: gdjs
                    .rgbToHexNumber(
                      objectData.particleRed1,
                      objectData.particleGreen1,
                      objectData.particleBlue1
                    )
                    .toString(16),

The last update of the plugin in GDevelop was done in Jul 19, 2020:

github.com/4ian/GDevelop

Upgrade to Pixi.js 5.3.0

4ian:master ← 4ian:pixi-v5

opened 01:15PM - 18 Jun 20 UTC

4ian

+6974 -1187

First, **thanks again to @Quarkstar** for working on the original PR #1628 (the …PR will be merged in master using a rebase to ensure the commit is properly attributed). Let's discuss/work here on what is needed to make Pixi.js v5 work perfectly with GDevelop - notably filters. @Bouh if you want feel free to make a list here of what you think need to be done before we consider this branch ready :) @HarsimranVirk You can now surely start from this branch `pixi-v5` and cherry pick your commits on top of it :) If you open a PR, you can choose to use `pixi-v5` as the "base" branch, instead of `master`, so that only your commits are shown in the PR.

There is no mention of the version of the update but I believe it can be used with the V3 configuration (we still use the V2 because they kept it compatible)

The feature would require to:

use EmitterConfigV3 instead of V2 in particleemitterobject-pixi-renderer.ts
create a new model for the emmiter object configuration and keep a compatibility with existing configurations in ParticleEmitterObject.cpp
create a new UI in ParticleEmitterEditor.js

It can be done but it’s not a small task.