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
Jeffrey Riley

Ashley, now I have another program with the same problem that the window for finding a trigger runs off the screen. I converted this from PowerPoint and the other project was converted from Storyline 2. That is the only common thing about these projects. I have not had the problem with projects created in Storyline 3.

Jeffrey Riley

I am experiencing a new Storyline 3 problem. After using the program for 2 or 3 hours, I get an error message when double-clicking a slide to open it. This just happened about 6 times. I sent a message each time but I don't know if that is working. Storyline 3 seems to have more problems now than before the update.

Cheryl Hoffman

I had similar issues shortly after I had a 1TB hard drive installed. Turns out, Win7 has a special hotfix to address the issue I had - not sure if you've changed hardware recently or not, though. Run Task Manager and check the Processes tab regularly to see what Storyline is up to.

Ashley Terwilliger-Pollard

Hi Jeffrey, 

I'm so sorry you've had such trouble recently! With this many oddities occurring, I'd like to have you work directly with our Support Engineers. They'll be best suited to take a look at all these issues and get you fixed right up. 

I'll start a case for you - so keep your eyes out for an email from Support@articulate.com!

Ashley Terwilliger-Pollard

Hi Sherry,

This discussion has gotten a bit long - so I'll apologize, as I'm not sure what you're referencing! Was there a specific reply that you could point to, or can you describe the issue you're running into? 

If you need to revert to an earlier update, our Support Engineers will be ready to help. They can also confirm and check on the status of any bugs you've run into. 

CINDY LYONS

I just updated my Storyline 360 to v3.14.15225.0 because the previous version was buggy as heck. I've had to rebuild slides that had triggers to show a layer when timeline ends, that absolutely would not work. Sometimes the NEXT button in default player doesn't work. I had several people look at my files to determine what I did wrong to no avail. Nobody could see anything wrong. Has anyone else encountered these crazy quirks?

 

Leslie McKerchie

Hey Cindy - there are no stupid questions :)

In fact, it's a pretty common question - and we have a great chart to compare as a result.

Check it out here.

Now, with regards to your Next button - could you share your .story here so that we can see if we spot anything? Just point us to the problematic slide(s).

CINDY LYONS

Actually, I do have a wonky slide. I've attached the SL file below.

Slide 1.1 - Has 3 layers and each is to play when the timeline ends. On the top (3rd) layer, I have 5 chevrons that fly in, and all but 2 are to change to gray, using a "Change State" trigger. The chevrons that are to change are the Prepare for Delivery, Delivery, and Billing chevrons. Currently, all but the Prepare for Delivery changes color.

Leslie McKerchie

Hey Cindy,

Thanks for sharing your file. 

I did see what you were describing on my first pass, then I deleted the trigger because I couldn't read it and added it back in:

...and of course it's working just fine now:

That being said, with the reported behavior you are experiencing, I'd import this file into a new file to see if that alleviates the issues you are seeing.

Kevin White

Thank you for this comprehensive list Ashley, and congratulations on the updates. I have a couple of questions. Have we addressed the Absolute versus a Relative compiler script for linking out to any remote files/urls? Also, are we able to adjust the results score variable yet to align with our ability to branch and therefore subsequently assess any branching scenarios accordingly?

Ashley Terwilliger-Pollard

Hi Kevin,

The results variable is still hardcoded into Storyline - so no way to change it manually yet. 

As for the absolute vs. relative compiler script I'm not familiar with that (or at least it's not ringing a bell!). Do you have a link to another discussion where you saw this or any more information to share? If it's not something I know much about, and you didn't see it while looking, chances are it's not yet a feature - so I’ll be happy to pass your thoughts on to our product team, but you can also feel free to detail them more through a feature request!

Amanda Schuster

I updated this morning and now I am having an issue with my layer not showing. When I click on the character for the the selection they either disappear or nothing happens when before it showed the next slide layer perfectly. I had three different files based on this model and now it is not working. 

Anyone else having trouble with layer?

Amanda Schuster

Some odd troubleshooting that is occurring. If you un-hide the base characters on the layers then the layers will show up. Now while this does fix the issue of going to the layer it create another of not being able to hide the base layer items without copying or duplicating everything which makes the files grow in size. 

These files were working perfectly fine till the update.