Low on Memory?! Cant save!

Hi Peter and all.

I have conducted a few severe tests after the SL update 2. My config is Win7, 64k, 16 Gb. Test spec's. Before update I could build upto 150-180 slides, including multiple layers reaching 230 Mb and after publishing reducing to 45 Mb without "cant save memory" problem. Above this level I had to break my project into pieces and allowing the client only to run a training consisting out of 2 or 3 seperate downloads on their iPads. This obviously gives a less professional look.

After installing SL update 2 I fired up one of the projects and imported the two other seperate part and this is what happened:

- Importing 2 other projects of each 230 Mb went without any problem

- The first project file of 230 Mb did not increase substantially, just a few Mb. One would expect it to triple.

- Editting within the project is no problem

- Saving the whole project (now consisting of over 400 slides (and layers) went with out error messages.

- Strangely enough SL tells you that it is saving (in my case 180) slides, the original number of slides of part 1.

- The output of the whole projects remains around the 45 Mb. Also strange as, despite importing two big parts, the output remeained the same.

And last but not least. Every item in the output file worked and is accessible with speed.

My preliminary conclusion is:

- Save error message has gone

- Projectfile does not increase - strange, but welcomed

- Output file did not increase - strange but also welcomed.

And to the Articulate staff I would like to say:

Thank you VERY much for your effort, you have done a great job!

And all the best for the New Year to come!

Regards,

John

Thanks Peter & team,

Hope the problem is solved but will give you feedback if 'can't save' occurs agian

Regards,

John

Great news Peter, testing it right now

I am running update 2 now and am still seeing Storyline using alot of memory (426000 at idle for a 98,848kb project). i have noticed though that the file size when saving seems to better reflect changes to the file. i.e. when you delete large sections of a project the save file size actually reduces.

No can't save errors yet but that was mentioned as one of the fixes in the update list so I won't expect to see them again.

Hi everyone, 

We proudly released Update 2 over the weekend and are excited to hear if it helps with the memory issues you've experienced. You can learn all about it here, and download it here. 

Thanks for your patience and help!

The problem with publishing is that if you have a bigger lesson, the publishing itself takes a while and wastes a lot of time... Please hurry on this fix, it is affecting a lot of people myself included

Thanks for adding that, James. Good pointers.

And though we don't have a specific release date to offer, the next update will handle memory better. Thanks for being patient. 

I was getting this message often and as am using a 32 bit work computer so the 64 bit patch won't work for me (I am still pushing for a 64 bit but IT have concerns about supporting it on the network since it would be the only one).

Anyway long story short I get around this by publishing my work often even if I don't need to. In a different post...

http://community.articulate.com/forums/p/20663/115379.aspx#115379

...which also covered the issue of the size of the file not getting smaller even if you delete most of the content (which appears to be a related issue) it was pointed out that if you publish the project the file size will get smaller when you save it.

Since I have started periodically publishing my work I no longer get the can't save issue.

Is there a timeline for 64 bit timeline of Storyline?

Just my 2 cents in response to Jonathan's question.

I normally create each module/chapter of my course in storyline as a seperate project/.story file. Same thing with assessments.

This was mainly to allow proper tracking of completion (If your project contains slides and quizzes you can only pick one to track against when you publish the project for use on an LMS)

In doing so I ended up with the scenario you guys are referring to. Disjointed projects all belonging to he same course. I use a product called Simple Scorm Packager from JCA solutions once I have completed all my individual components.

It allows you to "roll up" these individual scorm packages or projects into one larger one. Think of it like creating a course by specifying the chapters (your individual projects) in sequence, and the program then creating a larger parent scorm package with these as items.

Works well for me, hope it can help with your projects?

http://jcasolutions.com/ssp