Forum Discussion

marcello_'s avatar
marcello_
Community Member
4 days ago

Issue with Add motion path and move trigger

Hello everyone.
I have an issue with Add motion path.
In a slide some objects move along a motion path when other objects appear. 
The trigger used is "when object1 enters the slide move object1 along Line Motion Path 1"
But if I use the progress bar to return to a point on the slide, the moved object does not return to the original positions it had at that point in the timeline.
And this happens both in the preview and in the published scorm.
How can I fix this?
Thanks for any help.

storyline 360
  • Nedim's avatar
    Nedim
    Community Member
    3 hours ago

    The issue here is when the motion path is triggered based on the object visibility on the slide. If an object enters the slide at a specific point in time and triggers an action upon entry, scrubbing the timeline back to that point won’t re-trigger the action. This is because the object has already entered the slide once, and its entry action won’t fire again unless the timeline is fully reset.

    However, if an action is set to trigger when the object leaves the slide, it will trigger every time the object exits, regardless of scrubbing, because the exit action is tied to the object leaving the visible area.

    To fix this, instead of triggering actions based on an object's visibility on the slide, set your triggers to activate based on the timeline’s progress or at specific moments when the timeline reaches a certain time. For more precise animation synchronization, you can also use cue points as markers on the timeline. This way, your actions will consistently align with the timeline rather than relying on object visibility states.

  • StevenBenassi's avatar
    StevenBenassi
    Staff
    24 hours ago

    Hi Marcello!

    Sorry to hear you've run into trouble with Motion Paths in Storyline!

    I recreated your design in a sample file and noticed similar behavior when dragging the seek-bar backward. Before we confirm this behavior is related to a bug, it would be helpful to see a copy of the .story file you've been working with. Do you mind sharing that here in the discussion or privately through a support case?

    We'll delete it from our system as soon as troubleshooting is complete!

Related Content