We have a lot of modules that are not loading either when trying to access them directly from StoryLine 3 or when clicking on the actual file which is associated to StoryLine 3.
The error message attached states the file does not exist.
The path looks really long and maybe the issue, also that looks like a network drive and ideally you do not load from a network drive latency issues may prevent the file loading.
Thanks for the advise. It is a network drive and generally works well but now we are working from home there have been issues. I think we need to change our way of working in the future.
A network drive can be in the equation, but we recommend downloading and working on your local drive. This article explains a process that may work for you:
4 Replies
The path looks really long and maybe the issue, also that looks like a network drive and ideally you do not load from a network drive latency issues may prevent the file loading.
Hi Ken,
I agree with Phil and wanted to share a great article that covers both working locally and file naming/paths:
Follow These Tips to Reduce Your Risk of Corrupting or Losing Project Files
Hi both
Thanks for the advise. It is a network drive and generally works well but now we are working from home there have been issues. I think we need to change our way of working in the future.
Thanks again both
Glad that was helpful, Ken.
A network drive can be in the equation, but we recommend downloading and working on your local drive. This article explains a process that may work for you:
Storyline: Recommended Workflow for Collaborative Network Environments