Relative Start on Motion Path not so relative after all.

Hey there, Owen! Thanks for also opening a case. 

Gerald recently requested a copy of your file so he can take a closer look. Let me know if you have any trouble sending the file to him!

It took a while, but I sent the files yesterday.  Looking forward to a resolution as my DevLearn presentation is banking on this working in both SL3 AND 360. 😁

Hey Owen!

I checked in on your case, and I see that Gerald is still trying to nail down the cause of the problem. Luckily he found that the issue doesn't happen when you're using the Classic Player. Will that be an option for your presentation?

I tried his link that he sent through email and it looked good.  However, when I:

1. Open the SL3 file in 360 - Change to Classic - and Publish... it still malfunctions. I also
2. Opened a new SL360 file - changed to classic - imported the slides from SL3 file - and published.... same bad result.  How did Gerald get it into sl360 with a classic player and not have it continue with its bad behavior?

https://360.articulate.com/review/content/f334153e-4d79-41c6-a666-c14672a6dd38/review

Hi Owen,

I'll ask Gerald to follow up with you and share some more details on what he setup to have it work! 

Thanks Ashley!

I decided to update recently to take advantage of all the cool new features and in hopes this had been fixed.

It hasn't. 😭

The paths in my complex dial navigation still jump around and run offset to where they should be located.

I hate the thought of rolling back to the last build where it worked which is now over a year old.

Hello Owen!

I've looked at the file in Storyline 360 Update 37 (Build 3.37.21453.0) and Storyline 3 Update 9, and I see exactly what you're noticing! I can see how this is frustrating especially since that course is incredible! Wow! I love the language "Nothing to see here but the sharks!" 😂

Your file is still being investigated by our Engineers so I hope we can have a fix soon for you! I've updated the bug report with your recent comments so we are up to date as well.

Thanks Lauren. I would really love to one day be able to publish a full course based on this concept in 360 AND take advantage of all the cool new 360 features.

I've never heard back on this.... 

Hi Owen, 

I sent a quick message to Gerald letting him know you're following up. I was going to take a look at it myself, but the file links have expired due to our security policy, so we may need to request them again.

...still no word. 

Hi Owen,

I see that this has come up again as you tried to help a customer here (thank you by the way).

I took a look at your support case and the associated bug reported and see that Gerald did reach out to you in June when we chatted above. 

We are able to replicate the issue, but were not able to do so in the Classic Player and had that listed as a workaround. I see that you weren't able to accomplish this solution with your file, so I'm going to share that with Gerald.

I wanted to share some information on how we define bugs and how we tackle them when they occur.

Hi Owen,

I have great news to share! We are no longer seeing this issue in our latest version of Storyline 360 (Build 3.73.29831.0), where a motion path is not working properly in the Modern Player.

To make sure your software is up-to-date, please launch the Articulate 360 desktop app on your computer and select the Update button next to Storyline 360. I've included our step-by-step instructions here!