Then I repeated the process, but this time created zipped versions from within Storyline, In Storyline I exported 3 different versions of the Storyline project as normal exports (unzipped):Ģ. However, in both cases, whether as the web object or the HTML5 Animation, the emulator failed to display within the training package. Quite why one displays within Moodle and the other in a pop-out window from Moodle, I am unsure.again perhaps you may have some experience on this? The result was that I could run the training packages within Moodle, and the separate zipped emulator package, the training package being embedded into the Moodle interface and the emulator running in a pop-out browser window. I then exported (a) both the training package test and the emulator test out as zipped SCORM packages and (b) the second version of the project with the zipped HTML5 Animation and uploaded the packages to the Moodle Server. Here I tried both having the emulator embedded as a "web-object" (story.html file for the emulator) and secondly, as an embedded zipped "HTML5 Animation". I created two HTML5 projects as a test, the first containing a couple of pages from the main training package and a second containing a single interactive emulator. The issue comes when I create the SCORM packages and upload to a Moodle server.
#Moodle scorm package manual upload Pc#
As a stand-alone package, running directly of the PC all works as expected.so far, so good. The emulator is currently embedded as a web object and works fine inside the main training package which was also exported out as an HTML5 package. I have built and tested the interactive emulator which is built in and exported out as an HTML5 package. Converting Flash directly wasn't an option, it just didn't work.
#Moodle scorm package manual upload manual#
I have started undertaking this considerable task using Captivate 2019 for the main training package and (sorry) Articulate Storyline 3 for the multiple emulations, as this proved the easiest way I could find to obtain the interactions I required without having to digest a manual on JavaScript. With the demise of Flash, I have been tasked with changing all the Flash emulations to HTML5 and undertaking a complete revamp of the project. The emulations were originally built in Flash and the original project was built in Captivate 7. This project is a training package containing multiple user interactive emulations.
![moodle scorm package manual upload moodle scorm package manual upload](https://static.packt-cdn.com/products/9781849514828/graphics/4828_10_12.jpg)
A little history may help in clarification. I too have a Captivate project that has multiple interactive emulators embedded in it but am having issues getting everything working in a Moodle environment. I came across this post as I was researching a solution to a problem I have which sounds very similar to the original posting and wondered if you could assist with any suggestions to a solution.