Forum Discussion
LMS Playability Issue
Hello,
I am hoping someone can help me with a playability message when uploading a Storyline SCORM to our LMS (Blackboard Ultra). A few of our SCORMs, zipped .story files, are giving the message: “Some issues were found with this course which may affect playability”. Some of the modules that did have this message were remedy by coping the film into a new project or uploading from a different browser. However, I have 7 modules that still have that message. I have tried all the ways I can think of to remedy these modules. My LMS teams said it is a Storyline issue and not an LMS (Blackboard) issue. I am not sure where to look in Storyline to remedy this issue. I have checked triggers and links. Nothing seems out of place.
Thank you.
My reaction is that there is no problem, just a bug in Blackboard that falsely reports issues.
Speaking as someone who used to get paid to write error messages, the one reported to you is a failure. Error messages should describe the issue in a way that helps you fix or avoid the problem. That one could just as effectively say, "Error."
12 Replies
I can't imagine why duplicating the project and then uploading the duplicate would avoid the error. My first thought though is something related to the SCORM, such as the project being exported in SCORM 2004 when your current implementation of Blackboard only accepts SCORM 1.2 for example, or publishing to the Web format (which can still be zipped) instead of to SCORM.
I'm of the mind Carl is, though: if it's playable and reports completion appropriately, maybe it's just a benign gremlin?
The duplication worked for 3 other SCORM files. It had the message, duplicated to new project, SCORMed, uploaded into Blackboard, and no playability message. I exported the SCORM in all the versions in Storyline and still had the message in these files. These files played fine when testing in learner preview and reported completion as it should. It must be a benign gremlin😑. Thank you for your response.
Can I ask what you mean when you say you "SCORMed" the files after duplicating them?
When we publish content from Storyline for the LMS, Storyline includes some extra files necessary for the published web content to talk to the LMS, such as an imsmanifest.xml file.
Some designers and developers do create those SCORM files by hand or even use preformatted templates, but if we're publishing from Storyline we rarely need to "SCORM" anything. Me personally, I publish, tell Storyline to ZIP the folder, and then I upload the zipped folder to Workday's LMS. No editing or altering of files needed.
If you're doing something extra to the published output on top of what Storyline is adding, that may be a source of (or solution for) the hiccup.
Are there actually any playability problems, or just this vague message from Blackboard?
Tested in Blackboard and there was no issue. The SCORM behaved as expected.
