That's a great question! Supported SCORM specifications haven't changed from Storyline 2 to Storyline 360, and I haven't heard of one spec being faster than another. There could be a few other factors to consider here:
Is your customer comparing a Storyline 2 course and the same course after it was upgraded to Storyline 360?
Were the same publishing quality settings used on the courses that are being compared?
Are the Storyline 2 courses defaulting to Flash content and the Storyline 360 courses defaulting to HTML5 content?
Have you tried comparing the load time in SCORM Cloud with the load time in your LMS?
If you feel a course is loading abnormally slow, we'd definitely want to take a look at that. You can share your file with us here, and our Support Engineers are available 24/7 to assist!
Thank you for the relevant factors. I have asked the customer to take a look and return to me with their comments. But I will test in ScormCloud to see if I can find any issues there.
The vendor did publish with the option of having html5 first, flash second (fall-back). They republished it with flash first and html5 second, and the testing so far indicates that might have solved the issue. My guess is that html5 might be a bit slower in loading than the flash edition is. Using flash does not matter since all the end users have the flash player plugin anyway.
So thank you so much for the list of factors that helped me guide the customer (and the vendor) to try another publish setting.
5 Replies
Hi Niels!
That's a great question! Supported SCORM specifications haven't changed from Storyline 2 to Storyline 360, and I haven't heard of one spec being faster than another. There could be a few other factors to consider here:
If you feel a course is loading abnormally slow, we'd definitely want to take a look at that. You can share your file with us here, and our Support Engineers are available 24/7 to assist!
Hi Alyssa,
Thank you for the relevant factors. I have asked the customer to take a look and return to me with their comments. But I will test in ScormCloud to see if I can find any issues there.
Sounds good, Niels. Let me know if you have any other questions!
Hi Alyssa,
The vendor did publish with the option of having html5 first, flash second (fall-back). They republished it with flash first and html5 second, and the testing so far indicates that might have solved the issue. My guess is that html5 might be a bit slower in loading than the flash edition is. Using flash does not matter since all the end users have the flash player plugin anyway.
So thank you so much for the list of factors that helped me guide the customer (and the vendor) to try another publish setting.
You're welcome, Niels. Glad you were able to sort it out. :)
This discussion is closed. You can start a new discussion or contact Articulate Support.