Different behaviour for cpu and gpu particles after stop() call

Bugs
1

Hey guys,

Comment/uncomment 26 line to see difference between cpu and gpu behaviour after stop(). There is a timeout func to stop after 2 sec. As user i expect cpu behaviour to be correct.

3

Also looking.

4

Hey @TooCalm , both issues you reported have the same root cause, and it is a known difference of behavior between GPU and CPU particles. I am discussing internally what to do in this case, but I am going to wait until Deltakosh is back next week to land on a final decision with him.

1 Like
5

cross ref Different behaviour for cpu and gpu particles regarding emit rate

1 Like
Different behaviour for cpu and gpu particles regarding emit rate
6

This is now addressed on this PR:

Option for GPU particles to behave like CPU particles by VicenteCartas · Pull Request #18057 · BabylonJS/Babylon.js

Because the current behavior is already shipped and we don’t want to break code that depends on it, the “fix” is optional: you will need to pass a new parameter in the GPUParticleSystem constructor options: emitRateControl: true. This will make the GPU particles behave more like CPU particles in their emission.

Example PG (will work when this change is deployed):

different behaviour for cpu and gpu particles | Babylon.js Playground

2 Likes