Sluggish/slow performance of Storyline (lags and freezes)

Hi there,

first of all, I would like to clarify that I have read the two existing discussions regarding the sluggish nature of the Storyline, but I have not been able to find a solution for myself.

To make things simpler:

- Storyline has been since I have installed it working with cca 3 second lags (between click and response)

- Even though I am working on quite demanding projects (many images, even on single slide + whole lot of        variables), these images are never big. In fact, almost all of them are under 100 KB and most of them even under  50 KB / the overall size of my project is +- 12 MB

- In the last few days (after a brief pause), one part of my newest project appears to have evolved from 3 sec lags to 15 second freeze (i.e. I click on an object and it takes 15 seconds for it to become active; during this time, the cursor is movable but nothing can be clicked) - other parts of the project may have similar issues but I am not sure as when I have checked it now, it did not appear so

However, the overall performance of Storyline got worse.

My Laptop specs:

Windows 7 Ultimate SP1 x64

4GB RAM

Intel i3-2330M (2.2GHz)

ATI Radeon 6490M 1GB GDDR5 (renamed to 74xx) - but I noticed that whether I use this, or built-in graphic card, the Storyline does not have improved/deteriorated performance

I would really appreciate it if someone could give me a hand with this one.

Unfortunately, I am not able to provide you with a sample of my projects.

If nothing works, I will try to re-install my Windows, in a hope it will somehow solve the problem.

Thank you

Regards,

Michal Stevove

42 Replies
Michal stevove

So I have tried:

/ importing it into a new project

/ working on the scene in a completely isolated articulate project (where only that single scene, composed of single slide is)

/ reinstalling the storyline (according to troubleshooting, with the usage of slCleanup)

however, to no avail.Do anyone have any other suggestions or I just should try to reinstall Windows?

Leslie McKerchie

Greg! Sorry to hear that you are having difficulty as well. I tried to check for a support case with Michal to see if I could offer you some additional insight other than what is already here, but I cannot locate a case. If you would like to reach out to our support team for assistance, you may do so here.

Kevin Hart

Michal, I can completely sympathize.  I have nearly the exact same issue.  And I've tried every solution you've tried to no avail. 

My issue has not gotten nearly as bad as yours.  But I've lost hours and hours of work waiting on the program to be responsive. 

The thing that kind of irks me is that most of these big issues are redirected to the support team by moderators and staff.   And  that's usually where the threads about problems end.  We in the forums never actually get to hear if the issue was solved or not by the support team and if it was solved, how it was solved.  And if it couldn't be solved, what they think the underlying issue is so that maybe the more technically apt among us could try their hand at solving the issue.

Leslie McKerchie

Hi Kevin! That's not where we want the conversation to end. We try to update the threads when resolution is reached if it is a solution that may help the community. I will admit, sometimes we miss that follow up as we are going through hundreds of threads a day, but all it takes is a community member like you to pop back in a thread that you come across and ask if there was a resolution. I'm always happy to check back in on cases, etc to see if there is a solution that may benefit the thread at that point.

As an example, there is nothing that I can provide as an update in this thread as none of the users have submitted a support case.

Hi Todd and welcome to E-Learning Heroes! Thanks for popping in to offer your solution

Ashley Terwilliger

Hi James,

I see the case you submitted, and that John replied with the following troubleshooting steps:

I understand that you are seeing a delay when working with images in your file. I did not experience the issue when I tried to move your images around. I would suggest the following to better troubleshoot the issue: 

1) Work on a 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.

2) Check the Windows DPI setting. 

Storyline will function as expected when Windows is set to 96 DPI (dots per inch).   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.

3) Re-install Articulate Storyline. 

Please follow the troubleshooting steps in this article to fix unexpected or erratic behavior in Articulate Storyline.

Ashley Terwilliger

Hi Melanie,

The majority of this thread deals with issue when creating the course, not running the published version of the course. Have you looked into what browsers, flash versions you're users are accessing the course through? Could there be an overall bandwidth issue associated with the site/LMS that is hosting your content or if all the users are in one location an overall limit or issue with internet speed? You'll want to make sure they're accessing the course using one of the supported browsers here.

M. W.
Ashley Terwilliger

Hi James,

I see the case you submitted, and that John replied with the following troubleshooting steps:

I understand that you are seeing a delay when working with images in your file. I did not experience the issue when I tried to move your images around. I would suggest the following to better troubleshoot the issue: 

1) Work on a 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.

2) Check the Windows DPI setting. 

Storyline will function as expected when Windows is set to 96 DPI (dots per inch).   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.

3) Re-install Articulate Storyline. 

Please follow the troubleshooting steps in this article to fix unexpected or erratic behavior in Articulate Storyline.

 

For anyone looking for the article to adjust your DPI, I think the new link is: http://www.articulate.com/support/storyline/articulate-storyline-dpi-support

Thomas Albright

I am sure that everyone has tried this but since it is not mentioned in this thread... If you are sure there is no file corruption issue, I would advise updating your Graphics Driver.  It has fixed this issue for me. :)  I am running both SL 1 & SL 2 on a Windows 10 PC with Dual AMD HD 7770 in crossfire mode. Updating to the Beta driver 15.4 fixed the lag issue last time. :)

Good Luck

Jason Questor

Like everyone here, this slow response in going to the next slide was driving me crazy. The first course I loaded into Storyline 2 was an existing course created in Storyline 1. Client was very angry with delay caused by the new software. Had to regenerate it in Storyline 1 to keep the client happy. Followed all the threads, talked to everyone, to no avail. THEN THE ANSWER came when I looked at the Timeline for a basic slide. It is set for 5 seconds universally by Storyline 2. It delays Next Slide navigation even when the slide is set to advance manually by the user.  Drag this thing back to 1 second everywhere (there is no universal setting for this) except where you have duration-dependent items like narration or video and VOILA. Quick as a bunny. Don't know about any other hardware or Windows related issues reported here, but this has solved the problem for me (running Windows 7 Professional btw).

Ashley Terwilliger

Hi Jason,

I did also want to check that you weren't using restricted or locked menu navigation in Storyline 2 - if so, that'll also impact your navigation with the next button. It won't allow the user to navigate forward until the timeline has ended if you have used either of those menu navigation methods. 

Tom Murphy

Hi Ashley - I am in same boat as others in this thread and getting no where.

I have done all steps - reduced dpi to 96, reinstalled (twice), etc. and still taking 10-15 lags in getting to different parts of my video (let alone edit or do any changes).  The video is only 3 minutes long!

I am working locally.  The video file is not that big.  In fact, I took some sample videos at lowest video capture size (and  less than 15 seconds long) and STILL experience incredibly slow response trying to edit/work on a video.  I have no other applications open beyond the Storyline file.  The other rub, is that my computer has the same CPU (2.6 gig) and RAM (8 gig) as some of my colleagues and they are not having any issues.

There has to be fix to the very obvious issue others are experiencing.  

Please advise any clear cut resolutions I can try.

Thanks!

Tom

 

Ashley Terwilliger

Hi Tom,

Thanks for reaching out here. I  think we'd want to take a look at your file to see what you're experiencing as this thread spans more than just Storyline 2 and a few different issues - some of which were resolved by the user such as Jason's last post. If you'd like you can attach the .story file here using the "add attachment" button or if you'd prefer to share it privately you can also send along here.