Issues after upgrading to Storyline 3
Jun 14, 2017
Hi all,
We’ve recently purchased Storyline 3 and are now upgrading all our course files from Storyline 2 to Storyline 3.
Most things seem to work as we have hoped, but we do also find some issues.
I was wondering if anyone recognizes the problems and possibly have a solution.
(1) At the end of every course we have a little quiz. If someone gives the wrong answer we give them some feedback through a feedback-layer.
To get to the next question (or the end of the quiz) there is a button/picture on the layer and the there is a possibility to use the <right arrow>-key on the keyboard.
In Storyline 2 this worked just fine, but after upgrading the course to Storyline 3 we haven’t been able to get the <right arrow>-key trigger working!
Does anyone know how we can fix this?
(2) In all our courses we present a bit of the software by demonstrating things step-by-step. We use screen shots instead of screen recordings. In these demo-scenes the slides advance automatically (when the timeline ends) but users can also choose to move on (or back) to the next (or previous) slide by using the next (or previous)-button (Player) or by pressing the <right/left arrow> key on the keyboard. The trigger to move to the next or previous slide using the <right> or <left> keys used to work really fine in Storyline 2, but after upgrading to SL 3 it doesn’t work smoothly anymore. Most of the time, you need to click on the slide first and only then the <right/left> key will work. Often, the <right/left> keys won’t work at all.
I have the same question here, does anyone recognize the issue and knows how we can fix this?
These issues appeared in all browsers and in scorm cloud.
In Internet Explorer 11 we have encountered another issue.
(3) In several different (random) situations the browser window gets inexplicably pushed to the background, behind other programs.
It seems that when you have more than one tab opened, it doesn’t happen.
Has anyone seen this same thing?
Regards,
Chris
6 Replies
Hi Chris,
Thanks for the thorough break down! Really helpful.
1 and 2 sound similar and like an issue I've seen where the "key press" triggers aren't activated until the user presses the tab key which activates the slide in a sense which sounds similar to when you've clicked on it - that the slide has the focus. This is reported to our team as a possible software bug, so I'll connect it to this forum discussion as well to share an update with you here once we've got more info!
For 3, I know you mentioned them being random - but any examples of what those situations are? Are users opening another link or URL from the course? Something else entirely on their system that pushes IE to the back? There isn't a feature in Storyline to keep the course as the top most visible window/tab - but perhaps your LMS admin knows of a setting in the LMS or for specific browsers?
Hope that helps and let me know if you need anything else!
Hi Ashley,
Thanks for your reply.
I look forward to an update on the issue (1 and 2).
Some examples of the other issue (3) are:
* In the quiz, when users answer a question correctly they get a little feedback (A green check mark) on a layer. When the timeline of the layer ends, the course is supposed to jump to the next slide. But this doesn't seem to work ever since we have moved to SL 3. Instead, IE gets pushed back.
* Another example: when users move through a demo scene by clicking the <Previous> and <Next> buttons quickly...sometimes IE gets pushed back.
Regards,
Chris
Hm, that's definitely not something I've heard or seen myself yet. Do you have a sample course I could take a look at? You're only seeing this happen in IE11, correct - everywhere else it behaves normally? Are you hosting the content in an Learning Management System (LMS) or web server?
We are experiencing the exact same issue as described in #3 with the course browser pushed to the background. Was there a solution?
Hi Kelly,
It doesn't appear that Chris shared any more information so I don't know if he was able to resolve it. Do you know if it's happening only in one browser? Have you tested it outside your LMS as well? You could use SCORM Cloud as that testing platform - take a look at the directions here.
Hey everybody. I'm excited to let you know that we just released update 3 for Storyline 3! It includes new features and fixes - check them all out here.
One of the fixes addresses an issue where the trigger "when user presses a key" was not functioning unless you pressed the Tab key first.
Here’s where you can download and install the latest version of Storyline 3. Let me know how you make out!
This discussion is closed. You can start a new discussion or contact Articulate Support.