We're just launching our new LRS solution and have authored all of our modules in Storyline 2 and published them using the TinCan option.
The format of the courses is video followed by 3 quiz questions.
We're noticing that the Storyline 'buffering' appears after the last quiz question before the next video starts.
I've had our tech guys look at this and they say there's no issue with the LRS and there isn't any pre-loading of the next video happening, but instead the delay appears to be caused by Storyline 2 taking a while to write the TinCan statements before moving on.
Has anyone had a similar experiences or know of any solutions? I'm happy to give someone access to our LRS if they want to see what's happening?
Hi, Andy -- Thanks for reaching out and for indicating what troubleshooting steps you have already attempted. May I ask if you are finding the same behavior when you test your course in the SCORM Cloud? You may also want to take a look at this article for some additional troubleshooting ideas.
Please let us know if issues persist and we'll see what more we can do.
You are welcome to test your course in SCORM Cloud to see if you experience the same behavior. This will help determine if the issue lies within the course or your LMS.
If it's something you would like us to take a look at, please feel free to share your .story file with our team here.
2 Replies
Hi, Andy -- Thanks for reaching out and for indicating what troubleshooting steps you have already attempted. May I ask if you are finding the same behavior when you test your course in the SCORM Cloud? You may also want to take a look at this article for some additional troubleshooting ideas.
Please let us know if issues persist and we'll see what more we can do.
Hi Andy!
You are welcome to test your course in SCORM Cloud to see if you experience the same behavior. This will help determine if the issue lies within the course or your LMS.
If it's something you would like us to take a look at, please feel free to share your .story file with our team here.
This discussion is closed. You can start a new discussion or contact Articulate Support.