Object on Motion Path Line goes passed the END point.

I'm having trouble identifying a weird behaviour with a motion path that i've created that moves a custom sliding bullet arrow head that i've created for one of my slides. I use triggers to move the custom arrow head from one bullet to the next using cue points while syncing with the narration. The problem is when the arrow head slides from the 2nd bullet text to the 3rd bullet text, it goes past the 3rd bullet even though the motion path ends exactly beside the 3rd bullet text.

Ps. As a quick fix, I managed to tweak the motion line end position pretty much vis a vis 2nd bullet text and I finally got it to stop beside the 3rd bullet text. A little time consuming and not the most productive way especially when you have 150 slides to do like that!!.....anyone else experiencing this?

10 Replies
Christie Pollick

Hi, Yvan -- Thanks so much for your patience, and as you can see here when I published your file for LMS and tested on the SCORM Cloud, I experienced the same behavior you described. As I was not able to determine the root of the issue, I am going to have our Support Engineers weigh in with their input. I'll create a ticket momentarily, and you will be hearing from a member of that team shortly! :)

Christie Pollick

UPDATE for others following along here: Our Engineer, Victor, was able to share...

"We have reviewed your project file and we were able to duplicate your issue. I have submitted your case to our Quality Assurance team for their review. The issue appears to affect Motion Paths with Relative Startpoint enabled. 

I cannot offer a time frame for when or if this issue will be resolved. However, we recommend that you keep you installation of Storyline updated to the latest build for it may contain revisions that may address this issue. I'll keep you posted on any updates on this case." 

Christie Pollick

Hi, Yvan -- Yes, when an issue is sent to support, I always like to follow along with the case so that I am able to share relevant updates here in the forum for others who may have encountered a similar issue, and could benefit from the information or suggestions shared in a case. Thanks, and please let us know if you need anything further! :)

Christie Pollick

Hi, Greg --Thanks for reaching out! I just checked and it appears that the issue is still in with our QA team for investigation. And while I do not have a workaround to offer or a timeframe for if or when this will be addressed, please note that any further updates will be shared here. So, since you replied in this thread and are now subscribed, you will receive notification of additional information be shared here. We appreciate your patience! :)

yvan meloche

Hi Greg. I'm still having the same problem. I don't know if you've tried this but this is what I do and it works well as a temporary fix. Make your end point of your motion path just a few steps before your intended end point position and preview it. Keep tweaking that until you get the result you are looking for. Like i said, its not the most productive way but for now it works. (see my attachment above as an example)