Forum Discussion
Multi-part object triggers broken... randomly?
Hi there,
I recently opened up a few project files that I had started and put down a few weeks ago as I worked on other things. To my dismay, I've found found that each of my multi-part object triggers designed to move various objects around in designated patterns have completely broken within that time. The initial animation will trigger for each individual object when the timeline starts on said object, however, that initial animation seems to never be recognized as complete by the following triggers (despite looking complete). Since each of the following triggers rely on the previous animation completing, nothing happens for the remainder of the triggers.
This has occurred in two separate project files and across many different slides, so it doesn't appear to be project or slide-specific. Does anyone have a clue as to what's going on? Is Storyline always this sensitive/finnicky? It certainly doesn't make me want to continue using it for anything if the things I build are just going to randomly break.
Thanks,
Sean
Hi Sean,
I'm sorry you've hit this snag with broken triggers; I'm happy to help troubleshoot! We can start by checking if you're working on your local drive; working on a network drive can cause erratic behavior. If the problem still happens, try these steps to fix possible installation issues.
We'd be glad to investigate further if the problem persists. You may share your Storyline project here or privately in a support case, where our Support Engineers will work with you one-on-one. We'll delete it when we're done.
Hi Eric,
I realized I had been testing my slides with audio, and thus had been using the timeline to play the slides. Upon doing a preview I found that the triggers worked as expected. Unfortunately, using the preview button to do all of my testing would be incredibly annoying when trying to time out audio with the animations. I was working off of a network file (as is quite typical these days, if your org has made cloud-based storage available...), however saving it to a local file didn't change the behavior.
Is there anything I can do to resolve the timeline issue?
On a side note, what's Articulate's issue with network/cloud-based storage? Services like OneDrive and Google Drive have been used by businesses for a long, long time at this point, so to not have full support for such important functionality seems very odd to me. Most orgs with this available won't have backup software running for individual laptops/workstations, so it seems unintuitive to recommend that your customers store their Storyline files on a local drive, thereby making those files more susceptible to loss.
Thanks.
Hello Sean,
Thanks for letting us know that moving the file to a local directory didn't address the behavior. We'll need to take a look at your project file 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 so we can take a closer look at your triggers? We'll delete it when we're done testing!
As for your follow up inquiry, we recommend that users work locally when making changes to their project file because the introduction of network latency has been known to cause issues with file saving / file integrity. When working locally, the application directly accesses the project file on the hard drive reducing the risk of causing any issues with the file.
