Motion paths, relative start points

See attached a quick example, hope that helps.

Thank you, Michael, but I am back on an earlier 3.4.x version and am unable to upgrade at this time.  I can't open your file without doing so.  I appreciate the offer.

Try this version (completely based on Michael's version, just built in SL3 instead of SL360 with the modern player).

Thank you Christy (and Michael again for inspiration),

So what I realized is that by creating multiple motion paths for what I'm doing, I end up creating paths that are defined off the slide.  (I hadn't realized that the second motion path still 'starts' from the starting point of the shape.  I was initiating it where I directed it to on path 1.) Of course, it doesn't appear that way to the user.  There must be a bug, because after a preview, I have to switch to another layer then back to even be able to modify a path which is off the slide proper.  Since I'm basically aiming for a target that's not there, I find that I have to modify the endpoint of the second motion path a dozen times to get anywhere near where I want the shape to end up.  Is that just the way it is?  Ideally, I'd like to be able to specify a pixel to end up on, but I'm limited by the crude capability of how Storyline limits my mouse movement.

I'm trying to demonstrate website navigation, and considered recording with Camtasia, but I don't need two tools where I don't know what I'm doing.  The shape starts in the upper right, moves to the lower center, and then back up to the upper right (generally).  That's the motion path that then has to go off the slide.

I am doing what I wanted, but it seems like it should have been easier.

Thanks again to you both!  Judy

It may be easier to help you finetune your motion paths if you could share your .story file (or the one slide) here so that someone can take a look.

Hi Michael, please see attached for what I'm generally trying to accomplish.  Any suggestions appreciated!

Have a look at the attached and see if that's closer to what you are looking for. The 'bounce' between the first and second motion path happened because of the Direction settings (In&Out) and the timing of both.

I like that better, thanks for the help, Michael and Christy!

Hi Michael, wondering if you can help me understand the steps you actually took.  I would like to do the same thing, but each time I click on my motion path and select relative start point, I can't get a second motion path so I can add the trigger to occur from a cue point.

Every time I do it in storyline 360 it just moves my original end point.  Any chance I could bother you for a screencast?  I like this idea.  I have attached my one slide with my two images on your original file.  This slide is going to be a lightbox.  I have done motion paths on and off the screen using layers in other parts of the module and it works great, but this I want to move it on the same lightbox slide and was hoping not to create layers which I see you accomplished.  So the first image I want it to move down and than say after 3 seconds it moves off the slide either right or down not picky right now, and then as it is moving down the next image will move into the spot on the slide if that makes sense.  I put the second image just off the slide so you had it. Much Thanks :)

I have a similar issue that I can't seem to figure out. I am building this "peg" simulation where the user drops a ball that bounces down the pegs and eventually lands in a bin and that is how their knowledge check question is chosen. However, the ball keeps going back to the start of the motion path even though I have selected relative start point, so it never leaves the first row of pegs.

Hi Jennifer! In case you haven't seen it, I wanted to point you to a similar example by Ben McKenna. You can download the file to look at the triggers. Hopefully, that will guide you in the right direction.  

Hi Jennifer,

I think the reason why your ball was returning to the start point was because you were effectively resetting after each drop by hiding and re-showing the layer.

In the attached version of your original file I have taken a different approach:

1.  Everything now happens on the Fall layer, which only shows when the slide timeline starts.
2.  I have deleted the FallNum variable as this is no longer needed.
3.  I have set the random variable and started the first drop when the user clicks the ball:

4.  I have set the next drop to occur when the animation completes for the first drop and this then repeats for each successive drop:

5.  I have made the rectangles smaller at the bottom of the screen so that the ball is seen to drop almost to the bottom of the screen before the user is jumped to the next slide.
6.  More importantly, I have given the rectangles a 100% transparent, white fill. If you simply give them no fill, they are effectively not there and so the intersection with the ball never occurs and your triggers don't activate.

Hope this helps, but if you have any queries about anything I have done, just get back to me here.

Thanks, Ned!