I built a tool to use in our cinematics through Blueprints with a bunch of exposed variables.
I made them all Editable and selected Expose to Cinematics.
I can add them as tracked items in Sequencer and when I animate the values I see them changing on the blueprint but no change is taking place in the viewport.
We are using UE4 as a pre-visualization tool so it is extremely important that these sort of tools update while scrubbing in the sequencer timeline.
Is it a bug or am I missing some super simple solution?
We’ve had this asked before, but it doesn’t look like this will actually be implemented. I’m talking with one of our engineers who worked on UE-31193, but he’s in another time zone, so I might not hear back immediately.
Thank you for your reply,
I’ve seen the issue pop up here or there a few times before and I’ve also up-voted UE-31193.
I guess for now the solution would be to push those functions into code on our side like you did with the crane and the rail?
I think the biggest issue that’s confusing a lot of us, is that the functionality appears to be there but is not working as expected.
Not understanding everything that’s going on under the hood makes it appear like it’d be an easy fix for you guys.
Of course I understand it’s not that easy but getting this fixed/implemented would be a huge step for UE4 integration in movie production/previz pipelines.
Well, there were actually some recent developments on UE-31193. It was marked as a duplicate of UE-23853 and I’m checking with the fixer to see if the implementation of UE-23853 will actually make the UE-31193 request work.
The fix for UE-23853 is actually in 4.16 preview, so you can try it out if you’re curious.
That’s great news unfortunately on my end these two issues do not seem to be related. Or maybe they are because I tried my blueprint setup on 4.16 and not only could I not control the blueprint through sequencer but many of the controls stopped working outside of sequencer as well.
I will fiddle with the blueprint, experiment further and report my findings.
I spoke with some of our engineers and re-opened UE-31193 since we have a similar feature in one of our internal projects. It’ll need some cleanup, but we’re going to try to get it into a future release.
Note: UE-31193 is a feature request and we are no longer listing feature requests on the public tracker.
Hi everyone, I don’t know if the issue is still relevant, but here’s a possible solution after you’ve inserted/enabled with the checkbox the variables into the sequencer.
In the class settings panel, each actor has a checkbox labeled “run construction script in sequencer.” I think this is usually turned off by default, so it’s likely the cause of the issue.