I am currently working with motion paths in Storyline 360 on a drag&drop quiz and I am experiencing some weird behavior:
Once I have a motion path added to an object on a layer, the motion path can not be adressed with a trigger (even after saving the file first). It just doesn't show up in the list of available motion paths on the specific layer. This happens quite often and forces me to delete the motion path I already set up and define a new one. Sometimes the new one is listed, sometimes not.
This is pretty time consuming and I am still hoping that I have simply overseen some configuration.
This is very unusual indeed. I tried to replicate the behavior on my end but I didn't have any issues with assigning triggers to existing motion paths.
As a troubleshooting step, please try doing a repair of your Storyline 360 installation to see if this helps. If the issue persists, would you be willing to share a copy of your project file here or in private by opening a support case so we can check for anything unusual that may be causing the behavior? We'll delete it when we're done testing!
We couldn't replicate this behavior on our end so we'll need to take a look at your project file in order to get a better understanding of what's happening. Would you be willing to share a copy of your project file here or in private by opening a support case for testing? We'll share feedback with you as soon as we're done troubleshooting.
Sorry for not getting back to you - I was on holidays. I installed the storyline update yesterday, maybe that will fix the bug. I will try it out and get back to you.
5 Replies
Hello Luka,
Sorry to hear that you ran into this behavior.
This is very unusual indeed. I tried to replicate the behavior on my end but I didn't have any issues with assigning triggers to existing motion paths.
As a troubleshooting step, please try doing a repair of your Storyline 360 installation to see if this helps. If the issue persists, would you be willing to share a copy of your project file here or in private by opening a support case so we can check for anything unusual that may be causing the behavior? We'll delete it when we're done testing!
I was looking for a solution to this issue myself. Did you ever hear anything about how to fix it?
Hi Shannon,
Happy to help!
We couldn't replicate this behavior on our end so we'll need to take a look at your project file in order to get a better understanding of what's happening. Would you be willing to share a copy of your project file here or in private by opening a support case for testing? We'll share feedback with you as soon as we're done troubleshooting.
Oh thank you! I ended up deleting and starting over, so I guess I can send it if it happens again. Thank you anyway.
Hello
Sorry for not getting back to you - I was on holidays. I installed the storyline update yesterday, maybe that will fix the bug. I will try it out and get back to you.