I am trying to make an average size (by our standards) course just to test what happens, about 1/3 thru this project I try to publish this but it does unfortunately crash...
Publish for LMS, Scorm 2004, 4:th edition, HTML5 only with no resume.
The approach I used was to delete a batch of slides from near the end of your course, test publish. If it still crashed, I deleted more slides and tested again. After about 3 attempts, I was able to narrow it down to a range of slides. At that point, I added a few slides back in each time and published until I identified the bad slide. A little laborious but it worked.
I am curious -- what is an average or large size project? My current project (5 different .story) are all averaging around 1GB -- they are starting to crash. The largest are 1.9GB! Until this current project, we have had nothing this large.
Great question. There isn't really a typical file size for a Storyline course, as it all depends on how much media is used and your computer's processing power.
Now the recent crashes worry me–especially when you have projects to finish! This is definitely something our Support Engineers want to help with and pull a few system logs for. Would you be willing to work closely with the team here?
I’d be glad to work with your team. We are on a quarterly cycle and are looking at how we need to proceed in the future. Crashes close to deployment are frustrating.
Hi there, Roger. Thanks for circling back, and we really appreciate that!
I've opened a case on your behalf so we can dive right in. Keep an eye out for a confirmation email and an email from the team shortly. I'll follow along!
In the future, you can start a conversation with our Support Engineers by clicking this link!
10 Replies
My guess is that something corrupted in the image on Slide 52. If you delete that image, keeping the slide, then it all publishes without any problem.
Ok, thanks, yes it seems like that was the problem.
Good to hear it worked.
Hi Richard. How did you figure out that it was an image that was causing the issue? I'm having a similar problem and would to get it fixed. Thanks!
Mark,
The approach I used was to delete a batch of slides from near the end of your course, test publish. If it still crashed, I deleted more slides and tested again. After about 3 attempts, I was able to narrow it down to a range of slides. At that point, I added a few slides back in each time and published until I identified the bad slide. A little laborious but it worked.
Richard
I am curious -- what is an average or large size project? My current project (5 different .story) are all averaging around 1GB -- they are starting to crash. The largest are 1.9GB! Until this current project, we have had nothing this large.
Hello there, Roger!
Great question. There isn't really a typical file size for a Storyline course, as it all depends on how much media is used and your computer's processing power.
Now the recent crashes worry me–especially when you have projects to finish! This is definitely something our Support Engineers want to help with and pull a few system logs for. Would you be willing to work closely with the team here?
Hi Katie,
I’d be glad to work with your team. We are on a quarterly cycle and are looking at how we need to proceed in the future. Crashes close to deployment are frustrating.
Please let me know how to proceed.
Roger
I replied a moment too soon…..
[cid:image001.png@01D5858B.454C3BF0]
Hi there, Roger. Thanks for circling back, and we really appreciate that!
I've opened a case on your behalf so we can dive right in. Keep an eye out for a confirmation email and an email from the team shortly. I'll follow along!
In the future, you can start a conversation with our Support Engineers by clicking this link!
This discussion is closed. You can start a new discussion or contact Articulate Support.