Sequence events fire twice?
In working with the new level sequencer within release 4.12.5, I have discovered that the events on an event track fire twice? I'm not sure if this is the intended behavior but it certainly creates problems for blueprint scripts attached to the associated custom events that are only expecting it to fire once. There is already a bug(Level Sequence Event Duplicate Bug) that described this behavior but its resolution was lack of follow through. And that's not adequate since there was really no answer if this is correct behavior or a bug. IMHO this should be a bug. Below is how I produce the issue in a brand new 4.12.5 project on Windows 10.
First create a simple scene with a sphere and add a level sequencer to the scene. Open the level sequencer editor and create a simple movement animation as seen in the image below. Next add an Event track and place a event at the 1.0 second mark(30 frames). Name the event using the properties by right clicking it.
Now open the level blueprint and duplicate the setup below. Be sure to name your custom event to the same name as was used in the sequencer event track. Mine was named Event1. I wired the P key to allow the sequence to be played again and again.
Now if you play this project and press the P key(or whatever key you wired up), you will see sphere move as expected but you will notice that the PrintString attached to the custom event(Event1) will actually print twice. Setting a breakpoint on the PrintString and pressing the P key again also confirms that it hits the PrintString node twice.
Note this is hard to work around because there is a timing element to it. You basically need to ignore the second event if it occurs within a certain delta time. Doing this really complicates the event handling is definitely not the preferred solution. I hope this issue can get some attention as we use this behavior extensively. Thanks.
asked Jul 09 '16 at 07:46 PM in Bug Reports
Thanks for the detailed bug report.
This has been fixed and will be available in 4.13. The issue is that when the playback of the sequence is stopped, it returns the playback position to the start of the sequence and that caused all the events from the last playback position to the start of the sequence to be fired. Internally, we tracked this as bug UE-31494 and the changelist number that fixes this bug is 3019768.
answered Jul 11 '16 at 02:42 AM
Follow this question
Once you sign in you will be able to subscribe for any updates here