Working from network drives - Storyline 2

I remember years ago that working from a network drive caused problems saving and publishing Articulate files, specifically Studio files.

Is that still an issue with Storyline 2?

It would make my life a lot easier if I could work from network drives. But it would make things significantly worse if there are still glitches and I run into problems.

14 Replies
Leslie McKerchie

Hi Kyle! We still recommend working off of your local drive:

When creating, editing, and publishing Articulate Storyline courses, be sure you're working on your local hard drive (typically your C: drive). Working on a network drive or a USB drive can cause erratic behavior, such as file corruption, an inability to save changes, and loss of resources. See this article for more information.
Peak Bagger

The only issue that we have sometimes and could be related to the usage of a network shared-drive is sometimes when we save a storyline project, it says the file has been change since last save. Since we are a team of 6 developpers, we checked if someone else was working on the same file but it wasn't the case. Now we know that it's a little glitch that causes no arm...

Kyle Perry

I haven't tried working from a network drive since Storyline 1. It seemed to work ok for a while creating courses, until two situations. I published a course to a network drive and got an error. Easily fixed when I happen to try publishing to a local drive, but I didn't realize the problem was working off the network drive. The bigger problem came when I was working on a network drive and the saved file became corrupt and I lost everything.

Now the workflow includes downloading from the network drive and using a versioning system to keep track of the latest file. It's frustrating to have a file on a network drive and a local drive, and not know which one is the latest version. :)

Mike B.

We often work from a network drive out of necessity, and have not yet had any problems related to it. We run over a gigabit network which easy transfers 100MB/s to our storage drive, and most of our project files are under 5MB at this point, so that might be why we don't have any issues.

Yes, trying to manage file versions across local and network drives concerns me too, so I try to avoid that.

Peak Bagger

I guess our lightning fast gigabyte network access gives us a chance to work on it without hassle.

We use a strong versioning policy which causes a lot of "save as" and version incrementation each time we change a file. We never had some corrupted files though...

We had no problem with the publishing neither ! I guess there's a lot of environmental factors implied in theses problems people have.

Peak Bagger

It's kind of more complex than this, but shortly, everyday we work on the same file, we "save as" a new version of the .story file in the morning and a couple of times during the day. This way, if a file gets corrupted, we only lose a couple of hours of work. We created a standard versioning number scheme that every team member use. Something like "myprojectname_v1.01". We always increment the two decimals until we reach the first live release. Then we increment to v2.xx and so on. Some pretty basic versioning good practices I guess... We learned to work this way using the Adobe Creative Suite and having a Premiere file corrupted a couple of year ago...