Storyline 3 - Update 3 Released Today

Our latest update to Storyline 3 is available today! 

 

You can see the new features and bug fixes we've added to Storyline 3 since the last update listed below, or the entire list since the initial release in the Storyline Version History here. Updates are free for Storyline 3 licensees. Download the latest update here.

  • The new text-rendering engine for Storyline 3 allows text to flow beautifully with consistent spacing and readability on every device. And learners will always see the correct fonts for variable references and data-entry fields in HTML5 output. Learn more about modern text.
  • Storyline 3 users can now open Storyline 360 project files that have text-to-speech narration, random number variables, and course completion triggers. Compatibility details here
  • Fixed: Published content stored on your local computer wouldn't play in Google Chrome 64 and later.
  • Fixed: We fixed some drag-and-drop issues in HTML5 output, such as drag items that wouldn't drop on targets, interactions that were marked as correct even when learners answered incorrectly, and hover colors that were wrong.
  • Fixed: We fixed some triggers that didn't work consistently in HTML5 output, including key-press, hover, and click-outside triggers that didn't fire when expected.
  • Fixed: Right-click triggers displayed a context menu in some HTML5 browsers.
  • Fixed: We fixed some HTML5 quizzing issues, such as the Review Quiz button not working when a course was set to never resume, matching drop-down choices that overlapped during quiz review, and question banks that displayed the same set of questions after three quiz attempts.
  • Fixed: We fixed some issues with HTML5 output in Internet Explorer and Microsoft Edge, such as flickering that appeared when navigating between slides and crashing that occurred when text had shadow effects.
  • Fixed: Videos wouldn't replay when revisiting slides in HTML5 output in Firefox.
  • Fixed: Lots of videos in a course could cause slides to lag or lock up in HTML5 output, and they could be sized or positioned incorrectly during preview.
  • Fixed: Audio continued to play in HTML5 output when switching to another browser tab, causing animations to become unsynchronized.
  • Fixed: JAWS screen readers would announce selected answer choices as "not checked" in HTML5 output.
  • Fixed: Zoom regions wouldn't work in HTML5 output when they were set to start at the beginning of slides, and they wouldn't always return to their initial states when revisiting slides.
  • Fixed: Data-entry fields didn't have focus when slides loaded in HTML5 output, so learners had to click inside them before entering text.
  • Fixed: We fixed some issues that could occur after upgrading project files to Storyline 3, such as blank slides, white borders around slides, and brief flashes or flickers between slides in HTML5 output.
  • Fixed: In the responsive mobile player, the seekbar was interactive even when it should have been read-only and the course menu would sometimes jump to the wrong slide.
  • Fixed: Closed captions in Flash output didn't display special characters, such as accented letters and apostrophes, and the captions were the wrong size after changing the player font size.
  • Fixed: We fixed some LMS issues, including accented letters in course titles that were replaced by question marks in SCORM output and courses tracked by the number of slides viewed reporting a Passed status rather than a Completed status.
  • Fixed: When the audio editor was zoomed in, you couldn't always delete portions of the waveform, and the waveform might be out of sync with the audio.
136 Replies
Alex Arathoon

Another issue - objects which should be hidden on the base layer appearing on slide layers. I have set the option to hide objects on the base layer, prevent user clicking on base,  ensured object wasn't selected to view under 'Base Layer Objects'. All other objects aren't visible only certain ones...

The object is a button with a glow effect which would only show if the object hasn't been selected - and associated Slide layer not viewed. So it's the button that was selected that shows through. I created a variable to track if the object was viewed. If it wasn't it will glow on rollover can be selected.

This effect was created using a new state and not a hover state - as the effect should not be visible if the Slide Layer was viewed.

The native hover effect is only visible on the base layer. However, as it's a hover it keeps showing the glow effect even if it's been selected.

Anyone see this? have a resolution? 

** UPDATE ** - the object has a hover state when invoked on the base layer this shows through on slide layers. The workaround is to create a  shape to mask this. I don't recall having to do this in SL2



Michael Laudone

