Bug UE-66454 Isnt scheduled to be fixed until 4.22 and this is a big problem!
Bug UE-66454 (link) This bug causes a duplicated sequence to not fire its own events, but, the events from the sequence it was duplicated from. The output shows this error "LogMovieScene: Warning: Failed to trigger the following events because no director instance was available: SequenceEvent_#" Thus rendering the copy useless and its events forever disassociated from its sequence director.
This isn't the worst thing on its own, but, we've had the same problem and warning show even for non copied sequencers as well. All events will randomly lose their sequence director association regardless of if they were copied or not. This can happen hours into working on a sequence as well.
How this relates
This relates to bug UE-66454 as Epic staff have now pointed to this bug as having the same root cause.
One of our team members got this response back from Epic
After doing some digging I was able to find a known issue with the same root cause. I have provided a link to the public tracker. Feel free to use the link provided for future updates.
Why you should care
You can spend, hours, days or weeks putting together a sequence, and have it permanently ruined by this bug. This bug isn't slated to be fixed until the next engine version 4.22. This is simply unacceptable for such a core tool to go this long without being fixed. No one should have to play Russian roulette with time, money, energy, and sanity. Especially not until the next full engine release. A fix for 4.21.1 Hotfix would be understandable, but, 4.22 is not.
Follow this question
Once you sign in you will be able to subscribe for any updates here