I recently opened a story file built in SL2 in SL 360. After adding in closed captioning, triggers to change an object's state that were built with conditions based on number variables on the master slide, no longer work. I have rebuilt the triggers, created new variables, etc., but nothing seems to work. I have ensured that the triggers fire when the timeline starts and made sure that the trigger order is correct. I know the variables are adding correctly because I have also tested that using text reference.... The only thing I can come up with is that there was some issue when converting to SL 360. I am attaching the story file. Any help will be appreciated.
I took a look through your course, and I think I see your problem.
You have triggers that say: On timeline start, check this variable, and change the state of these objects based on that variable's value.
The problem is when you return to the home screen, you are resuming from saved state - which won't trigger "On timeline start".
You can do a few things here to overcome this issue.
You can change your home screen to reset to initial state - but this would mean you would have to add more triggers to determine whether or not it's the user's first time here or not. This could get messy!
You could return the users to a different slide - identical to the home screen, but without the intro. It would merely act as a menu that you could reset to initial state every time you re-visit it.
It looks like you could simplify this whole thing by taking advantage of visited states. When a user clicks on each character, it takes them to a separate scene. When they return, the button will be in it's "Visited" state.
If it were me building the course, I'd probably go down the route of number 3 and simplify the whole thing by using visited states and button sets. :)
Let me know if this helps, or if I've got the complete wrong end of the stick! (I'm good at that...)
I think I will just take the objects off the master and place them on the content slide instead. I seem to have found something that works going that route. I built this a while back and am unsure of what I was thinking about when I decided to use the master slide --may have been the first time I worked with a pre-built template...
I had a chance to compare the two files, and I noticed some differences. In the Storyline 2 version, I noticed that not only were the characters in the slide master, but they were also on the slide.
In the Storyline 360 version, the characters were not on the Welcome slide timeline (below), just the slide master layout.
And in your triggers panels for the slide (not the master), you have lots of triggers changing the states of those characters in Storyline 2, but no triggers changing the states of those characters in Storyline 360.
I built an example file in Storyline 2 and upgraded it to Storyline 360 to see if upgrading breaks slide master triggers, but mine worked as expected.
I tried upgrading your Storyline 2 file into a new Storyline 360 instance, but I still saw the same behavior.
I agree that a visited state should be sufficient for this case, since essentially, you want the character to appear "complete" or visited once they go through the flow. Since there's no way out of the flow (navigation is pretty locked down), using the visited state should work better.
Thanks for looking into this for me. Like I mentioned in the earlier post, I decided to take the pictures off the master and just build them as buttons on the content slide. I have learned a few tips/tricks since building this last November, and am puzzled by some of my own choices. Anyway, I think I have resolved the issue with those changes and reduced some redundancy as well. I appreciate all the ideas/discussion on these boards -- I usually can find an answer to any problem I encounter while building in Storyline. This community is awesome!
Ahh I missed your last post...elbow deep in concentration 😁
Ok, I'm glad you found a way through it! Slide masters are great for maintaining consistency throughout your course, but since this is a layout that is only being used for one slide, your idea to just keep it on the live slide sounds like a good one to me!
6 Replies
Hi Laurie,
I took a look through your course, and I think I see your problem.
You have triggers that say: On timeline start, check this variable, and change the state of these objects based on that variable's value.
The problem is when you return to the home screen, you are resuming from saved state - which won't trigger "On timeline start".
You can do a few things here to overcome this issue.
If it were me building the course, I'd probably go down the route of number 3 and simplify the whole thing by using visited states and button sets. :)
Let me know if this helps, or if I've got the complete wrong end of the stick! (I'm good at that...)
Laurie, I'm going to have a look at your file that you attached.
Can you also attach the backup Storyline 2 file if you still have it? It would probably read
Dating_Violence_Module - SL2 backup.storyThanks!
This post was removed by the author
I think I will just take the objects off the master and place them on the content slide instead. I seem to have found something that works going that route. I built this a while back and am unsure of what I was thinking about when I decided to use the master slide --may have been the first time I worked with a pre-built template...
Hi Laurie!
I had a chance to compare the two files, and I noticed some differences. In the Storyline 2 version, I noticed that not only were the characters in the slide master, but they were also on the slide.
In the Storyline 360 version, the characters were not on the Welcome slide timeline (below), just the slide master layout.
And in your triggers panels for the slide (not the master), you have lots of triggers changing the states of those characters in Storyline 2, but no triggers changing the states of those characters in Storyline 360.
I built an example file in Storyline 2 and upgraded it to Storyline 360 to see if upgrading breaks slide master triggers, but mine worked as expected.
I tried upgrading your Storyline 2 file into a new Storyline 360 instance, but I still saw the same behavior.
I agree that a visited state should be sufficient for this case, since essentially, you want the character to appear "complete" or visited once they go through the flow. Since there's no way out of the flow (navigation is pretty locked down), using the visited state should work better.
How are you making out with that suggestion?
Thanks for looking into this for me. Like I mentioned in the earlier post, I decided to take the pictures off the master and just build them as buttons on the content slide. I have learned a few tips/tricks since building this last November, and am puzzled by some of my own choices. Anyway, I think I have resolved the issue with those changes and reduced some redundancy as well. I appreciate all the ideas/discussion on these boards -- I usually can find an answer to any problem I encounter while building in Storyline. This community is awesome!
Ahh I missed your last post...elbow deep in concentration 😁
Ok, I'm glad you found a way through it! Slide masters are great for maintaining consistency throughout your course, but since this is a layout that is only being used for one slide, your idea to just keep it on the live slide sounds like a good one to me!
Let us know if you need any more help!
This discussion is closed. You can start a new discussion or contact Articulate Support.