Hello, I just updated my Storyline 360. When I now publish my project, the seekbar, Playbutton and Rewindbutton are not working properly. The project contains a few slides, on which I disabled the seekbar. When I visit them in the published project, the navigation won't work afterwards.
Morning, I am having a similar issue which may be linked, I have always been using custom navigation - graphics as buttons with 'jump to slide X' triggers on them. I have also always turned off the player borders and backgrounds to get a custom look.
Now that I have updated Storyline360, the navigation doesn't work, no rollover, no function, if I reset my player to Storyline default it works... I need to release a course today and just found this! any help!?
Sonja, I'm having some luck copying and pasting each slide (one by one - pasting the scene didn't fix it) into a new SL file, not sure if that will help with your issue as yours is more with the default controls, but...
that's exactly what I mean. but I have to hide the seekbar on some slides, so it's not a good workaround for my projects. My workaround is to work in SL360 and publish in SL3, which is working, but I can't use the modern Framework.
Good news, we released Update 38 (Build 3.38.21779.0) for Storyline 360 today!
Included in Update 38 (Build 3.38.21779.0) is a fix for a recent bug where the seekbar and other player controls wouldn't work when the first slide uses custom features that does not include seekbar.
10 Replies
Hi Sonja,
Sorry to hear you're running into this issue! A few questions to dig deeper:
If you're able to share your file publicly here, that will help us narrow down the issue! Feel free to do so by clicking Add Attachment. Or you can share it privately with me here, and I'll delete once I'm done taking a look!
Hello,
it's only in the published version and only in Internet Explorer 11.
Kind regards,
Sonja
Morning, I am having a similar issue which may be linked, I have always been using custom navigation - graphics as buttons with 'jump to slide X' triggers on them. I have also always turned off the player borders and backgrounds to get a custom look.
Now that I have updated Storyline360, the navigation doesn't work, no rollover, no function, if I reset my player to Storyline default it works... I need to release a course today and just found this! any help!?
Sonja, I'm having some luck copying and pasting each slide (one by one - pasting the scene didn't fix it) into a new SL file, not sure if that will help with your issue as yours is more with the default controls, but...
Hi Steven, it's a different problem and I still couldn't solve it.
I'll attach a little testfile, maybe anybody has some advise?
Hi Sonja,
Thanks for sharing the difficulty that you're having with your project when viewing in IE11.
We are looking into a similar issue with the seekbar and player controls not working as expected if the seekbar is disabled on the first slide.
The current workaround is to enable the seekbar on all slides.
Does this fit what you are seeing as well?
Hi Steven,
It does sound like you may have been experiencing a different issue, especially if adding slides to a new file was correcting the issue for you.
We typically advise importing the slides vs. copy/paste.
Are you still having difficulty with this course?
Hi Leslie,
that's exactly what I mean. but I have to hide the seekbar on some slides, so it's not a good workaround for my projects. My workaround is to work in SL360 and publish in SL3, which is working, but I can't use the modern Framework.
I understand, Sonja.
You may want to consider installing a previous version if you'd like to take advantage of the modern player as well.
Hi everyone!
Good news, we released Update 38 (Build 3.38.21779.0) for Storyline 360 today!
Included in Update 38 (Build 3.38.21779.0) is a fix for a recent bug where the seekbar and other player controls wouldn't work when the first slide uses custom features that does not include seekbar.
Make sure to update your Articulate 360 Desktop app to take advantage of the recent bug fixes and new features!
This discussion is closed. You can start a new discussion or contact Articulate Support.