Description

Trigger Delay is not behaving as described in it's current tooltip, i.e. "Executes output trigger after the given delay time from the most recent execution of the input trigger." Namely, it is outputting a trigger for every execution, not just the most recent one.

(While outputting a trigger for every execution is sometimes desirable, that's what the Trigger Pipe node is intended for. At the moment these two nodes behave exactly the same way, and they should not.)

Steps to Reproduce
  • Create a MetaSound
  • Add a Trigger Delay Node
  • Make a Trigger Input, and attach it to the In pin on the Trigger Delay
  • Simulate the Trigger Input, and then Simulate the Trigger Input again before the Trigger Delay time elapses
  • Watch the connections between the nodes to see when the triggers get sent

Expected Result:

  • Only the most recent input trigger gets delayed, e.g., there is one pulse that occurs at the delay time after the second simulate

 

Actual Result:

  • Both trigger inputs are delayed, leading to two pulses, one shortly after a recent trigger message

Have Comments or More Details?

There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-183510 in the post.

3
Login to Vote

Fixed
ComponentUE - Audio - MetaSounds
Affects Versions5.15.2
Target Fix5.4
Fix Commit30848985
Main Commit30849050
CreatedApr 17, 2023
ResolvedJan 24, 2024
UpdatedMar 19, 2024
View Jira Issue