sequence onStop does not fire in shipping build

Justin.Dooley · November 8, 2016, 3:28pm

I set up a simple level fly through at the start of a match that fade out at the end. I then bound the on stop event in the level sequence. That plays a “globalFadeIn” sequence and the rest of my initialization such as adding my UMG HUD.

This works fine in editor and it also works fine in stand alone but the packaged project does not fade back in and my hud is not added.

anonymous_user_e729f54e · November 8, 2016, 6:19pm

Hello .,

I have a few questions for you that will help narrow down what issue it is that you are experiencing.

Quick question:

Can you reproduce this issue in a clean project?
If so, could you provide a detailed list of steps to reproduce this issue on our end?
Could you provide screen shots of any blueprints/widgets that may be involved?

Justin.Dooley · November 8, 2016, 6:46pm

Yes I can. I’ll attach it.

Repo Steps:

Create a new Project
Create a level sequence.
Create a fade track and have it fade in, and then fade out.

Create a second sequence and have it fade in.

Have the main sequence autoplay
In the level blueprint assign a onStop to the Main sequence’s sequence player.
Have the onStop event playthe fade in sequence
Package the game.

[Project Files][3]

anonymous_user_e729f54e · November 8, 2016, 7:44pm

After testing the project provided things appear to work the same in the editor as then do in the packaged version of the project. That is to say “NewLevelSequence” plays and then GlobalFade Plays. Could you test the zipped down copy of the project that was provided?

Justin.Dooley · November 8, 2016, 7:57pm

Hey Rudy I’m currently streaming this so if you are online, come say hi on twitch and I can show you. Otherwise I’ll link a video of it happening and my staged build setup after the stream.

Twitch Stream

Justin.Dooley · November 8, 2016, 10:14pm

Please see the attached stream highlight.

anonymous_user_e729f54e · November 9, 2016, 4:29pm

Hello .,

After further testing I was able to reproduce this issue on our end. I have written up a report and I have submitted it to the developers for further consideration. I have also provided a link to the public tracker. Please feel free to use the public tracker for future updates. Thank you for your time and information.

Link: Unreal Engine Issues and Bug Tracker (UE-38416)

Make it a great day

Justin.Dooley · November 14, 2016, 10:31pm

Hi Rudy,

I see that this task has been fixed but it marked for 4.15. Where can I see what the changes are so that I can perform them myself here?

Justin.Dooley · November 15, 2016, 5:27pm

Yea I tried looking at the master build on GitHub and could not find anything with a submit of 3163859 in the repository. Any suggestions?

anonymous_user_e729f54e · November 15, 2016, 7:50pm

I took quick look. It appears that this has been resolved in an internal build. However, it has not been merge with the master branch as of yet.

Justin.Dooley · November 16, 2016, 10:34pm

I don’t know if it’s possible but could you copy paste the fix here for me. I’m on a super tight deadline and we won’t be on 4.15 any time soon.

anonymous_user_e729f54e · November 17, 2016, 5:49pm

Due to terms of service I am limited to how many lines of source code I can post publicly. These posts are visible by those who have not signed the EULA. The source code that is associated with this solution goes over that limit.