I have just recorded my screen from inside a storyline module (>Input>Record Screen>Record Your Screen) and when I try to preview scene to tidy it up I continue to get error messages every time (see attached). If I preview the whole project then I can go through it but previewing the scene on its own is impossible.
I'm really sorry about the trouble you're encountering and I'd like to first confirm that you're working on local project files as described here. Next can you try importing this project into a new file and see how it behaves? Lastly if the behavior persists and you're seeing it in more than one file, I'd look at going through the repair.
Thank you for getting back so promptly. I am using my local drive. I imported that particular scene into a new project and it worked just fine. So now I've imported the whole project across into the new project and it appears to work great. Thank you.
Do you have any ideas how I might avoid this happening again? Is it something that happens frequently?
Thanks for the update and I'm happy to hear it's all back to normal. File corruption is unpredictable, and there's no straightforward way to determine what causes it. Common causes are environmental (disk errors, power outages, improper shutdowns), viruses, failed Windows updates, and even file size (i.e., very large files have a higher risk of corrupting).
Consider these preventative measures to protect your project files:
1) Save and publish projects on your local hard drive. Working on a network drive or external USB drive can cause erratic behavior.
2) Save incrementally. If your app has an AutoRecovery feature, take advantage of it. If not, save a new version of your project every hour or so with a new file name each time. If a file becomes corrupt, you'll still have a working version available.
3) Install Dropbox. Snapshots of changes in your local Dropbox folder are kept for 30 days. If a file is damaged or deleted, you can restore a previous snapshot: https://www.dropbox.com/help/11/en.
4) Don't leave the app open and unattended for long periods of time. Some users have reported file corruption after leaving their apps open overnight. It's possible that a malware scan or disk backup could run because the machine is idle, making your app vulnerable to crashing.
3 Replies
Hi Gary,
I'm really sorry about the trouble you're encountering and I'd like to first confirm that you're working on local project files as described here. Next can you try importing this project into a new file and see how it behaves? Lastly if the behavior persists and you're seeing it in more than one file, I'd look at going through the repair.
Hi Ashley
Thank you for getting back so promptly. I am using my local drive. I imported that particular scene into a new project and it worked just fine. So now I've imported the whole project across into the new project and it appears to work great. Thank you.
Do you have any ideas how I might avoid this happening again? Is it something that happens frequently?
Kind regards
Gary
Hi Gary,
Thanks for the update and I'm happy to hear it's all back to normal. File corruption is unpredictable, and there's no straightforward way to determine what causes it. Common causes are environmental (disk errors, power outages, improper shutdowns), viruses, failed Windows updates, and even file size (i.e., very large files have a higher risk of corrupting).
This discussion is closed. You can start a new discussion or contact Articulate Support.