Low on Memory?! Cant save!

@Johnathan Brouwer thanks the patch seems to be working for me

Storyline isnt powerpoint, not sure you can compare the memory usage.

I've got a deadline next week and Storyline keeps crashing due to this memory problem.  My 'course' is a massive branching scenario with variables that track a user's success rate. 

The storyboard has been written - storyboard approved - SME  input done, hours and hours of work, and now it's all unraveling because Storyline can't handle the file size.  Other than the 'unofficial' suggestion - can we break the course up and then link it back together some how?  I have an employee near tears over this mess.

My client does not have an LMS and we will be publishing to their web-server.

Thank you!

Betsy raises am interesting question that I've been trying to figure out: is there a way for one Storyline project to "call" another, that would enable us to break up large projects (mine currently has 14 modules and is headed for 32, each with 10+ sides and each slide with at least 3 layers, audio and lots of graphics, including video).

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

Is there a timeline for 64 bit timeline of Storyline?

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.

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. 

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

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.