Description

An Actor with Run Construction Script in Sequencer set to true doesn't render out correctly with Movie Scene Capture or Move Render Queue. While previewing the Sequencer the actor moves as expected. The tool tip for Run Construction Script suggests it'll be reran, but doesn't elaborate when or how. That combined with the preview behaving 1 way and the rendering behaving another is confusing.

Steps to Reproduce
  1. Create a blank project with Preview 2
  2. Create a Blueprint Actor named 'BP_Offset'
  3. Add a Cube component to BP_Offset
  4. In the Construction Script Ctrl+Drag in a reference to the Cube
  5. From the Reference create a 'Set Relative Location' node then connect it to the 'Construction Script' node
  6. Right click and split the 'New Location' pin
  7. Right click and promote the X value to a variable named 'OffsetX'
  8. Enable Instance Editable, Expose on Spawn, and Expose to Cinematics for 'OffsetX'
  9. In the Class Settings for BP_Offset enable Run Construction Script in Sequencer
  10. Compile, Save, and close the Blueprint
  11. Drop BP_Offset into the world
  12. Create and Open a Level Sequencer
  13. Add a Track for the BP_Offset actor from the scene
  14. Add an OffsetX track to the BP_Offset
  15. For OffsetX key a Value of '0' then scrub forward some and Key a Value of '200'
  16. Select the Create New Camera button and position it to look at BP_Offset
  17. Render a Movie by selecting the Clapper icon and then Capture Movie

Expected Results:
The Cube moves from 0 to 200 on the X axis as it does when previewing the sequencer.

Actual Results:
The Cube remains at whatever value is assigned to OffsetX in the sequence when the movie is render. For example if you scrub halfway between Key 1 and Key 2 then the cube will offset by 100 and not move.

Have Comments or More Details?

There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-147746 in the post.

19
Login to Vote

Won't Do
ComponentUE - Anim - Sequencer
Affects Versions5.0
CreatedMar 31, 2022
ResolvedApr 6, 2022
UpdatedApr 6, 2022
View Jira Issue