Flash = Fast but HTML5 = Slow?
Jun 09, 2016
I have a complicated Storyline module (complicated to me anyway). One slide has over 500 triggers, and the project has a lot of JavaScript dependencies.
When Flash is turned on everything works as expected. But if I disable Flash and run the HTML5 version, the module crawls, and sometimes halts completely. I've tried publishing this for web and tested on a web server, and for the LMS with testing in Blackboard, and I've also tested it on SCORM Cloud. No matter what I do the HTML5 version has miserable performance.
Anyone have any ideas on how I can troubleshoot this? I'm at a loss.
14 Replies
The HTML5 version is always slower because it refreshes in realtime as there is no preloading, can you post the slide it may be possible to rationalise the number of triggers you have used. realistically improving performance will mean reducing the content on the slide.
Thanks, Phil! Sadly I can't post the slide, and (equally sadly) I can't reduce the number of triggers. Hopefully Articulate will pay more attention to the HTML5 output in the near future, so it can rival the Flash output.
So I have a module that is running terrible slow. it's the first time I've published in all HTML5 mode (my LMS will no longer accept Flash content).
There's only 1 trigger on each slide. It's a practice module and the exercises are being graded as a test. What can I do?
Hi Elizabeth. The HTML5 output doesn't preload exactly the same way as the Flash output. So if your content has videos, those are loading per slide, though they are progressively streaming.
What other elements do you have on your slide? Is it a screen recording that you've inserted in Test mode? I'm happy to test out your .story file if you'd like to share it here, too.
Thank you Crystal.
Attached is the file.
Hi Elizabeth! Thanks for sharing your file. I published it for LMS and uploaded it to SCORM Cloud here. Would you mind testing this link and letting me know if you notice a difference in speed? I'll be standing by!
The responsiveness is amazing! Do you think it's my LMS? What did you do?
Hi Elizabeth,
It could be your LMS, but let's first double check that you and I are using the same version of Storyline. Can you tell me what update you're on? Here's how to check:
Click the Help tab, then click About Storyline. You should see version number in the bottom-right corner. What is the number shown there? Thanks!
sorry to keep you waiting, Alyssa.
Storyline 360 V3.8.13281.0
I think it might be my LMS. We tested it on another LMS and it worked better.
No worries, Elizabeth! It looks like you're on the latest update of Storyline 360. Since the course performed better on SCORM Cloud and in another LMS environment, I would say that the lag is related to your LMS.
Have you had a chance to reach out to your LMS support team? I'm curious, what LMS do you use? Perhaps other folks in the community who use the same one can chime in with their suggestions.
Hi there. I’m also having issues with laggy HTML5 modules that were fine as Flash.
We are using NetDimensions.
Any suggestions?
Thank you!
Hi John!
Sorry to hear that you've run into difficulties. Were you able to test your published output in SCORM Cloud as well? Curious if you were able to replicate.
Is there any news on this subject Leslie?
I have courses made in 360 and when I publish to HTML5 the hospitals working with these modules experience unexeptable pace with the HTML5 output via their virtual machines, while with flash the output pace is just fine. We can not move beyond the virtual machine concept as this is a setting needed for flexible workplace configuration.
Very inconvenient and I was wondering if there are going to be any changes made to the HTML5 SCORM output that will speed things up in the (near) future?
Or any experiences you or the tech dept could share in order to speed it up in the hospital / at the virtual machine side?
Thank you in advance for your reply.
Hi Judith! Happy to work with you on this issue. I have a couple of questions to see if we can figure out what's happening:
Thanks!
This discussion is closed. You can start a new discussion or contact Articulate Support.