Particle System Improvement

[ghost]

Godot's particle system is very simple and does its job very well, but some things can be added to it:

• Random lifetime
• Collision
• Take out the delay it takes to emit particles when emitting is marked or make a emit() function
• Array of colors to choose randomly
• Fix randomness "bug" where if the param is 0 it doesn't do anything. Suggestion: make it more controllable, like if I put direction 10 and random direction 5 then it do 10 + randi_range(-5, 5)
• Graph of size during lifetime

Off topic: add randi_range(min, max). No more cyber-bulling to integers!

[Sslaxx]

Seen #6235 then, regarding the random numbers?

[rgrams]

IMO each particle parameter should be input as a Vector2: Max and Min. That would be easy and let you choose any range you like.

[rgrams]

See also #3994, #4003, and #4294

[freemanfromgodotengine]

I will add to this particle improvement general subject.
It would be great if Godot particle system was able to do things similar to Hayate Particle Turbulence that was available in Unity's Assetstore for previous version of Unity.
Especially two features:

• particles "turbulence" generated from Sine, Cosine, Perlin, Animation Curves, Textures and Audio.
• particles leaving trail.

Watch it in action on https://youtu.be/vG-0RO7e48U

There was a similar request before, so also add #4250

[reduz]

currently working on new particle system, this kind of stuff will be possible

…

On Fri, Jan 6, 2017 at 8:34 PM, Freeman ***@***.***> wrote: I will add to this particle improvement general subject. It would be great if Godot particle system was able to do things similar to Hayate Particle Turbulence <http://maxproude.com?p=160> that was available in Unity's Assetstore for previous version of Unity. Especially two features: - particles "turbulence" generated from Sine, Cosine, Perlin, Animation Curves, Textures and Audio. - particles leaving trail. Watch it in action on https://youtu.be/vG-0RO7e48U There was a similar request before, so also add #4250 <#4250> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#6377 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AF-Z25QMvHBliyfCBrWpMPYP4FCbMDdYks5rPs98gaJpZM4J0DEg> .

[ghost]

First of all thank you for your report and sorry for the delay.

We released Godot 3.0 in January 2018 after 18 months of work, fixing many old issues either directly, or by obsoleting/replacing the features they were referring to.

We still have hundreds of issues whose relevance/reproducibility needs to be checked against the current stable version, and that's where you can help us.
Could you check if the issue that you described initially is still relevant/reproducible in Godot 3.0 or any newer version, and comment about it here?

For bug reports, please also make sure that the issue contains detailed steps to reproduce the bug and, if possible, a zipped project that can be used to reproduce it right away. This greatly speeds up debugging and bugfixing tasks for our contributors.

Our Bugsquad will review this issue more in-depth in 15 days, and potentially close it if its relevance could not be confirmed.

Thanks in advance.

Note: This message is being copy-pasted to many "stale" issues (90+ days without activity). It might happen that it is not meaningful for this specific issue or appears oblivious of the issue's context, if so please comment to notify the Bugsquad about it.

[Sslaxx]

#7199 - related to this issue - is still open.

[akien-mga]

If some of the features proposed here are still relevant in the current master branch, I would suggest to add them to this tracker: #20473.