Just got a Win10 machine and installed this update. Am working on a project with motion paths and when I add it, the end state is now SOLID, not semi transparent like it has been, making positioning impossible. Couldn't find a setting to change this...can't imaging why anyone would want it this way...help?

Ashley Terwilliger-Pollard

Hi Celeste, 

I'm sorry you're seeing an error about corruption. It's difficult to say what could have happened without knowing more about your file or set up, but I'd start with the steps below to try and find a working version of your file: 

1. Open this folder in Windows Explorer:  

%appdata%\Articulate\Storyline 

2. Scan the contents of this folder for a file that starts with the name of your project. If you find one, copy it to your desktop. If you find more than one, copy the latest version to your desktop. 

3. Change the file extension of the copy on your desktop from *.tmp to *.story. 

4. Double-click the file to open it in Storyline. 

After that, double check that you're following our best practices here to prevent future corruption. 

Michael L, 

Do you still have this file set up? Can you share it with our Support Engineers who can take a look at the transparency issues you're seeing in Update 3.

Michael K, 

I saw you previously worked with my colleague Leslie and  Robert in a case. We confirmed this custom font is not working as expected in the HTML5 output, but noted that applying the bold formatting resolved it. I understand if you're not able to use that set up right now, but this issue is specific to that font. I don't know much about font types, but if you'd like I can have Robert touch base with you again? 

Andy Carter

Reading this thread and other comments elsewhere, I'm wondering if it's safe to use this latest update?

There is very little new functionality and a lot of the bug fixes seem to have introduced new bugs. Are any users getting any benefit from this latest version of SL3 or should we wait until the next update which will hopefully give us additional functions and bring us into line with SL360 users?

Articulate are normally superb at looking after their users. They seem to be dropping the ball with SL3.

Ashley Terwilliger-Pollard

Hi Andy,

I'll let folks in the community weigh in on using this update, but a number of the issues mentioned in this discussion and others are still on the list to be fixed and were not introduced as a part of this update.

Update 3 of Storyline 3, brings the compatibility of Storyline 3 and Storyline 360 back in line as they have the same fixes right now. As for new features, Storyline 360 will always be ahead of Storyline 3 and receive the new features you've seen in recent updates such as: 

Jeffrey Riley

I have the current SL3 update 3.3.15007.0 but am still having issues. 

There is a problem when I change a trigger. The lookup window to select the target is much too wide.

It does not matter where I move the window, the look up keeps going to the right. I am attaching a picture of the trigger lookup.

I also do not have the text to speech option in Audio. Audio Menu

Jeffrey Riley

Color me perplexed. This is only happening on one course. I am attaching it to this post. I do have the course maximized and undocking and re-docking did not help.

At first, I thought it was because I converted it from SL2 but the other courses are fine.

I hate to rebuild this course because it is two languages and it took a long time to work out getting results in one slide! I still have the issue where if I move a results slide the variables disappear. I have that in another post.

Alex Arathoon

My experience so far has been fairly good apart from a few quirks. The biggest benefit is improved HTML5 output. Although some of my text boxes had to be resized as it was illegible - related to a custom font the text was called from a variable. Also mentioned earlier that some base layer buttons with hover state showing through on slide layers. Using a workaround.

It would be good to have two versions of SL3 running so you could always use the prior version if quirks occur.

Also found in the previous version Completed/Incompleted SCORM is not reporting properly. It reports as passed/failed. Yet to check if this update resolves.

Now I've upgraded looks like I can't go backward - hoping I don't run into too many issues.




Ashley Terwilliger-Pollard
Alex Arathoon


Also found in the previous version Completed/Incompleted SCORM is not reporting properly. It reports as passed/failed. Yet to check if this update resolves.

Hi Alex,

Is it not reporting correctly or when you open Storyline back up you see that the publish settings did not save? This is something our team has seen as well and reported as a bug - but it should be publishing with the correct settings and sending those to your LMS as you'd expect. 

If you're not seeing that, can you please reach out to our Support Engineers here to do some additional testing?