I have noticed this problem for some time, but was hoping an update could fix it. I am running Storyline 3.0 and have all of the latest updates, but my characters are still "jumping" when changing states.
When they go from normal to talking, for example, there is a "jump" in the whole screen.
I have seen a discussion on this, but can't find it and wondering what the update on this issue is.
According to SL3 version history release notes August 16, 2018 (Build 3.5.16548.0) that issue was fixed. See attached. If you’re on that version and it’s still happening you may want to log a support case.
Hey there, Victoria. Is there anyway you can share your .story file with me for a closer look? You can attach it here or use this link. Also, if you can do a little screencast of what you're seeing, that will help me completely understand what to look for. Thanks!
I was contacted by Articulate support and sent it to them through the link they provided. I tried doing a Snag it video of the jump, but it didn't record (even though it jumped).
Apparently, this is still an issue with those who use Firefox. I received this message from Articulate support today:
Hi Victoria,
Upon checking, the bug report associated with this issue is still open. We are very sorry for this inconvenience. Using your project file, I published this to LMS and was able to replicate the issue using the latest version of Firefox. An identified workaround that I've confirmed is to use a different browser when viewing the published course, such as Chrome, Internet Explorer, or Microsoft Edge.
I have linked this support case with the bug report for the issue, and I will be notifying you as soon as possible once the bug has been addressed by our engineering team. Thank you for your understanding and we are very sorry if this has slowed you down in any way.
If the software was free, I'd have to agree with you, but if you are paying thousands of dollars for a software package, having it compatible with the latest versions of the 4 main browsers would be a minimum requirement, in my experience.
I'm experiencing it on both Firefox and Chrome. Chrome less often than Firefox, but it's happening in both places. If you'd like to see the course where it's loaded, we have a free version I can sign you up for - let me know and I'll email you the instructions.
Thanks so much for those details. I'll be sure to share that information with my team. Now that you're subscribed to this thread, you'll be one of the first to know if we get this bug fixed!
17 Replies
Hey Victoria
According to SL3 version history release notes August 16, 2018 (Build 3.5.16548.0) that issue was fixed. See attached. If you’re on that version and it’s still happening you may want to log a support case.
You still on Bribie? We may be neighbours soon 😀
Nope, not fixed. I am running version 5:35.16548.0. It doesn't do it every time, but mostly when the character changes state.
And YES! I'm on Bribie. Where are you moving to, Wendy?
Hey there, Victoria. Is there anyway you can share your .story file with me for a closer look? You can attach it here or use this link. Also, if you can do a little screencast of what you're seeing, that will help me completely understand what to look for. Thanks!
Hi Crystal,
I was contacted by Articulate support and sent it to them through the link they provided. I tried doing a Snag it video of the jump, but it didn't record (even though it jumped).
Gotcha, Victoria! I see Jose is working through it with you, so I'll follow along there.
Apparently, this is still an issue with those who use Firefox. I received this message from Articulate support today:
Hi Victoria,
Upon checking, the bug report associated with this issue is still open. We are very sorry for this inconvenience. Using your project file, I published this to LMS and was able to replicate the issue using the latest version of Firefox. An identified workaround that I've confirmed is to use a different browser when viewing the published course, such as Chrome, Internet Explorer, or Microsoft Edge.
I have linked this support case with the bug report for the issue, and I will be notifying you as soon as possible once the bug has been addressed by our engineering team. Thank you for your understanding and we are very sorry if this has slowed you down in any way.
Wendy - see note below. This issue has not been fixed.
Ah got it - so it's a browser issue. Can you use another browser or is your organisation locked into Firefox?
I can use another browser, but can’t guarantee that all of our employees and customers will use a different browser when they view it.
It’s not MY user experience I’m worried about; it’s my learners’ experience that I am concerned with!
Sure - completely understand.
i would put something at the beginning of the module to say e.g.
This course is best viewed using the latest version of Chrome or IE. Viewing through Firefox may cause unexpected behaviour.
How about Articulate just fix it instead? ;-)
TBH with the amount of updates to the multitude of browsers available to view output I'm amazed the software works as well as it does ;-)
If the software was free, I'd have to agree with you, but if you are paying thousands of dollars for a software package, having it compatible with the latest versions of the 4 main browsers would be a minimum requirement, in my experience.
Hello, I'm having this same issue four months later. Has there been any progress on this bug?
Hello StatEase,
I do not have an update on the issue initially reported here.
Are you experience a similar issue in Storyline 3 within Firefox as well?
I wanted to share some information on how we define bugs and how we tackle them when they occur.
I can confirm that this conversation is attached so that we can share any updates we have to share as well.
I'm experiencing it on both Firefox and Chrome. Chrome less often than Firefox, but it's happening in both places. If you'd like to see the course where it's loaded, we have a free version I can sign you up for - let me know and I'll email you the instructions.
Hi StatEase Admin,
Thanks so much for those details. I'll be sure to share that information with my team. Now that you're subscribed to this thread, you'll be one of the first to know if we get this bug fixed!
This discussion is closed. You can start a new discussion or contact Articulate Support.