Storyline 3 - Update 3 Released Today

This post was all we needed, Cheryl - so I'm glad to hear it's working for you. 

Enjoy, and let us know if you have any other questions! 

I've been struggling with Character state changes in SL3's HTML5 output for a while.

There used to be a flickering, or flashing, between states and at worst, some kind of weird rubberbanding going on. I updated to the latest version of SL3 hoping it would fix the issue, and to an extent, it did...in IE and Edge, which is weird. Now, Chrome is showing the character flicker or outright half explode before snapping to the new state. It's a little inconsistent.

Can you offer a fix, or if this is a known issue?

Awesome updates, especially the one I quoted. :) I was hoping that the lightbox exit button issue (screenreader not reading it as an exit button) would be in this update, but alas I would have to wait some more. Would it possibly addressed soon?

Uhhhhhmmmmm, where's that link to submit a bug again?   :::giggle:::

It's not going to be a huge impact for me, but might for others. Markers are buggy (I've crashed SL3.3 twice formatting/inserting them). Fortunately, copying one from another slide and pasting it in is my current workaround.

Hi Rio,

The issue where tabbing to the Close button for a lightbox is only read out as "Button" that we discussed here should be fixed in Storyline 3 Update 3 as well. Not all fixes make the version history, and this one having only been reported by a few users wasn't listed. Are you seeing it not work correctly? If so, I'd love to take a look! 

Cheryl,

No worries - our Support Engineers are always standing by to help! Reach out to them here. We've seen a few odd performance issues and/or low memory errors, so it could be that which you're running into. As I said, we'll work with you to get to the bottom of it! 

Oh perfect! I'll test it out with one of our projects. Thanks!

Low memory memory error is how I would describe the behavior. Submitted a ticket. Thanks!

Thanks, Cheryl - and I got that case right off to our Senior Support Engineers who are tackling these issues with low memory. Thanks for helping us dig into this to find a solution! 

It's great to see so many bugs fixed but it's a real shame that Articulate didn't take the opportunity to provide any new features apart from the modern font update. SL360 has had several new features recently. Why hasn't SL3 been updated to in order to keep the two products in synch with each other?

I hope there's going to be an update to SL3 soon, rather than simply bug fixes.

Is anyone else experiencing an issue with the course freezing in Chrome? We've published two courses with this recent update and now the courses freeze on a particular slide when viewed in Chrome. I will submit a support ticket, but I would like to know if anyone else has experienced this.

I updated to the recent version this morning and now I'm unable to add text in a new course. And when I import a template screen, the text boxes are getting wiped out. What the heck!!?? And it was working perfectly the last time I needed to use it. I did try editing an existing file and was able to but I effectively cannot create anything new (with text) at this point.

Oh wait, I have Storyline 360, does that make a difference? Am I in the wrong thread?

HELP!!

So I've narrowed down my issue. It looks like it has to do with using buttons in Chrome. ANY button that I use to jump to another slide is freezing the course. I even opened up a brand new Storyline file, created 2 new slides, and tested both a shape as a button and Storyline's default button. Both of them caused the spinning wheel to go on forever and ever. Even the next button wouldn't work.

Has the issue of courses not resuming properly in SCORM 1.2 been resolved in this update?  I could not see this listed in the change log.

I am waiting to update to see if this release is stable.  Do you know if anyone else is seeing this or is this isolated to just this case?  Thx.

Hi Katie, 

Thanks for reaching out here, and sorry for the delay in getting back to you. Can you share this sample file with our team? They'll take a look at what's going on and work directly with you. You can reach them here and upload your .story file.

Hi Ashley,

I sent two links and a story file to the support team. Case Number: 01291983 

Hi Anna

Storyline 360 would allow you access to content library, and the last update of Storyline 360 was update 13 released March 1. Is that when you started to notice this behavior? 

I opened the file you shared and saw the text placeholders as shown here. It doesn't seem to match what you're seeing so I would want to make sure you're on the latest update of Storyline 360 which is Update 13. 

Hi Leslie,

I think you're referring to the issue where resuming the course was inconsistent for all SCORM outputs, but worked in Tin Can API. That issue was only one we saw in Storyline 360, introduced with Update 12 and fixed as a part of Update 13. As such, all the same fixes in Update 13 of Storyline 360 were ported over to Storyline 3 Update 3 - so it should be working well. 

Ah, I see it now Katie! (I was spelling your last name wrong - whoops!) 

I reached out to our team and it was assigned to a Support Engineer this AM. 

After yesterday's update, I'm now seeing the lightbox issue mentioned in this thread:

https://community.articulate.com/discussions/articulate-storyline/new-release-lightbox-error?page=2#reply-503461

I've been working as normal for months (local drive, etc.) and I was happy SL3 had recently become so stable without the memory bugs (not enough memory, can't save). After this update they started appearing like crazy. Is there somewhere I can download the November build? I've got to get my work done. I'm under deadline.

If you right-click on the Storyline 3 icon, you should see an option to Restore previous versions. We had to use that to rollback our update until we can figure out what's causing our Chrome issue.

Hi Tim,

You can reach out to our support team here as well if Katie's solution does not work for you and request the download file you need.

Thank you, unfortunately there were no previous versions saved to roll back on the exe.

I contacted support.