Poor performance / Publishing for CD

Feb 01, 2019

I am having some performance issues when publishing Storyline 360 projects using the CD option (executable). 

Launching the course via "Launch_Story.exe" results in very poor performance. For example, slide transitions take well over 10 seconds to complete. Animations are extremely slow and choppy. This issue is not present using Preview, or if I launch story.html or story_html5.html in a browser window from the same export folder. 

Publishing using the CD option is still very critical for us. 

The issue is not present in projects published in CD format using Storyline 2.

Storyline (Storyline 360) v.3.23.17480.0

8 Replies
Alyssa Gomez

Hey Tom,

We'd love to take a closer look at the trouble you're seeing. But first, let's get you on the latest update of Storyline 360, which is Update 24. Here's how you can install the latest update.

If you're still seeing sluggish behavior after updating, we can take a look at your project file to investigate what's happening. We'll delete it when we're done troubleshooting.

If that works for you, you can upload your file privately to our support team here. We'll give it a test and let you know what we find!  

Leslie McKerchie

Hi James,

I do not see a similar issue reported for Storyline 3, so I have no update.

Are you seeing an issue across projects when using Storyline 3 or just a particular one?

With your permission, I'd like you to share your project file with our support engineers to investigate what's happening. You can share it privately by uploading it here. It will be deleted when troubleshooting is complete.

Ren Gomez

Hi Tom,

We're still monitoring the impact of this bug, so I appreciate you letting us know that it's affecting your projects. Here's an inside look at how we tackle bugs when they're reported. 

I'm really sorry that I can't say when this issue will be fixed, but you're in the right place to stay updated on this bug's progress.

Jose Tansengco

Hi Michael, 

It looks like what you're experiencing is different than the issue described in this thread. Would you be willing to share a copy of your published output and project file here or in private by opening a support case so we can take a look at what's happening? We'll delete it as soon as we're done troubleshooting.