Forum Discussion
Multi-part object triggers broken... randomly?
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.