Storyline 3 Visited States Appears Buggy

I downloaded the free version of SL3 to test, as we're thinking about upgrading from SL2.  I converted one of my existing files from SL2 to SL3 and found some buggy behavior with Visited states.  After all 4 buttons are "visited", the Next button should appear.  I noticed in SL3, the buttons will not stay in the "visited" state, so the Next button won't appear.  Personally, I prefer working with states and triggers, instead of variables.  I've attached sample files for both SL2 and SL3 to illustrate the difference in behavior.  Is there something I should be doing different in SL3?  I saw a similar posting for SL360.  I appreciate any assistance.

10 Replies
Crystal Horn

Hi Jennifer.  Thanks for sharing your .story files.  In the SL3 version, it seemed like the trigger to "change the state of" those buttons to Normal was firing again when returning to the main slide.  That trigger should only happen when the media ends, so I'm not sure why it happens again upon returning to the slide.  I'm going to document that specific setup for our team to have a look.

I wouldn't want to rework those slides either.  I did find that putting a condition on the trigger to change the buttons to normal (IF the state is hidden) prevented it from firing again when returning to the slide.  I hope that helps a bit with your current setup.

I'll let you know if we have any new information to share on the state behavior.

Jennifer Klach

I recently had a computer refresh - when I access SL2, now all of the icons are extremely tiny and I cannot view things easily.  I saw this article and realized my issue is widespread.  Seeing that the recommendation is to upgrade to SL3 to address the font issue,  I wanted to follow up on this reported issue about visited states.  If I upgrade to SL3, my concern is that I would need to rebuild all of my interactions that use visited states.  I appreciate any updates or information you have.  Thank you

Crystal Horn

Hi Jennifer.  I'm guessing that you're using a newer machine with a high resolution monitor.  We did update performance on high resolution displays in both Storyline 3 and 360.  The state issue that we talked about is still on our radar, too.

You may find that user interface elements in Storyline 2 are small and difficult to read on high resolution monitors—generally, monitors that are more than 2,000 pixels in width. You may need to reduce your screen resolution while working in Storyline.

Let me know if bringing the resolution down to 1900 or so helps!

Crystal Horn

Hi, Jennifer. I'm sorry that this issue is still open with our team. This bug has impacted a low number of users, and that contributes to the priority we give it. 

For now, the workarounds are to:

  • add a condition to the trigger, or
  • change the timing of the trigger from "when media completes" to "when timeline reaches"

We'll post here if there are any changes to this behavior!