SCORM Output with encoding errors

Jun 12, 2017

Jessica Koehler
By Jessica Koehler

Hi,
I'm using Storyline 360 and create SCORM output (HTML5 with flash fallback). The SCORM package is used in the LMS OpenOLAT.
Until today I changed the layout-settings in OpenOLAT to UFT-8 and everything worked fine. Today I uploaded another SCORM module and the layout-settings didn't have any effect at all. The whole text wasn't readable (see attached screenshot).
I called our LMS admin-team. The admin uses a Linux system and there the encoding error doesn't appear with Firefox 53.0.3 -- same with MacOS and Chrome. Windows has this error on Firefox 53.0.3 and Opera 45.0. (didn't check more Browsers). If I upload the data not as a SCORM file but as HTML output it also works fine. So there seems to be an error within the SCORM Module. Could that be possible? Has anybody had this error and knows a solution?

Thank you for your help!

Jessica

3 Replies
Ashley Terwilliger-Pollard
almost 7 years ago06/13/17 at 2:53 pm (UTC)

Hi Jessica,

Are you on the latest update of Articulate 360? 

To check, launch the Articulate 360 desktop app on your computer and look for the Update button for Storyline 360. Details here.

If you are on the latest update, have you also looked at testing this in another LMS environment? I would give it a try in SCORM Cloud, a free standard for testing. This article has directions on troubleshooting there.

Also, Opera isn't one of the supported browsers but Firefox is for Windows and Mac. You can see the list of system and viewing requirements here. 

This discussion is closed. You can start a new discussion or contact Articulate Support.