Trigger Conditions Resetting Values

Hello. I have my slides setup with conditional triggers for the NEXT button. I have one trigger to prevent navigation to the next slide until a variable becomes True, and another trigger that could allow free navigation if another variable becomes True. These two conditions are set using an OR condition. This setup worked well in SL1. However, in SL2, each time I close and reopen the .story file, all my trigger conditions are now all of a sudden set to AND instead of the OR that I had them set to. How can this be fixed?

12 Replies
Wendy Farmer

Hi David

I've seen another thread (can't seem to find it right now) about this where the trigger displaying when you highlight the slide/s in story view is different to the trigger displaying when you highlight the same slide/s in panel view - not sure if was reported as a bug or which condition is followed by SL - whether Story view is king or the panel view...sorry I'm not much help but will be following with interest to see if it is answered.

 

david mckisick

Well, looking at the trigger in the trigger panel, it does show the correct OR value. However, when previewing the course, it fails to work correctly. When I then double click the trigger it shows it as set to AND, even though looking at it from the trigger panel overview it still shows it as OR. HOWEVER, because the course fails to operate correctly, it seems to be switching all my triggers to AND.

david mckisick

UPDATE:  Trigger conditions are definitely resetting after you close a .story file and reopen it. I have been able to workaround the issue by creating two NEXT button triggers and ensuring that my global variable is on top, essentially splitting the single trigger into two triggers that do the same thing. I should not have to do this because the same trigger setup with the OR conditions worked well in SL1. I would certainly like to know if this is intended behavior in SL2.

Ashley Terwilliger

Hi David and Wendy,

I think this is the thread that Wendy is referring to - and that was reported to our QA team for review as a bug. I don't have any updates to share on this issue, but I can add this thread to the existing report filed with our team so that we can share any additional updates here. 

Ashley Terwilliger

Hi David,

Just checking in on your case and I see that Cleo shared:

  We were able to duplicate the issue you reported on a new project file using my Storyline 2 Update 3. We have reported this issue to our Quality Assurance team for their review. I cannot offer a time frame for when or if this issue will be addressed. I would recommend, at this time that once you have set the conditions to "OR" try not to edit the trigger and if you need to do it, the issue is isolated to that specific trigger. It will not affect all other triggers with "OR" conditions unless you edit it.

We'll share any additional information here and in your case.