"Reset to Initial State" Doesn't

Hi, thanks for the response. The only triggers are to disable Next when timeline starts then set to normal when the two buttons are clicked. Again, navigation is set to restricted and When revisiting is set to "reset to initial state".

Navigation restriction shouldn't affect it. I'm wondering if something in the slide is preventing the slide from retriggering the trigger. Like maybe when you return to the slide it's not going back to the beginning of it to actually trigger the trigger to hide the Next button. Do you have any slide layers that have triggers on them?

Nothing I can think of. Just the 2 buttons that, when clicked, show a layer. No other triggers exist on either of those 2 layers. I'm under a tight deadline (aren't we all) with a client that is testing the output backwards and forwards and everything in between. Storyline seems to have issues accounting for navigation that could occur in more than one way - i.e. if the slide ends THEN buttons are clicked, or vise versa, when buttons are clicked THEN the slide ends. 

I hear ya....Try adding a cue point right at the beginning of the base layer and a trigger that says to hide the Next button when the timeline reaches that cue point.

Will try it out. Thanks. Just creates an inconsistency in appearance where most slides have the button grayed out, but slides that have buttons to click have no Next button until a certain cue point or trigger is hit.

Thanks again for your help.

No Problem.... the reason I think that may work is I worked on an interaction yesterday where selecting a hotspot was set to cause a viewed slide layer to continue playing, but for whatever reason I had to click it twice to get it to work. So I added the same command a second time and it worked. So maybe it will work for you! Let me know if you have any luck.

Yeah, I bet Storyline's doing something similar to me. Thanks!

What I ended up having to do: Add a variable "Proceed" set to False and change it to True when timeline ends. Add function to Next button to advance to next slide only IF Proceed = True. Ugh, good thing I'm made of time. *grumbles*

It's a shame Storyline's "Reset to Initial State" doesn't reset to initial state.

Glad to hear you got it working. That's frustrating though. I haven't run into this issue but similar issues as I pointed out earlier. Still I gotta say I love Storyline 2. At least in comparison to Captivate 7 and 8. I had to reset just about every advanced interaction I made. Such a waste of time!

True. I use both but for different course types. I find that both have strengths and weaknesses. It almost seems like Articulate and Adobe get together and say: "Hey, we'll be really good at x but really suck at y, you be really good at y but suck at x...". lol

True. There are some features I definitely miss from Captivate. But not many. Development in SL2 has proven to be much less aggravating for what I do most of the time. I miss working in Flash though more than anything.

JMHO but I have found Storyline to be much better for softskill type eLearning but prefer Captivate for more screen capture based, step by step eLearning. Oh, and it's 2015 but still don't have a video export option from Storyline?!? Yikes.

That said, love the tech support of Articulate hands down above Adobe/Captivate.

Hi Jim,

Without seeing it, it's difficult to say but restricted navigation does impact the next button in Storyline 2, in that the user isn't able to proceed using the next button until the slide's timeline has ended. Also, here is information on how "reset to initial state" works in Storyline.  

If we can offer any other assistance, please feel free to let us know. 

Hi Ashley (one of the support folks that make Articulate great),

I would share our content but would have to have you sign a non-disclosure agreement :-/ . Anyway, I would LOVE to do a web meeting with you folks, show you my pain and how your current offering is inconsistent in how it processes triggers, variables, and functions - based on a variety of ways clients might interact with the slide in question. I started a long thread a few weeks back re this same type issue and with the help of the wonderful community and your awesome support staff thought I found a solution. But the same "solution" is inconsistent from interaction to interaction on different slides. Knowing me, you might be able to say "that's not how you should do it, do it this way." and all would work fine. I'm thinking that's what it may take. Maybe we both come away with better eLearning dev insight?

Thanks Ashley.

Another question. Why, if navigation is set to Restricted, isn't the Next button automatically set to disabled - i.e. grayed out? In what scenario can you tell me why in the world if a user can't click Next until the end of a slide, the Next button should appear AND animate (have a clickable animation) when, in fact, the Next button will not work??? If navigation is indeed restricted, why not have the Next button disabled by default until it will actually work - at the end of the slide?

Thanks Jim - nice message to start with. ;-) 

We're happy to sign an NDA - you'll just want to indicate that as such when reaching out to our team here.  You'll want to link to this thread and the other one where you may have gotten some additional help. 

As for the why, I couldn't answer that as I'm not a part of the development team - so I wouldn't want to speculate either. But again, if you want to connect with the Support team, they can walk you through things a bit more one on one, and we can go from there. If you choose to go that route, let me know once you've submitted the case so that I can follow along. 

Thanks, Ashley. I've contacted them to meet and discuss. Looking forward to their response.

Thanks Jim - and I share the information here with our team as well. 

I am dealing with a similar problem. The details:

• I have a freeform slide.
• There is a drag and drop box on the slide. This drag and drop box is not part of the interaction. It is only there to help learners gauge the distance between the buttons.
• The user can select multiple buttons on the slide.
• The user has a single attempt.
• If the user answers incorrectly, they are sent several slides backwards to review the material and try again.

Similar to Jim, the first time the learner goes through this things are OK. The second time, though, all the buttons are inactive. In my mind, the buttons should be re-activated.

I have tried:

• Deleting the drag and drop. The issue remains.
• Changing the slide to "Automatically decide". The issue remains.

I'd really like to have this interaction work correctly as it's the best way to present the question. Any help would be appreciated.

Hi Steve,

Can you share the file for us to look at? It's hard to visualize what you're trying to accomplish exactly.

Hi, Steve -- May I ask if you are also testing your published output in the intended environment and are seeing the same behavior there? And I agree with Daniel; if you are able to share your file, it would be great! Please use the ADD ATTACHMENT button in the bottom left of the reply box to browse and upload your file. :)

Sorry for the delayed response on this. I was pulled away.

Some new observations:

• I tested it in the intended environment and the problem persists.
• I was stripping out the majority of the slides so that I could post something here. I noticed that, in the shortened version, if you redirect to the first slide in the scene (rather than a slide in another scene) the problem went away. However, making this change to the main file didn't fix the problem.
• I thought this might have something to do with the number of attempts. As it stands, the user can attempt the quiz as often as they want but only get to answer a question one time per quiz attempt. If I set the question to unlimited the user can then attempt the question as many times as they like which is not what's needed.

In the example file you must get at least one wrong answer to have to repeat the scenario.

Any assistance would be appreciated.

Hi, Steve -- I seem to be having some difficulty testing your file, as your published output when uploaded to the SCORM Cloud results in what seems to be a blank project. Please click here to see what I am experiencing.  

And my apologies that I am unable to create a support ticket on your behalf, as I do not have your last name to look up your contact information in our system. You are welcome to reach out to our Support Engineers for additional assistance using this form. I will be sure to follow along with their progress, and will share relevant updates here for others who many benefit. :)