Problem with Resume saved state!!!

Hi Luis!

Would you mind submitting a case with us? You'll be able to upload your .story file into the case. We'll take a look and see what may be causing this problem. 

Thanks!

Thanks! Christine

I sent my project to http://www.articulate.com/support/contact/submit.php?

I have the exact same problem, when revisiting the 2nd or 3rd time there is a problem. when click on a trigger that is meant to bring me back to previous slide it disappears and im basically 'stuck' with plain white screen. 

Is there a solution?

Hi Aoife!!. Recently was released the second update for Storyline which fixes the disappearing layer issue. It's available for download at: http://www.articulate.com/freetrial

Greetings!!

I too have a problem with 'resume saved state' in Storyline :

I am asking my usesrs to choose from a list of words on a slide.  When they click on the word it changes state and takes them to another slide.

Once they have finished on that slide they return to the original slide with the list of words.

I have set the slide to resume saved state but it does'nt save the changed state of the word that was clicked.

They have to revisit this slide 9 times and I would like to show which words they have visited and which they still need to visit

Any ideas what I am doing wrong ?

Thanks

Hi Chris,

Does this work properly when you're previewing the project? Also, how are you publishing/viewing the project? Are you publishing for Flash, HTML5, Web, LMS, etc.? Are you viewing the project after its been uploaded to a web server or LMS?

Also, can you confirm you're using the most recent release of Storyline? To find this information, please click on "Help" and "About Articulate Storyline". If you're not running version 2 (1212.1412), please download and install Update 2 from the link below. Once you've installed the update, please republish and test your course.

Articulate - Download Storyline Update 2

Thanks!

Hi Christine.

We found out what the problem was with the resume saved state.

We were changing a state AFTER the change of slide,

so the triggers looked like:

-Change slide

-Change State of...

so the slide changed before the change of state could actually occur... simple now we look back on it,

So we simply moved the order around. hope other people can learn from this

Hi there Chris,

Ahhhh! Nice catch :D Very happy to hear you were able to get it working.

Thanks very much for sharing the solution.

Have a great day,

Christine

Hey Tom - This thread is a bit dated. Do you have a .story file that you would like us to take a look at?

Due to the amount of data Storyline sends to the SCORM suspend_data field when choosing to resume saved state, I typically will use custom variables and triggers to achieve the same thing.

For instance, you could create a true/false variable for each button, set to false initially.

Add a trigger to each button to first change its associated variable to true, before navigating to another slide.

Create base layer triggers to change each button to its visited state if its variable is true when the timeline starts.

Set slide to return to initial state when revisiting.

Thanks Tom for the recap of the situation and how you went about to resolve it. If it's ever something that you'd like our team to take a look at in terms of a possible bug please don't hesitate to share it here using the "Add Attachment" button or you can also send it along to our Support Engineers using the case submission form here.