27 Replies
Han Li

http://individual.utoronto.ca/hanli88/test/story.html

This is a link to a test module i just created which has the delay problem.

when you click on "prev", there will be a circle on your cursor, or if you wait a few seconds till the "back" button shows up, same delay problem will occur when you click on it.

There are delays when i click "next" button too, but sometimes it works fine.

Thanks in advance for your help

Steve Flowers

Hey, Eddie - 

Do you have a sample to post that shows the issue? Just trying to wrap my head around what might be causing it. Are you using slide transitions, by chance?

I ran into an issue yesterday where all of my published outputs were behaving oddly. I ended up having to reload an earlier snapshot of my virtual machine and reinstall Storyline to resolve it. Sounds like there could be a similar thing going on here.

I've never noticed a delay in transition with slide jumps.

Gerry Wasiluk

Is it possible to post your story file?  Or, at the very least, all the buttons and all their states?

Through an HTTP tracker I'm seeing what I believe (though not sure) is a ton of states on your buttons.  They get reloaded from cache when you go back but it seems to take a while to process and some states have to be loaded after certain others.  So this may be causing the delay?

Han Li

Yeah, no more delays when i delete the two on slide buttons. 

but i put the two button on the slide for a reason, i want to make sure that the users have read all the information on one slide before going to the next..

is there a convenient way for me to do that with the pre-loaded "next" button if i have to delete the two buttons on the slide?

Gerry Wasiluk

Hey, Phil!   Getting the same thing as you.

Also seeing it on one some of my courses that use custom buttons.  Going forward is speedy but going back often has a delay.  Almost as if things get re-downloaded into cache or re-processed from cache at least twice or sometimes even more.

I'd file a bug and have Articulate look it.  I beginning to question my use of custom buttons . . .

Phil Mayor

I think its something with those buttons, never seen it before and most of my courses have custom navigation buttons.  Try rebuilding them.

Not sure why you need to force the user to read the content though.  If you have a form of assessment you can ensure they assimilated the information and if they pass the test without reading the content, well they didn't really need to take the course. 

BTW You are not ensuring the user is reading the content, just delaying them pressing next.  This will annoy users who want to revisit the content at a later date as they will be stuck until the next button appears.

Phil Mayor

Gerry, I agree with Steve.  I think Dave M explained the preloader as:

It loads three slides (the current slide +2slides ahead) it also loads any slide that branches off the current slide.

The problem may be on the previous trigger, but the preloader should be catching this.

Do not think this should happen.

Gerry Wasiluk

Phil Mayor said:

Gerry, I agree with Steve.  I think Dave M explained the preloader as:

It loads three slides (the current slide +2slides ahead) it also loads any slide that branches off the current slide.

The problem may be on the previous trigger, but the preloader should be catching this.

Do not think this should happen.


My custom buttons are not on the masters yet.  So that may explain why Steve is getting good results.  Have to remember that for future projects.  May have to experiment with that later today on one course . . .

When it is faster moving forward to a slide that the learners have not seen then it is going back to the same slide after they have seen it, then something amiss may be happening.