is it possible to shorten the delay when clicking "prev" button?

i think it can't be my pc's problem...

my client also has this issue as well, he was running on his Mac pro

As Steve says it shouldnt be that slow, there is an intelligent preloader built in.  Does it happen on all slides or just specific ones?

If it is specific slides I would look at what is on those slides

And what format was the content in--native Flash, HTML5 or iOS?  Were you previewing locally or viewing with content on a web server?

i tested my module both locally and on a web server. The delay occurs regardless of where i test it. 

There are delays whenever i click on either buttons for almost every slide.

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

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.

I see what you mean with the delay. I'm seeing a 1 to 2 second inconsistent transition delay between some slides. You might want to submit this as a trouble report to see what the technical team can figure out. 

Alright, i will install storyline on another pc and see if it improve or not, i will update on that.

Thanks Steve.

Meanwhile, How do i file a trouble report?

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?

Hi Gerry,

I have attached the story file.

All the states on the buttons are in the file.

Please feel free to test the files and tell me what you think.

Thanks

That is one strange file you have there, I think Gerry caught it, It is something to do with your on slide next and previous buttons.  If you delete them the transition is instantaneous.

I just dont know why, the publish time is really slow as well. 

Worth reporting

If that doesnt sort it, the first thing I did before deleting the buttons was to import it into a new file

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?

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 . . .

There's really no reason why it should behave like that. I think the support and dev team would love to look into it

http://www.articulate.com/support/contact/

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.

I'm using custom buttons on my slides as well, though Im pushing them down to the slide master. I'm also controlling visibility of the buttons through triggers and variables. Haven't noticed any delays.

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.

Hmm, did my experiment.  Not seeing any speed increases with buttons on the masters, especially on complex slides.  I'd call it a wash . . .

I dont think it is if they are on masters or not. 

Eddie's file was slow using the player buttons, it was only by deleting the custom buttons that the speed increased.  It must be a bug somewhere, would be worth sending to Magnus

Thanks a lot for all of your help.

i hope this can be fixed soon. 

Eddie have you reported this to Articulate?