I recently started trying to implement Niagara FX and ran into a problem.
I’m not sure if this is a problem when how I’m trying to implement my FX, but when I try to deactivate or destroy my component it doesn’t seem to behave the same as with cascade.
First of all the ‘Destroy Component’ node doesn’t even seem to do anything.
Secondly the ‘Deactivate’ node seems to be acting the same as the destroy one.
So am I doing something wrong? Is there a node I’m not aware of? Or is this some sort of Niagara quirk?
I had the same issue just few days ago and what I did was:
Create a user variable in the Niagara emitter linked to the Particles.Lifetime (User.Particles.Lifetime) and then set this Niagara Variable (Float) to Zero in Blueprint to deactivate it.
Not sure if there is another option to really destroy Niagara emitter (for performance reasons…to release it completely from memory).
I just looked into this and thought I’d put my findings here in case somebody else finds this thread.
In the ‘System State’ section and the ‘Emitter state’ section, there is an option called ‘Inactive Response’. As long as this value is not ‘Continue’, the system will die after doing its job.
If the system or emitters are set to spawn infinitely, the ‘Inactive Response’ is set to kill it if particles cannot spawn. By using the ‘Deactivate’ node, the system cannot spawn particles, and thus it will be automaticaly killed.
Well, in my case for example, I have a vehicle that starts to emit smoke and later fire after a certain amount of received damage. But once the vehicle is destroyed and respawns, the niagara system should be deactivated by deactivating the actor. Yet I cannot deactivate the actor, since it’s the player character. So even after respawn the NPS just keeps firing.
