Storyline 3 not working with new Chrome update

Hello,

Hoping someone can give me some reassurance with this issue I encountered with the new update for Chrome - Version 64.0.3282.140 (Official Build) (64-bit).

Before this update, Chrome was the only browser that displayed my SL file properly. IE and the Launch_Story.app Application (Which runs off IE) both caused glitches in my graphics and the audio never synced up with the animations on the timeline. We decided we would direct all our clients to simply open the story.html files and always open with Chrome.

This has been running smoothly for the past 5 or 6 months. I noticed yesterday however with the new update to Chrome 64.0.3282.140 my course will not open. It just stays on the loading page continuously loading. 

I was 2 days away from publishing and delivering Five 150 MB courses to my clients and now I'm kind of in a pretty bad situation. 

Again, the courses still load and open in IE, they just don't run the way they're supposed to. My project is animation and audio heavy so when the audio doesn't sync properly it's very detrimental to the learner. So this isn't really an option.

See attachment for screen shot of loading screen stuck.

Anybody with any info please help. Thanks,

Dave

36 Replies
OWEN HOLT

I am experiencing the same. From what I understand, this is caused by a change in the security settings with the chrome build. The SL3 courses stall but only when you are looking at the published files "locally" (directly sourced from files on your machine). I have been told (but haven't tested) that if the files are on a server or your lms (no longer local), they should play fine.  
Until then, my SL3 files have been playing great locally on MS EDGE for me to preview.

Articulate is working on a fix and will keep the community updated.

OWEN HOLT

You might look at publishing to Articulate's (unsupported) tempshare for previewing/testing. This will let you validate the local vs published environment and let you see how the courses will play for your client. All content on the tempshare gets deleted after 10 days so it is a great solution for testing courses in situations like this.

Leslie McKerchie

Great news!  We just released Update 3 for Storyline 3. This includes quite a few important fixes and some new features as well. Check out all the details in the release notes here.  

The item you'll be interested in is:

Local playback of published story no longer working in Chrome version 64

Be sure to download and install the latest version of Storyline 3.

Let us know if you have any questions, either here or by reaching out to our Support Engineers directly.

Dennis Wijma

Im working on storyline 2, it seems i also have the local bug. 

wipe, wheel, and the playing of a video isnt working on Chrome. i chekked it with firefox, and firefox only struggles wiht the wipe and wheel, the video does start automaticly here.

Can you ensure me if it is only local?

Yunior Murillo

Hi there, 

Already submitted a case:

Case Number: 01359012 
Reference ID: ref:_00D30Txo._500f31CrQI4:ref 

But hopefully I can get some help here, because I am having an issue that is affecting many of our employees. The problem I am having is that the content cannot play for some users in google chrome. What has me stumped is that it is not all chrome users and not all content. I uploaded and tested a file to scorm cloud and found the same issue. 

What happens is that player opens with a big play button in the center and nothing else happens. Our older files work fine and after reading various threads, multiple exports, and seeing inconsistent results with other computers. Two other options that I think may be causing my issue (since it plays on the same chrome on a different computer) may deal with either, Windows 10 compatibility, or the Articulate Storyline 3 update from March. I did the update and my scorm files seem to cause the problem. While my co-worker did not update his AS3 and his files seem to work. 

I attached a screenshot of what we are seeing. Has anyone else encountered this error?

Leslie McKerchie

Hello Yunior and welcome to E-Learning Heroes :)_

Sorry to hear that you've run into an issue with this, but I appreciate you reaching out to the support team and sharing your case number here as well.

I took a look, and I see that you've run into a bug we've recently discovered related to Chrome Version 66 not allowing the audio to play in the HTML5 output.

I'll add this thread as well as we track user impact and if we have any updates to provide.

Leslie McKerchie

Hey Ziv,

3 in a row! Man. Sorry to hear that you ran into an issue as well.

I see where you reached out to our support team as well, and I've added a note about the bug identified related to Yunior's support case. You should be hearing from someone soon and we will share updates here as well.

Duane Knudsen

Thanks Ashley, I installed the update. I know Chrome is a bit of a moving target as Google will always be tweaking the darn thing. With 3.4 I still get the big play button on the browser screen but at least now when I click it, it actually starts the course (before it wouldn't do anything). So definitely progress.

Alyssa Gomez

Thanks for following up, Duane! That is progress. And the good news is, learners may stop seeing the play button as Chrome's Media Engagement Index (MEI) learns that they allowed audio to play on previous visits to the same site. When that happens, audio will automatically play as it did in earlier versions of Chrome.