Storyline player painfully slow to open

Is it just me being impatient, or has anyone else noticed that the Storyline player takes a loooong time to open now - to the point where I really dread having to go in there and make changes as it impacts pretty severely on the times it takes to develop a course.

Also, if I want to apply a different player, when I click on "Current Player" I invariably get an error message saying something went wrong. Then when I try to send the error report, I get this screen...

 

25 Replies
Alyssa Gomez

Oh no, Dianne! So sorry for that sluggish behavior. 

First, let's be sure you on the latest update of Storyline 360. To check, click the Help tab, then click About Storyline. You should see 3.17.16168.0 in the bottom-right corner. 

Let me know if you're already on the latest update, and we'll keep digging!

Leslie McKerchie

Oh no, sorry to hear that this is impacting so many of you.

I have not noticed this behavior personally but based on the response here, I'm going to report this so that we can keep an eye out and track user impact.

If anyone has a specific file that they can easily recreate this issue with or even a screen recording of your experience, that would be helpful.

Dianne Hope
Dianne Hope

Is it just me being impatient, or has anyone else noticed that the Storyline player takes a loooong time to open now - to the point where I really dread having to go in there and make changes as it impacts pretty severely on the times it takes to develop a course.

Also, if I want to apply a different player, when I click on "Current Player" I invariably get an error message saying something went wrong. Then when I try to send the error report, I get this screen...

 

I was wondering if there has been any progress on a resolution to this/these issues?

Whilst I can deal (barely) with the slowness of the player opening, the second issue I raised here is causing me a lot of grief.

I have just returned from 6 weeks away, and have installed the latest version of Storyline, but I'm still having the same problems with applying a different player. This is something I do all the time and this results in the program freezing and I need to end the process through Task Manager - very frustrating!!

I've attached a video I've just recorded of this happening.

Can someone please confirm that this is being investigated with a view to resolution? 

Thank you!

Leslie McKerchie

Hi Dianne,

We are monitoring the report of the player being slow to open, and this conversation is attached so that we can update you when we are able.

Thanks for sharing the video demonstrating what you are experiencing once the player is open and trying to select a different one. 

Curious if the issue happens in any course you are working on or just this particular one? Can you tie the error to a specific player perhaps?

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 conduct a repair of your software.

Katie (Gokhshteyn) Riggio

Thanks for sharing that recording with us, Dianne, and ouch! Really sorry you're experiencing that.

While I don't have any new information to share in regards to the sluggish load yet, you're in the right place and we'll let you know as much as we can, as soon as we can! The red X typically appears when Storyline is low on resources. Closing any other open applications and working on a local hard drive usually help combat those gruesome Xs.

I opened a support case on your behalf, so our Support Engineers can do a deep-dive on your setup for targeted next steps to try. Thanks again for continuing to reach out, and keep your eyes out for an email from support@articulate.com!

Crystal Horn

Hi again, Sara! As we're working on performance improvements, could we get a copy of a file where you're seeing the painfully slow loading of the Player Properties window? If it's happening in all of your files, just one will be fine for us to use for testing. You can share it with me privately by uploading it here. We'll delete it when we're done troubleshooting.