I have video on each slide that plays automatically, have set each slide to "reset to initial state" and have a "jump to slide" trigger for the same slide for each of the slides.
This was working prior to the update and I have a published SCORM output that works fine, however I have gone back into the working file to make a small change and now the "reset to initial state" it is no longer working. Was there a change with the new update that would affect this from working?
I'm happy to investigate this with you! Referencing Jana's case, our Support team connected the experience to an open bug in Storyline 360:
Behavior: Video does not play when revisiting the slide, even if the video is set to play automatically and the slide is set to reset to initial state when revisiting.
Workaround: One option is to create the following trigger: When: When the timeline starts on this slide Action: Play video Video 1
Let us know if that doesn't help or if you see something different!
I am having the same issue with a slide that has layers on it - The base layer has audio playing and a button to show another layer - when hiding the additional layer and returning to the base layer, the slide does not reset!!
I got around this by making the "hide layer" button - a "jump to slide" - but the point is.... There are clearly some issues with reset to initial state simply just not working.... why has this not been fixed?
I appreciate you sharing some additional details of what you are experiencing.
It sounds like what you are seeing is the expected behavior.
Slide layers are intended to lay information on top of the base layer. When you close a slide layer, this does not trigger the slide timeline to start over. A manual trigger, such as hiding the layer AND jump to slide (this slide) is what would be needed.
If I've misunderstood or you have an example you'd like us to take a closer look at, please feel free to share your .story file.
11 Replies
Hi Jana!
Actually, I haven't noticed any changes on my end with this setting since the update!
Would you mind if I take a look at your file? You can share it with me by using the "Add Attachment" button in this discussion.
I'll update you on my findings!
Hi Lauren,
That would be great, however I'm worried about privacy - if I add as attachment is it visible to all or just you?
Thanks,
Jana
Hi Jana,
You are correct. Sharing here posts to the public forums.
With your permission, you are welcome to send it privately by uploading it here. It will be deleted when troubleshooting is complete.
Hi Leslie,
Thank you, I have uploaded the file to the private portal.
Cheers,
Jana
Hi, I am having a similar issue... was there a fix?
Regards
Pete
Hi Pete,
I'm happy to investigate this with you! Referencing Jana's case, our Support team connected the experience to an open bug in Storyline 360:
Let us know if that doesn't help or if you see something different!
Many thanks
Yes - that sorted it
Regards
Pete
I am having the same issue with a slide that has layers on it - The base layer has audio playing and a button to show another layer - when hiding the additional layer and returning to the base layer, the slide does not reset!!
I got around this by making the "hide layer" button - a "jump to slide" - but the point is.... There are clearly some issues with reset to initial state simply just not working.... why has this not been fixed?
Hi Pete,
I appreciate you sharing some additional details of what you are experiencing.
It sounds like what you are seeing is the expected behavior.
Slide layers are intended to lay information on top of the base layer. When you close a slide layer, this does not trigger the slide timeline to start over. A manual trigger, such as hiding the layer AND jump to slide (this slide) is what would be needed.
If I've misunderstood or you have an example you'd like us to take a closer look at, please feel free to share your .story file.
Hello Everyone!
I'm happy to return to this discussion with an update—we've fixed the issue where the:
Be sure to install the latest Storyline 360 update (Build 3.50.24668.0) to take advantage of all the recent features and fixes.
If this happens again, please let us know! Or you can work directly with our support engineers here.