Best Practices to Avoid Crashes
I've culled and searched for some best practices we can all use to prevent crashes and file losses. We've all been there - well, hopefully you have not! Please feel free to add to the list!
- Don't work on your local drive (your C: drive).Working on a network drive or a USB drive can cause erratic behavior, includingfile corruption, loss of audio, and other unexpected behavior.
- You should also make sure the directory path to your project files and your published output is less than 260 characters(for example C:\Articulate).
- Avoid using special characters, accents or symbols in your file names.
- Save other copies in a different directory. Keep a consistent naming structure e.g. V2.2, 2.3, etc. so you can keep track of which files are new or old.
- Save lots - especially as the file gets big or you do new more complex, resource-heavy uses (e.g. Multi-layer slides, triggers, many images, or known crashes/bugs like using Exam Banks
If it crashes:
- Have you tried importing it into a new Storyline file?
- Are you using the latest version of Storyline ( version 3)? You can double check this by going to the Help tab -> About Articulate Storyline. You'll see the version number just under the Storyline heading.
- Have you conducted a repair of Storyline? The directions on how to do so are here, if the behavior persists after repairing Storyline you may also need to follow these directions to uninstall/reinstall Storyline and the supporting Microsoft software.
- If the issue persists, can you check if you still encounter the issue when working on a new project in Storyline?