Thanks, Richard. I did a profiler capture of the event playing in the Sandbox, and the parameter appears to behave correctly the first time I trigger the event. But, if I hit stop in the Sandbox (double or single click), and then hit play again, the parameter starts/holds at its destination value of 0, instead of starting at 1 again and advancing to 0 (at -0.5 units/sec). If I “remove” the event from the sandbox, and then trigger/re-add it, it behaves correctly again.
I should note that, for either scenario, I don’t see the parameter change in the Sandbox. I.e. when the profiler shows the parameter changing as expected, the Sandbox does not. Should it?
If what I’m seeing in the Sandbox/profiler is expected, is there a way for the programmer to trigger an event such that it will behave like how it behaves in the Sandbox (i.e. when I triggered it the 2nd time without removing it)? I’ll check how our programmer is triggering the event, but I don’t believe they’re doing anything special. I’ll also double check that they’re not manipulating this parameter, but I asked them to simply read the value and pass it to another event.