Storyline 360 Running Very Slowly

Hey Alexander,

Sorry this is slowing you down! Let's see if we can get you back up and running again. Is it possible that you’re working from somewhere other than your local C: drive?  Working from a network drive or a USB drive can cause a few different problems, and you can read more about that here.

If you're already working locally and things are still running slow, try these steps to fix erratic behavior in Storyline 360. And if that doesn't do the trick, reach our to our Support Engineers here, and they'll work with you one on one to troubleshoot further. They're available 24/7 to assist!

Hello,

I am facing the same issue on one slide of my project.

In order to solve the problem I isolated all elements of the slide to see what is causing these lags. First I thought the problem may be caused by shrinked images but there was no effect in deleting them. 

Surprisingly all delay disappeared when I deleted one of the two Textboxes on the basic slide.

However, it is not possible to insert any new text in the other textbox nor in a new one without having heavy lags again.

When copied into a new project everything is running fine. 

Any idea or advice on this issue? 

Many thanks

 P.S. For the moment i will just add the text when everything else is ready but I am still interested to come to know why this is happening.

Hi Thomas,

It's hard to say without seeing the file, but it could be an element of corruption within the file or textbox itself? Have you looked at the best practices here to prevent file corruption?  I'd also want to suggest in the future, you import the slides in as shown here vs. copying/pasting them into a new file. 

Storyline is very very slow. Yes the file is on my local. What is the resolution. Please advise.

Hi Doyal,

I'm happy to help! Can you tell me more about what's going on?

• What version of Storyline are you using?
• Is Storyline slow when you open one file in particular, or is it slow in all files?
• If it's just one file, does that file contain large image files or audio/video files?

large image files

Hi Jen,

Sounds like you believe large image files are the culprit of some slower behavior that you are experiencing?

Curious if the issue happens in any course you are working on or just this particular one?

If you cannot re-create the issue in a new course, I would advise to import the file into a new one and proceed.

If it's happening in any/all files, you should certainly conduct a repair of your software.

We are tracking some specific examples for replication, so you are certainly welcome to share your .story file with our support team here and we'll be sure to take a look.

I'm right there with everyone else complaining about Articulate performance. It doesn't matter which .story file I'm working on; the application is absurdly slow (about 1-3 second delay between clicking something and any response). 

Most irritiating is the fact that the PC I'm working from is basically a tiny god. i7-7700K, 32GB memory, NVMe M2 SSD, GeForce 970. You have to try to make things run slow on this machine, but Storyline manages!

I'm looking forward to an update.

I'd like to add my feedback too. I've noticed when there are many elements on a slide (any project, really) correctly selecting an item gets some 200ms delay. when clicking outside and dragging to select multiple items often the program seems to instead select just one item and drag it where the mouse selection ends. This happens when performing the selection action fast (like I usually do when I work on most other programs)
I think this is due to this "200ms delay".
If then you're working on a slide layer it can get even harder to select and move objects.

Hi Matthew and Walter,

I'm really sorry to hear you're having such trouble with Storyline, and I can see how frustrating that would be. As Leslie mentioned, there are a few troubleshooting steps we'd want to have you go through first, and if you're still seeing this slowness our Support Team is working one on one with folks to dig deeper into what's causing the slowdown. 

It's really helpful if you're able to share that level of detail with us, as we're actively working on some performance improvements and testing it against real courses is the best way to verify our fixes.