Storyline and Studio: How to Enable LMS Debug Mode

Article Last Updated

Need to troubleshoot an issue with a Storyline or Studio course in your LMS? Enable debug mode in your course to see all the communication between your content and the LMS.

SCORM, AICC, and cmi5

  1. Publish your course for LMS distribution, then click Open Folder on the Publish Successful window.
  2. Open the lms folder in your published output.
  3. You'll see either a scormdriver.js file or a Configuration.js file, depending on the authoring app you used and the publishing format you chose. Open the file in a text editor, such as Notepad.
  4. Find this line of text: SHOW_DEBUG_ON_LAUNCH = false;
  5. And change it to: SHOW_DEBUG_ON_LAUNCH = true;
  6. Save and close the file.
  7. Return to the Publish Successful window and click Zip, then upload the zip file to your LMS for testing.
  8. Launch the course from your LMS and reproduce the issue you're troubleshooting. The course will open in one window, and the debug log will open in another.
  9. When you're done testing, copy and paste the text from the debug window into a document for your LMS administrator to investigate.

Tin Can API (xAPI)

Tin Can API debug mode is only supported in Flash-enabled browsers. It won't work with HTML5 output.
  1. Publish your course for LMS distribution, then open the folder that contains your published output.
  2. Open the following *.html file in a text editor, depending on the authoring app you used.
    • Storyline 360: story_flash.html
    • Storyline 3: story_flash.html
    • Storyline 2: story.html
    • Storyline 1: story.html
    • Presenter 360: presentation_flash.html
    • Presenter '13: presentation.html
    • Quizmaker 360: quiz_flash.html
    • Quizmaker '13: quiz.html
    • Engage 360: interaction_flash.html
    • Engage '13: interaction.html
  3. Scroll to the end of the launch file and paste this line of text before the closing </body> tag:
    <script src="debug/tincandebug.js" type="text/javascript"></script>
  4. Save and close the launch file.
  5. Download and extract this zip file on your computer, then copy the debug folder into the root folder of your published course, the same folder that contains the launch file you just edited.
  6. Zip your modified published output, then upload the zip file to your LMS for testing.
  7. Launch the course from your LMS and reproduce the issue you're troubleshooting. The course will open in one window, and the debug log will open in another.
  8. After you've reproduced the issue but before you exit the course, click Export Data on the debug window and save the TinCanDebug.dat file to your computer.
  9. Send the TinCanDebug.dat file to your LMS administrator for investigation. To review the file, launch this web page, click Import Data, and import your TinCanDebug.dat file. (Or, launch the debug.html file from the extracted zip file in step 5 above, then import your TinCanDebug.dat file.)