Hello everyone. We are having an issue with the navigation buttons (PREV and NEXT) in the Storyline Player becoming non-responsive / freezing between 1/2 and 3/4 through a linear course. The button rollovers do not work and obviously the slide advancement does not work.
How are you testing the course? Locally or hosted online? Are you viewing Flash or HTML5 or Mobile Player app? And what device / browser are you testing with?
Thanks for the quick reply. I have tested the output in IE, Chrome, Firefox, Opera, and Safari both locally and remotely on our server. It appears that Storyline's output is just too large for what we want to accomplish. Our users are waiting on files to download and render before the buttons become usable. Presenter can output what we need (at least at the moment) at 1/5th or even 1/10th the size and our users have a much smoother experience.
When/if we need the interactivity and other things Storyline can do we may come back to it later. It may also be that we are importing from PPT and that is bloating the file/image sizes. Either way, we will have to abandon Storyline for now unfortunately.
Really sorry to hear that. Storyline actually preloads published content in a specific order to help prevent that kind of thing from happening, and to make playback of your courses as smooth as possible.
Out of curiosity, does the same thing occur when changing the host server, to something like Tempshare, for example?
3 Replies
Hey Brandon!
That doesn't sound good
How are you testing the course? Locally or hosted online? Are you viewing Flash or HTML5 or Mobile Player app? And what device / browser are you testing with?
Thanks for any more info you can provide...
Hi Peter,
Thanks for the quick reply. I have tested the output in IE, Chrome, Firefox, Opera, and Safari both locally and remotely on our server. It appears that Storyline's output is just too large for what we want to accomplish. Our users are waiting on files to download and render before the buttons become usable. Presenter can output what we need (at least at the moment) at 1/5th or even 1/10th the size and our users have a much smoother experience.
When/if we need the interactivity and other things Storyline can do we may come back to it later. It may also be that we are importing from PPT and that is bloating the file/image sizes. Either way, we will have to abandon Storyline for now unfortunately.
Hi Brandon,
Really sorry to hear that. Storyline actually preloads published content in a specific order to help prevent that kind of thing from happening, and to make playback of your courses as smooth as possible.
Out of curiosity, does the same thing occur when changing the host server, to something like Tempshare, for example?
This discussion is closed. You can start a new discussion or contact Articulate Support.