GPU particle systems and targetStopDuration

[Evgeni_Popov]

@julien-moreau

The PS always returns “true” when calling ps.isStarted() even when the stop duration is reached and no particle drawn anymore. Maybe this is expected but this behavior is different from classic ParticleSystem implementation

I think it’s because of:

GPU Particle System - Particles remain alive after stop()

This is expected: GPU particles cannot be removed from the CPU (well we can but it is overly expensive). Hence the choice to simply skip the stopped ones By the way, it does not generate additional draw calls as the GPU particles are all rendered in one draw call

GPU particle system start delay if active particles is "full"

Hi everyone! I’m struggling a bit with my gun muzzle effect, trying to use particles with that. I have a pooling system for particle systems, so my muzzle gpu particle system is stopped after a really small time and then reactivated some time later when a gun is shot again. However, I struggle to start the system exactly when the start function is called. I do preheat the system as well. I don’t really know if I’ve understood something wrong or where the problem is Her…

Particles are not removed from a GPU particle system, they are just skipped when they are not alive anymore, so isStarted for a GPU PS always stays true after it has been started.

@julien-moreau

Once stop duration is reached, impossible to start the system again. The only ways is to set _actualFrame = 0. This behaviour is also from the one implemented in ParticleSystem class.

This one is probably a bug, as this._actualFrame = 0; is done in the start function of ThinParticleSystem but not in GPUParticleSystem:

GPU particle system: Reset actual frame when starting the particle system

Thanks for reporting!

(note that you can do particleSystem.isStopped() instead of particleSystem["_stopped"])