Progress Issues When Moving Between Layers

Dec 10, 2020

Hi Heroes!

I need a hand. Or maybe just a third or fourth pair of eyes. I'm building an interactive 1'11" module that has mp4 vids, an mp3 track, and a modest array of slide/object triggers and hotspots to govern when the learner can continue through to the end. The .story file is attached for your perusal.

Essentially, if it worked as conceptualized, the learner would only ever go back and forth between the slide layers ('main' and 'oops') until they successfully navigated all the way through. Like a click your own adventure game. I've already tried building it out as different slides, and that works technically, but has less efficacy and requires chopping the video up and making it more stilted.

If you would limit your recommendations to what is given in the attachment, I would be most grateful. This is a time-sensitive project, and I would hate (or perhaps not, depending on your answer ;) to start it over on Captivate or some other application platform available to me. Thankee kindly! :)

4 Replies
Dave Cox

Hi Lance,

I'd love to help you out, but I don't know what it is you are attempting to do.

Storyline is very powerful, and the triggers, layers and states provides you with much more capability than Captivate, so I'm sure it can do whatever it you need to do. But without an idea of what that is, it is really hard to help you achieve it. Can you provide more detail?

Thanks,

Dave

Lance Wright

Hi Dave,

I'm trying to have the 'oops' layer return to the 'main' layer in my build based on the simple logic triggers I've set up in the attachment I shared. Neither slide nor object triggers on the 'oops' layer that are coded to return to a specific time or cue point on the 'main' layer will initiate a return. The best result I've managed so far was to get the video on the 'oops' layer to replay a bit of the music track from 'main', but it always fails to return to the timeline on 'main'. There's nothing that I can see, practically speaking, that should prevent this, based on the coding that's given in the .story file.

Again, maybe my prescription needs to be thicker.

Does that help?