I am trying out SL360 and I run into a very ugly problem. When using Chrome (version 54.0.2840.99 m) the sharpness of text and images go from very blurry to sharp depending on the size of my browser window. IE11 neither SL2 has this problem.
I do want the ability to scale the output (player options, Player size: Scale player to fill browser window). Does anyone know this problem and how to overcome this?
This is a competitive issue for the hole AS community, please keep us updated!!! I have also 3 projects in risk because of this quality bug. We are in your hands to solve this problem and keep making high quality courses. Need a solution ASAP. Thanks.
As I'm reading this thread, it seems everyone is having this problem on SL360 but I have the same problem in SL2 with my text and images transitioning from blurry to sharp within the slides. Increasing the quality doesn't help either. It also appears to be isolated to Chrome. Has there been a fix for SL2 for this issue?
There was an issue introduced in an earlier version of Chrome that contributed to this blurriness, and that has been fixed up by Chrome. Our team is still looking into additional settings to adjust that would resolve the rest of the issues. It's something that we've seen reported mostly in Storyline 3 and 360, based on our increased HTML5 support and how the rendering was modified in the newest versions.
In Storyline 2 are you also viewing the HTML5 output? You mentioned transitioning from blurry to sharp, do you mean while viewing the course it changes? Could it be a loading delay - any easy way to test is reloading/refreshing the existing page to see if it starts again as blurry/sharp.
Still experiencing the bug in Chrome 61, using Lato font. I attached some screenshots (one with firefox and one with chrome) to let you see the difference.
It appears that the latest Chrome version 62 has resolved the issue of blurry text and images. While the player text and elements still appear slightly blurry to me, it isn't a deal breaker since it is a vast improvement. I've attached a screenshot that includes a side to side comparison with Firefox. However, I just wanted to confirm that it appears an acceptable fix has been implemented.
This e-mail and any attachments may contain information which is confidential, proprietary, privileged or otherwise protected by law. The information is solely intended for the named addressee (or a person responsible for delivering it to the addressee). If you are not the intended recipient of this message, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete it from your computer.
I'm curious to see what others are seeing. Maciej, it would be helpful to see a screenshot of what you are seeing as well to confirm the problem on your end.
Alicia, screencasts are usually blurry due to compression settings which can be adjusted when you publish your course. However, if you provide a screenshot, which includes your player elements as well, it would help determine if it is indeed related to the Chrome issue.
When you set up web based training, one of the things you need to do is pre-size your graphics. If you choose to resize your graphics in Storyline you're going to get blurry graphics. Even one pixel up or down it will blur. Try it with your problem graphics, size one to the correct dimensions before placing the graphic and size another up or down in Storyline and preview it in a browser and you'll see what I mean.
Thanks for continuing to share your experience here. Our team is continuing to look into some of the blurry display issues that are appearing in the Chrome browser specifically.
Pano, it's good to know that yours is appearing much better than before! It may also help folks if you could share additional information about your course set up such as: story size, player/browser scaling settings, publish quality chosen, etc.
Alicia, just a note that replying via email will include your signature. You can edit out your contact information from your post if you'd like!
Richard, your correct that any scaling of an image in Storyline (whether when you insert it or as a part of scaling the published output) will result in a change to the image quality. We have some best practices for working with images and media detailed here.
I've found this too - and It was prompted by zoom-region issues; FF is crisper (not perfect, though) - so I'm guessing SL is doing some mass compression on everything before output.
So, just to throw another suggestion in the mix:
Something which kind of helps is by making a stupidly large template (1920x1080 -- full HD); and then, this gets scaled down. It's not ideal, of course: things are still blurry, and actually uncomfortable to read (because your eyes are fighting to try focus) but it 'feels' better than the distortion / pixelation that occurs with up-scaling.
.tif files seem to maintain some better clarity, but you still get artefacts.
I'm just adding my voice to the crowd here. I too am experiencing this in Articulate SL 360 with the latest version of both Chrome and Firefox. I'm building a screenshot heavy course (pulling in the screens as PNGs. My source images are clear as day, they look good when authoring but HTML5 in Chrome is really blurry. Using highest quality on publish. It looks great when I publish to Flash only (had to enable flash on Chrome) but awful on HTML5. I'm publishing to 360 review for now to check quality. Any updates?
Sorry to hear this problem is affecting you as well, Leah. Our team is still looking into a fix, and you're in the right place to stay up-to-date on this bug's progress.
I'm really sorry you're still facing this bug, Stephen. This issue is a priority for us, and our team is heads down working on a fix. We'll notify everyone here as soon as it's released, and you'll be updated immediately since you're now subscribed to this thread.
I can see that you’re still struggling with font issues since you reached out here and in this other discussion. I’d love to help. Can you take a look at the questions I asked in the other discussion? We can keep the conversation going over there!
I am in the latest version of Chrome with html5 output on Chrome. It is very blurry. Users complaining they cannot view. We have many users using Chromebooks so Chrome is the only option. Also, we must use html5 due to flash not running on some of our computers. Please fix this problem ASAP. This seems like a major flaw.
So sorry you're hitting this too, Amy. We know this is causing headaches for our customers, and our team is looking closely at what we can do to remedy this. As soon as we come to a solution, we'll let you know!
199 Replies
This is a competitive issue for the hole AS community, please keep us updated!!! I have also 3 projects in risk because of this quality bug. We are in your hands to solve this problem and keep making high quality courses. Need a solution ASAP. Thanks.
As I'm reading this thread, it seems everyone is having this problem on SL360 but I have the same problem in SL2 with my text and images transitioning from blurry to sharp within the slides. Increasing the quality doesn't help either. It also appears to be isolated to Chrome. Has there been a fix for SL2 for this issue?
Hi Sou,
There was an issue introduced in an earlier version of Chrome that contributed to this blurriness, and that has been fixed up by Chrome. Our team is still looking into additional settings to adjust that would resolve the rest of the issues. It's something that we've seen reported mostly in Storyline 3 and 360, based on our increased HTML5 support and how the rendering was modified in the newest versions.
In Storyline 2 are you also viewing the HTML5 output? You mentioned transitioning from blurry to sharp, do you mean while viewing the course it changes? Could it be a loading delay - any easy way to test is reloading/refreshing the existing page to see if it starts again as blurry/sharp.
Still experiencing the bug in Chrome 61, using Lato font.
I attached some screenshots (one with firefox and one with chrome) to let you see the difference.
It appears that the latest Chrome version 62 has resolved the issue of blurry text and images. While the player text and elements still appear slightly blurry to me, it isn't a deal breaker since it is a vast improvement. I've attached a screenshot that includes a side to side comparison with Firefox. However, I just wanted to confirm that it appears an acceptable fix has been implemented.
No changes for me, still all blurry.
Chrome 62.0.3202.89 64bit
I'm sorry to hear that. Out of curiosity, did you clear your cache? Also, do they images I attached appear crisp you?
Can't tell on 100%, but im afraid they are not. The bluryness is very much visible when you scale (specially down) your course.
My screen casts are still quite blurry. No change whatsoever.
Alicia Barrientos
Instructional Designer
CEANNATE CORP
T: 888-853-8148 ext. 4308
Ceannate Companies
www.ceannate.com
www.fmsdc.com
www.i-3group.com
www.iontuition.com
www.authenticaid.com
This e-mail and any attachments may contain information which is confidential, proprietary, privileged or otherwise protected by law. The information is solely intended for the named addressee (or a person responsible for delivering it to the addressee). If you are not the intended recipient of this message, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete it from your computer.
I'm curious to see what others are seeing. Maciej, it would be helpful to see a screenshot of what you are seeing as well to confirm the problem on your end.
Alicia, screencasts are usually blurry due to compression settings which can be adjusted when you publish your course. However, if you provide a screenshot, which includes your player elements as well, it would help determine if it is indeed related to the Chrome issue.
When you set up web based training, one of the things you need to do is pre-size your graphics. If you choose to resize your graphics in Storyline you're going to get blurry graphics. Even one pixel up or down it will blur. Try it with your problem graphics, size one to the correct dimensions before placing the graphic and size another up or down in Storyline and preview it in a browser and you'll see what I mean.
Hi all,
Thanks for continuing to share your experience here. Our team is continuing to look into some of the blurry display issues that are appearing in the Chrome browser specifically.
Pano, it's good to know that yours is appearing much better than before! It may also help folks if you could share additional information about your course set up such as: story size, player/browser scaling settings, publish quality chosen, etc.
Alicia, just a note that replying via email will include your signature. You can edit out your contact information from your post if you'd like!
Richard, your correct that any scaling of an image in Storyline (whether when you insert it or as a part of scaling the published output) will result in a change to the image quality. We have some best practices for working with images and media detailed here.
Here are my course settings before and after the fix:
Thanks for those details, Pano! I'm sure that will be helpful for the other folks who are seeing the same issue.
This post was removed by the author
I've found this too - and It was prompted by zoom-region issues; FF is crisper (not perfect, though) - so I'm guessing SL is doing some mass compression on everything before output.
So, just to throw another suggestion in the mix:
Something which kind of helps is by making a stupidly large template (1920x1080 -- full HD); and then, this gets scaled down. It's not ideal, of course: things are still blurry, and actually uncomfortable to read (because your eyes are fighting to try focus) but it 'feels' better than the distortion / pixelation that occurs with up-scaling.
.tif files seem to maintain some better clarity, but you still get artefacts.
Hi there,
I'm just adding my voice to the crowd here. I too am experiencing this in Articulate SL 360 with the latest version of both Chrome and Firefox. I'm building a screenshot heavy course (pulling in the screens as PNGs. My source images are clear as day, they look good when authoring but HTML5 in Chrome is really blurry. Using highest quality on publish. It looks great when I publish to Flash only (had to enable flash on Chrome) but awful on HTML5. I'm publishing to 360 review for now to check quality. Any updates?
Sorry to hear this problem is affecting you as well, Leah. Our team is still looking into a fix, and you're in the right place to stay up-to-date on this bug's progress.
The original post is over 1 year old now and there is still no solution. Is there anything you can tell us about when this is going to be fixed?
I'm really sorry you're still facing this bug, Stephen. This issue is a priority for us, and our team is heads down working on a fix. We'll notify everyone here as soon as it's released, and you'll be updated immediately since you're now subscribed to this thread.
This post was removed by the author
Hi Alexandra,
I can see that you’re still struggling with font issues since you reached out here and in this other discussion. I’d love to help. Can you take a look at the questions I asked in the other discussion? We can keep the conversation going over there!
I am in the latest version of Chrome with html5 output on Chrome. It is very blurry. Users complaining they cannot view. We have many users using Chromebooks so Chrome is the only option. Also, we must use html5 due to flash not running on some of our computers. Please fix this problem ASAP. This seems like a major flaw.
So sorry you're hitting this too, Amy. We know this is causing headaches for our customers, and our team is looking closely at what we can do to remedy this. As soon as we come to a solution, we'll let you know!
Hopefully the Articulate team is working with Google to try and resolve this.
This discussion is closed. You can start a new discussion or contact Articulate Support.