Hello everyone, I’m trying to stop a MetaSound via BP and it seems like the Execute Trigger Parameter is not working. I am sending Booleans or Float Parameters and they work just fine, but not the Triggers.
Here is a snapshot and hopefully someone could tell me what am I doing wrong?
Oh, they work. It’s just that I have some triggered delays after that are not stopped when “StopAll” trigger is received.
Nope, they don’t work.
they absolutely work, have checked by this .
need to double-check that “TriggerName” in the Inputs members category
I have, it 100% is not working for me.
@MeddleGearSalad Can you show your setup for we can see if there is anything obvious?
I had this issue, it only worked if I used exactly this setup:
The MetaSound is placed in the scene, with the Trigger as an Input (not a Variable) within the MetaSound definition.
In the blueprint, I have an Ambient Sound variable which is tied to the MetaSound instance in the scene, and I call Execute Trigger Parameter on its Audio Component.
Crucially, calling Execute Trigger Parameter has no effect if you call it on the AmbientSound (scene object) directly, you have to fetch the audio component.
The trigger path is different from the other params — you need Execute Trigger Parameter, not Set Bool/Float, and the metasound must be in a playing state when you execute it. Also double-check the trigger Input is exposed as a trigger type in the graph, not bool — mixing those fails silently.
I wrapped that plus the other Set nodes into one consistent API so you dont have to remember which is Execute vs Set: Expose MetaSound Parameters To Blueprint. Same engine call underneath, just one node per type and a component that auto-finds the AudioComponent. Disclosure: my plugin.
