Trigger Jumps to Wrong Cue

Jul 16, 2021

Hey all,

I am making an interactive video slide. I have defined sections of the video using numerous cue points on the timeline. An overlaid set of menu items uses the cues to jump to different sections of the timeline before jumping back to the menu cue point at the end of each one. In addition, there is a small portion--also defined by cues--within one section that may or may not be skipped according to the value of a previously set variable. 

Here is the problem: when the variable is set to jump over the small portion, instead of jumping to it's defined cue point about 30 seconds later, it goes back to the cue point where the menu is. If the variable is not set to jump the portion, all is well and the timeline goes right on through that portion. All the other cues and triggers seem to be working properly. I have experimented with several variations on the variable/trigger combo but it still goes awry. I even tried deleting all the cues and triggers and starting over. Still no joy.

Does anyone know of a solution or at least a reason for this behavior?

Thank you,

--Allen

.

9 Replies
Lauren Connelly

Hi Allen!

Sorry for the trouble! It sounds like the triggers are jumping to the wrong cue point. It's difficult to pinpoint the reason and/or solution without seeing the file. Would you mind sharing your project with our Support Engineers? You can upload it to them privately in a support case so they can take a look at what you've created so far!

Allen Way

Update: Angelo in Articulate support believes it may be a bug involving mishandling of some jump triggers after a pause trigger.

My workaround for the issue was to make a copy of the slide, w/o the portion to be skipped, and send users to the different slide when that portion was not called upon.

--Allen

PS. I like to help squash bugs!

Darren McNeill

Any fix for this yet?  I have a cue point 1 set at 5 seconds. At that point a button appears and I have a trigger set to pause timeline at the cuepoint 1. This works. However, The button is triggered to jump to either a cuepoint 2 or time of 32 seconds on the timeline.

When testing, the timeline (video) does pause, but when I click the button it just continues from where it paused, it does not jump to the 32 second mark.

It seems that the cuepoint and timeline triggers get confused when the Seek bar for the slide is turned off and the video controls for the video in the slide are turned on, there is no correlation.

Using cue points and jumping to timeline times wont work at all.

Is there a way to control the Video timeline and not the Slide timeline with triggers jumps?

This is important for being an accessible interactive video slide. The video timeline and the Slide timeline are working independent so if the video is paused then the timeline could still be running. I tried setting the trigger to pause the video and also pause the timeline, but then again the timeline starts but the video stays paused... confusing

 

Is this the same bug?

 

D R

this is definitely a bug that I've encountered many times. Has to do with pausing the main timeline, or a layer... No clear idea when and how it happens that it does not jump to the correct cue point. Lots of wasted time debugging which means lots of wasted money I cannot charge for. ARTICULATE, fix this asap as you're causing us to lose income!

Yuri Lopes

Yes it does.

As per usual with Articulate, it's an issue a lot of people have been having, in this case for the past 2 years, and still no fix, workaround or any help whatsoever.

 

@Walt Hamilton, i tried EVERYTHING i could possibly think as a workaround for this, and nothing works. I have 3 triggers to pause after a speech bubble, and i have 3 buttons to skip to each one. the first 2 work, the last one, never does. it always goes to a cue point i USED to have on the slide, i deleted it, and it still always jumps to the same spot, ive tried changing shapes, swapping images, using different content as button, jumping to cue point and also jumping to specific times, and all combinations possible.

nothing works, storyline just decides that after the first 2 triggers, the third one is now locked to jumping to that wrong specific time and i cant do anything

 

 

it's honestly unbelievable

Jose Tansengco

Hi Yuri,

Sorry to hear that you ran into this issue. 

The bug discussed in this thread prevents a trigger to jump to the later timeline from properly working if the slide had already executed a pause timeline trigger earlier.

I'd like to test if your file is being affected by this bug so we can notify you as soon as a fix is released. Would you be willing to share a copy of your project file here or in private by opening a support case for testing? We'll delete it when we're done. 

philip williams

I think I have an idea of what is happening on the internal functions in Storyline. The cue points are held ordered array. The cue points are assigned an order number (1st, 2nd, 3rd...) . Somehow they are not re-instantiating "jumpToCuePoint_variable" when the subsequent "Jump to" to is called. So it goes to whatever cue point was last in the variable "jumpToCuePoint_variable". I think it has to do with the jump to and play timeline and not setting the next cue point in that internal function correctly.

Scenario I had audio playing, a pause on cue point 1, another cue point 2, audio playing, a pause on cue point 3. another cue point 4, etc. While the audio played the user could click a continue button to skip to the next cue point with a pause timeline. My second Jump to cue point failed and when back to a previous cue point when I wanted it to jump forward.

Sometimes successful solution is to put a trigger "Pause timeline on this layer"  when the user clicks on button_1 immediately before my "Jump to cue point" when the user clicks on button_1 trigger.

I looked at another storyline file with the same problem and couldn't fix it. And it repeatedly jumps to a previous cue point (or time). The same timeline will jump whether using cue points or times for the jump to trigger. the eventdispatcher is broken with  cue points. I just have heart ache trying to design with this trigger.