Forum Discussion
Buffering
Experiencing buffering problems with my SL file, occurring intermittently for specific users and locations. I haven't encountered the issue during my testing, but it's the most common complaint. Please help resolve this.
8 Replies
Hi Nikki!
Sorry to hear you've run into this setback!
It would be helpful to know how your learners were accessing the Storyline course when they ran into the buffering issues. Were they viewing the course through a learning management system? If so, testing the project file with SCORM Cloud can help determine if the issue lies with the .story file, or the LMS itself.
Also, if you're comfortable sharing the .story file, we'd be happy to take a closer look and test the behavior on our end. Feel free to attach a copy here in the discussion or privately through a support case.
Looking forward to hearing from you!
Thank you, I have created a support case.
Hi Nikki!
You're welcome! Thanks for following up!
I see that you're working with my colleague Philam, through your support case. We can continue the conversation through your case to keep all information in one spot.
I am experiencing a buffering issue lately that occurs on some slides only when the published course is zipped and loaded into an LMS. When previewing it in SL or using "View Project" before zipping it, there is no issue. This happens regardless of which LMS I test on. The attached video shows what is happening. Only there for a very short time, but long enough that my client is not happy with it, and neither am I. Any word of advice would be greatly appreciated.
When this was an issue for me, I actually ended up deleting the slide that was causing me the issue and remaking it (just the one slide) and then for some magical reason I no longer had that issue... It was like that slide was corrupt?
Thanks for the tip. I tried it, but
it did not work for me; maybe more than one slide needs to be reworked.
This issue was identified in the last 5 courses I developed, as they were undergoing review and validation. So seems to be after a recent update. Since the issue only shows when you publish to an LMS or SCORM Cloud, I didn't see it while previewing the course after publication, but before zipping it.
A workaround that masks the issue, but does not fix it, is to add the following code to the bottom of the "output.min.css" file:
This has to be insert everytime the course is published. Big pain, so hopefully Articulate will find a solution that does not require its users to be experts in writing code.
Hi BarryHollembeak,
Thanks for outlining what you’re seeing and for the testing you’ve already done. I can see how concerning this would be, especially since you’ve reproduced it across multiple LMS platforms, confirmed it doesn’t happen in Preview, and even identified a CSS workaround. That’s a thorough set of troubleshooting steps, and it really helps narrow things down.
Since the behavior appears in LMS and SCORM Cloud but not in Preview or View Project, that suggests it’s related to the published output rather than your LMS specifically. The fact that it’s occurring across several recent courses also makes your observation about a possible recent update especially relevant.
I do want to mention that editing files like output.min.css in the published output isn’t supported and, as you’ve seen, those changes will be overwritten each time you republish. It’s helpful for isolating what might be happening, but it’s definitely not something we’d expect you to maintain as part of your workflow.
Given everything you’ve described, the best next step would be to open a support case and share one of the affected Storyline files. Our team can test it in the current build, examine the impacted slides, and determine whether this is project-specific or something more systemic. Including your short screen recording would also be very helpful.
We’ll be glad to dig into this with you and work toward a proper fix rather than a recurring workaround.
