When published and viewed from a browser (i.e. Firefox), my Captivate demo (incorporated as a Web Object) works fine and loads promptly. Once I have it loaded to our LMS a 20 second plus delay has now been incorporated into my course. How can I remove this unwanted time?
It may be important to note that the original XML & XSD files are deleted and replaced with files that are able to communicate with our LMS system. I referred to this as the Manifest Maker Conversion Process.
Another option would be to use our Tempshare server. Just keep in mind that this server is only available for testing content - it is not officially supported by Articulate and all content will be removed automatically after 10 days.
In addition, you could also use Dropbox. Just remember that you'll need to place your content in the "Public" folder. Also, you'll need to make sure that the folder is enabled. To do so, click on this link.
You're always welcome to try out Articulate Online, as well - it's available for a free 30 day trial.
Over the last few days the problem has persisted. I've also discussed the situation with our LMS admin and, so far, we don't have an answer as to why this is happening. To that end, I've just discovered how to Enable the SL's Debug Mode (see link: http://www.articulate.com/support/storyline/how-to-enable-lms-debug-mode) so we are continuing to research the problem.
However, all is not lost. The problem I described impacted 2 courses with captive demo swf files that was about 4K KB and the other at 6K KB originally. I started to suspect that file size was a problem. Captivate compressions were already in place (Advanced Project Compression & Compress SWF File boxes were checked in one file and Compress Full Motion Recording SWF File was checked for the other). In both courses I eliminated any unused objects from the library and ultimately got one CP Demo down to 2K KB and the other was just above 5K KB.
The course with the 2K KB started loading immediately..... YEAH!
The other course continued to have problems. In order to move past this problem, I split the demo in two (one CP demo had a 4,513 KB swf file size and the other was 1,748 KB swf file). Both demos now open as intended.
The only conclusion I can draw is size matters. We are continuing to diagnose the problem to see what additional answers I find. Will post additional findings.
Thank you very much for that excellent information. I'm happy to hear that you were able to make some progress with this.
I'm still curious to hear whether or not the original (larger) versions worked well outside of the LMS. If not, then it might be something to look into from our side. If so, then hopefully your LMS admin will be able to give you some more information with regards to the size of the projects/content and what may be possibly causing the issues.
Just to clarify, published SL files with the Captivate demos work well outside of my LMS. So I fully recognize the our LMS could be the problem. I've contacted our LMS admin to share my concerns and she has conducted a review to the best of her ability. In short, there was nothing that she was able to "See" to indicate a problem. In light of our internal limitations, I thought the SL debug log (see attached) would be helpful. Unfortunately, I don't have the necessary skill/knowledge needed to decode the log in order to find, if captured, the problem related to the sluggish loading of the CP demos.
This post has prompted me to ask, How can I translate the debug log into usable information? I would be happy to share the log. Since I wasn't able to upload the log, I would need an alternate methof for sharing.
I just noticed that I didn't include valuable insight provided by Ashley Terwilleger. Thank you Ashley for getting me started on a corrective path and to Christine for providing additional support:
Exert from Ashley Sent 7 days ago
Hi Kim,
My apologies that you haven't heard from anyone in the community yet, and I'm not sure if you've solved the issue yet - but I did want to refer you to a few troubleshooting steps:
Have you tested the course out at SCORM Cloud to see if it's something within the Storyline file or the LMS? SCORM Cloud is a free, industry standard testing site: http://scorm.com/scorm-solved/scorm-cloud-features/
You mentioned changing the original XML and XSD files, but I wasn't clear if you changed those within Storyline's published output. If so, we're unable to offer support for modifications to our published output.
Lastly, have you contacted your LMS team to see if they're aware of any issues on their end which could be causing the behavior?
6 Replies
Can anyone offer a helping hand?
Hi Kim,
I wish I could help, but it sounds like it may be specific to the LMS or modification to the files you've made.
You could try testing it on a different server, to see if it's specific to the LMS, if you'd like.
You could try using SCORM Cloud.
Another option would be to use our Tempshare server. Just keep in mind that this server is only available for testing content - it is not officially supported by Articulate and all content will be removed automatically after 10 days.
In addition, you could also use Dropbox. Just remember that you'll need to place your content in the "Public" folder. Also, you'll need to make sure that the folder is enabled. To do so, click on this link.
You're always welcome to try out Articulate Online, as well - it's available for a free 30 day trial.
Hi Christine,
Thanks for the suggestions.
Over the last few days the problem has persisted. I've also discussed the situation with our LMS admin and, so far, we don't have an answer as to why this is happening. To that end, I've just discovered how to Enable the SL's Debug Mode (see link: http://www.articulate.com/support/storyline/how-to-enable-lms-debug-mode) so we are continuing to research the problem.
However, all is not lost. The problem I described impacted 2 courses with captive demo swf files that was about 4K KB and the other at 6K KB originally. I started to suspect that file size was a problem. Captivate compressions were already in place (Advanced Project Compression & Compress SWF File boxes were checked in one file and Compress Full Motion Recording SWF File was checked for the other). In both courses I eliminated any unused objects from the library and ultimately got one CP Demo down to 2K KB and the other was just above 5K KB.
The course with the 2K KB started loading immediately..... YEAH!
The other course continued to have problems. In order to move past this problem, I split the demo in two (one CP demo had a 4,513 KB swf file size and the other was 1,748 KB swf file). Both demos now open as intended.
The only conclusion I can draw is size matters. We are continuing to diagnose the problem to see what additional answers I find. Will post additional findings.
Hi there Kim,
Thank you very much for that excellent information. I'm happy to hear that you were able to make some progress with this.
I'm still curious to hear whether or not the original (larger) versions worked well outside of the LMS. If not, then it might be something to look into from our side. If so, then hopefully your LMS admin will be able to give you some more information with regards to the size of the projects/content and what may be possibly causing the issues.
Thanks again for the update - I appreciate it!
Best,
Christine
Hi Christine,
You are welcome.
Just to clarify, published SL files with the Captivate demos work well outside of my LMS. So I fully recognize the our LMS could be the problem. I've contacted our LMS admin to share my concerns and she has conducted a review to the best of her ability. In short, there was nothing that she was able to "See" to indicate a problem. In light of our internal limitations, I thought the SL debug log (see attached) would be helpful. Unfortunately, I don't have the necessary skill/knowledge needed to decode the log in order to find, if captured, the problem related to the sluggish loading of the CP demos.
This post has prompted me to ask, How can I translate the debug log into usable information? I would be happy to share the log. Since I wasn't able to upload the log, I would need an alternate methof for sharing.
I just noticed that I didn't include valuable insight provided by Ashley Terwilleger. Thank you Ashley for getting me started on a corrective path and to Christine for providing additional support:
Exert from Ashley Sent 7 days ago
Hi Kim,
My apologies that you haven't heard from anyone in the community yet, and I'm not sure if you've solved the issue yet - but I did want to refer you to a few troubleshooting steps:
Have you tested the course out at SCORM Cloud to see if it's something within the Storyline file or the LMS? SCORM Cloud is a free, industry standard testing site: http://scorm.com/scorm-solved/scorm-cloud-features/
There are some additional LMS Troubleshooting tips in this article: http://www.articulate.com/blog/troubleshooting-lms-issues/
You'll want to follow the steps outlined here for inserting captivate content into Storyline: http://www.articulate.com/support/storyline/how-to-insert-captivate-content-into-storyline
You mentioned changing the original XML and XSD files, but I wasn't clear if you changed those within Storyline's published output. If so, we're unable to offer support for modifications to our published output.
Lastly, have you contacted your LMS team to see if they're aware of any issues on their end which could be causing the behavior?
This discussion is closed. You can start a new discussion or contact Articulate Support.