You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In bullet_particles.gd, the finished signal is connected to the on_finished() method, where the particle system is then queued for deletion. However, this never executes. For some reason, the GPUParticles2D never emits the finished signal.
The workaround I did for now is to define a "dying" variable at the top of the class and initialize it to false, and then change the _physics_process code to:
I believe the reason the finished signal doesn't get fired is due to the particle system not being one_shot at the beginning of its life, but I'm not 100% certain.
To fix this issue the tooltipp of "finished" hints: This signal is never emitted when one_shot is disabled, as particles will be emitted and processed continuously.
Setting checking the box on "one_shot" to on and in _ready() setting emitting = true will queue_free() the particles.
I alse notice the bug. I ask gpt, got the reason: Scene with a BulletParticles root will reparent root automaticaly by godot, I almost believed it!
Then I found this issue, and notice the bullet_particle.gd script (I even didn't notice the little script)......thank you
Activity
fred-eric-rieg commentedon Oct 23, 2025
Your final thought is on spot!
To fix this issue the tooltipp of "finished" hints:
This signal is never emitted when one_shot is disabled, as particles will be emitted and processed continuously.
Setting checking the box on "one_shot" to on and in _ready() setting emitting = true will queue_free() the particles.
fkjkkll commentedon Dec 5, 2025
I alse notice the bug. I ask gpt, got the reason: Scene with a BulletParticles root will reparent root automaticaly by godot, I almost believed it!
Then I found this issue, and notice the bullet_particle.gd script (I even didn't notice the little script)......thank you