Forum Discussion
Erratic behavior after our network drive moved
Hello,
I need an advice from someone who knows more about how Storyline works, than I do. :)
First of all: I've already read, it's a bad idea to work on a storyline file on a network drive, but I didn't read that in time and in our organization that's how we usually work.
It worked pretty well for quite a long time and we only noticed some objects moving a tiny little bit once in a while, but nothing that really concerned us.
Well, a few weeks ago our servers moved and since then we only can add audiofiles from the local hard drive and no longer from the network drive, objects moved a lot while opening the file on the server and we noticed several other kinds of "erratic behavior", we can't explain.
My question: Is it possible to "repair" the file by only opening it on the local hard drive from now on and making changes there until all observable erratic behavior is gone?
Or is the file "broken" and (new) erratic behavior will occur/persist?
Thanks for your advice!
Elke
2 Replies
Hi Elke!
Happy to help!
As you've shared, working off of a network, or shared drive can introduce latency and cause erratic behavior when authoring in Storyline. However, these issues are not irrevocable, and can be corrected by ensuring all of your files (.story and any media) are stored on your local hard drive. Also, for your reference, this article outlines other common causes of file corruption, as well as ways to avoid it.
If you're still noticing unexpected behavior or slowdowns while authoring on your local hard drive, please connect with our team through a support case. They'd be happy to help troubleshoot with you!
Thank you for your help! I'm glad, there's hope to "repair" all those strange things going on in our file. :)
We won't open a storyline-file off of our server again ;)
