Developer Notes

The restore state button actually doesn't work this way. But to actually determine whether an object should restore or keep, you need to go to each of the sections and change the "When Finished" property. The restore state toggle on the player itself just means whether it should save the existing state for the possibility that any of the sections wants to restore state. There's no global restore state toggle.

Description

Restore State should have an affect on sequencer. The animation snaps back to its starting point even when this option is not set if played in PIE. If you drag in the level sequence in the editor and go to the details panel with it selected, the Restore State can be set here. The same effect is had here as in the level Blueprint.

Steps to Reproduce
  1. Download the attached project
  2. Open the level Untitled
  3. Open the level Blueprint and see Blueprint
  4. Play in the editor and see the object/animation snaps back to its original location
  5. Go into the level Blueprint and check the Restore State box
  6. Compile
  7. Save
  8. Play in editor and see the same results as mentioned before(Object/Animation snaps back to original state)
  9. The Restore State has no bearing on the settings and the animation does not snap back into its original location even if this box is not checked
  10. If the animation from sequencer is played through the sequencer window or by hitting play at the bottom of PIE while sequencer is open instead of PIE the animation never snaps back even if Restore State is enabled

Expected: Animation does not set back to its original state unless the Restore State is set.
Result: The animation never snaps back to its original state even if this setting is checked.

Have Comments or More Details?

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

1
Login to Vote

By Design
ComponentUE - Anim - Sequencer
Affects Versions4.16.34.17.24.19
CreatedOct 3, 2017
ResolvedOct 6, 2017
UpdatedApr 27, 2018
View Jira Issue