Preview Issues (caching?)

Apr 03, 2013

Hi.

I've been having a problem with previewing pages both in the slide and in the previewer. 

In the slide:

I change the position of items on the timeline and preview the page, only to have the preview show the item in its previous timeline location. This happens with any type of item (caption added in Storyline, image added to the page, etc.) but seems particularly prominent with zoom regions. The problem is also inconsistent (happens on one preview, not on the next). It is sometimes cured by the slide being closed and reopened, but this is also not a consistent fix. 

In the previewer:

Previewer at times will show previous versions of the slide or have items again appear where they were previously placed on the timeline. Just now, previewing a slide in the previewer showed me both the previous version of a caption (which had been deleted) and the version that is currently on the page. Menu in particular seems to be holding older information, showing slides available that have been deleted weeks ago). This is also inconsistent.

It seems to be a caching issue with previewers holding onto previous information, but I could not discover how to clear the cache on Storyline.

3 Replies
Christine Hendrickson

Welcome to E-Learning Heroes, Gina!

Storyline doesn't cache content in the way I think you're referring to. It sounds like it may be a rendering issue, or possibly a problem with loading the updated content into the slide or preview. 

First, please try to make sure you're working with local project files.

  • Work on your local drive (your C: drive). Working on a network drive or a USB drive can cause erratic behavior, including file 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.

Additional information regarding "Naming Files, Paths, and Namespaces" in Windows operating systems can be found in the following Microsoft article.

You may also want to make sure your machine is currently running 96 DPI. Storyline doesn't currently support 120 DPI. If your system is set to 120 DPI, you may experience erratic behavior, such as:

*  Elements of the application are misplaced or distorted.

*  Objects are misplaced or distorted when previewed or published.

*  Zoomed images don't work as expected.

*  Font sizes are incorrect after using the translation features.

Here's how you can switch to 96 DPI:

Articulate Storyline DPI support

If the problem continues, can you try creating a new, blank Storyline course and tell me if the same thing happens? If not, it may be an issue with the original file. You may be able to resolve this by importing the original files into a new course.

Importing from Another Storyline Project

Let me know how it goes. Thanks!

Christine

Lauren Parker

Did anyone ever figure out a resolution to this issue? We are having pretty much the same problem on our end. We make changes on a slide, but when we preview and publish the file, the changes are nowhere to be seen. It does feel like Storyline is caching the files somewhere, but I can't find where to delete them. In a previous job, I had more access to Windows files, and it seems to me that I found a bunch of cached project files that I could delete. I can't find them now. This almost feels like a bug issue. At any rate, in order to resolve the issue we've had to go in, delete any changes we made and make the changes again a second time. That works some of the time, but is a major pain. Any solutions anyone can offer would be much appreciated.

Ashley Terwilliger-Pollard

Hi Lauren,

This thread is much older, so I suspect you're likely not using the same version or update as previously mentioned above. We're on Storyline 2 Update 7 (and Storyline 1 Update 10). Do you know which one you're using?  You can check by going to the Help tab and clicking on About Articulate Storyline. 

If you're using Storyline 2, have you also looked at purging the temp files as detailed here. Similarly have you tried to do a "save as" to create a new copy of your project and confirm that you're working on local project files? 

This discussion is closed. You can start a new discussion or contact Articulate Support.