Forum Discussion
Triggers Not Functioning Correctly AFTER Publishing to LMS via Scorm file
Hi everyone! I have built a "Mario Brothers" inspired game where Learners will move the main character around (jump, left, right back, etc.) - in Storyline's preview mode, everything is functioning as it should. In our LMS after it is published, when the character "jumps" it will get stuck in the air but in Storyline's preview mode the character comes back down from a jump. Does anyone know what could be causing my "game" to function differently in the published LMS versus Storyline? Thanks in advance!
- LSheffieldCommunity Member
I came here to post a similar issue. The trigger to "mark as complete" at start of slide 2 timeline is not working for some users when I publish to the LMS. But it is working for others. I've tried using different browsers, having them clear the cache, and even switching between SCORM 1.2 and SCORM 2004. Nothing is resolving the issue for those users.
- ClaireB_TAMU15Community Member
Awh man, sorry to hear this! I am going to meet with our eLearning systems team tomorrow - if they give me any recommendations and guidance I will gladly share.
- PhilMayorSuper Hero
Can you share the project? Are you previewing the whole course or just one slide?
I would suspect there is a variable not getting reset, but without seeing the file it is just guessing- ClaireB_TAMU15Community Member
Hi Phil, I am attaching the slide giving me the post-publishing issues, thank you in advance for your guidance and taking a look at this!
- JoeFrancisCommunity Member
I would add, how does it work on Review 360? It's easy to paint an LMS as the scary boogeyman, but really all it's doing is launching courses, tracking courses, and reporting learner progress. If you're trying to retrieve a variable which isn't present, that could cause Storyline to choke. But a crappy network connection could theoretically do that too.
- ClaireB_TAMU15Community Member
Good insight, thank you Joe! I did not even consider the network connection. My two individuals that experienced this "bug" were from satellite locations.