We’ve encountered a weird bug with sequencer when we package our project where it will use completely wrong values for some of its tracks. The sequence in question has been modified a few times since we created it and it looks like when we package some of the tracks are using values that they were previously set too instead of the current ones. I looked inside the sequence and there aren’t any additional keys or anything of the sort and even inspected the sequence through Visual Studio, didn’t find any extra tracks that shouldn’t be there.
Unfortunately I can’t figure out a way to repro this but I am attaching a stripped down version of my project with just the maps and sequence that is causing the problem. [Sample project][1]. If you open and PIE that project it should look like
which is what we expect it to look like. If you package and run it instead it looks like
which we recognize as the camera angle that sequence used to use.
We’re baffled by how this is happening and haven’t been able to find a workaround that works consistently. This occurs even if I delete my Intermediate/Saved folders or even from a completely fresh checkout. Duplicating the sequence causes the same issue but creating a completely new sequence and copying the values over doesn’t.
I’m not sure about this but it might be related to the bug I posted yesterday about [events getting called multiple times][4]. However, the workaround for that (Deactivate/Reactivate the tracks) doesn’t consistently work for this issue (it worked once, but I reverted the file to make sure I could replicate it and stopped working).