If I’m automating a lowpass cutoff from two parameters (say distance and direction), how does the final cutoff get calculated?
From experimenting with it, it seems only one parameter controls the cutoff at once, but the other can take control if the other parameter is at a certain threshold value.
Is this intended? Should I create a user parameter and work out the overall cutoff in game code and change this parameter?
Thank you in advance!
When a lowpass effect’s cutoff property is automated by two different automation curves, the final value of that property is the lower of the two values dictated by the curves. In other words, when the two automation curves each specify a different value for the cutoff property, the lower of those two values is the one that’s used.
Incidentally, the method by which having multiple automation curves on the same property is handled varies from property to property. For example, when a lowpass effect’s resonance property is automated by two different automation curves, the final value of that property is the higher of the two values dictated by the curves.
Hi Joseph,
Thank you for the reply.
The behaviour makes sense now you’ve explained it.