Storyline 360 - Animate In By Paragraph Missing Words and Lines
Aug 06, 2021
Pinned Reply
Hi everyone!
I'm happy to share that we just released Storyline 360 (Build 3.70.29211.0)! In this update, we've released the fix for the bug where text boxes that animate by paragraph might not load consistently.
Now all you need to do is update Storyline 360 in your Articulate 360 desktop app! If you run into any issues, please reach out to us by submitting a support case!
74 Replies
Hi Alistair,
Thanks for reaching out and sharing a video of what you're experiencing! I was unable to replicate the issue on a sample file, but let's double-check a few items:
If all is good on those items, I'd like to have our support team review one of your .story files and help troubleshoot. Feel free to share it with us here.
Hi Ren,
I am on the latest version of Storyline and I am working from a OneDrive folder which auto-syncs to our cloud, but its on my PC as a local file.
Hello Alistair,
Thank you for the additional information.
The sync process temporarily locks the file. While you're working on your Storyline file, it's being locked by OneDrive every time there is a modification, which is what causes the erratic issues Ren mentioned above.
The two options to get around this are:
If you'd prefer to work with one of our support engineers, you can reach them directly here.
Hi everyone. I thought I'd update you on this issue. I have begun copying the files from OneDrive directly to my desktop, however the problem is still happening.
It's happening to the Scorm package as well as when I publish it to Review 360.
Hi, Alistair.
Thank you for the update, and I'm sorry to hear using local files didn't fix the issue!
I went ahead and opened a support case on your behalf. You should hear from our team soon via e-mail.
Is there any progress on this issue? Searching through the forums it is not an isolated issue, but each response from support is the same and ends up in a ticket.
Are there any suggestions beyond the copy and paste set of suggestions that clearly don't fix the issue?
Here's another article with the same issue from two years ago.
https://community.articulate.com/discussions/articulate-storyline/problem-with-animation-by-paragraph
Hi Malcolm!
Thanks for reaching out, and I'm sorry you're hitting a similar issue. I searched through Alistair's case notes, and I don't have an update to share, as we didn't receive confirmation that their issue was resolved.
Connecting with a support engineer is the best route since there isn't a standard resolution, and it may be specific to the project. I'd encourage you to share your file with our team to work with you directly to find what is causing this for you. We'll reach out soon after reviewing your file!
Unfortunately, support's suggestion was to remove all custom fonts from my PC and the story files, which was not possible as the fonts are needed for clients branding. It's still happening.
Thanks for the additional information, Alistair. I've shared this information with your support engineer so that you can continue working together.
I had the same problem and thought I fixed it but when I updated to the new April 20 version, animate by paragraph is acting up again.
Certain words disappear within one textbox. Certain lines disappear if animating multiple paragraphs. The support engineer did not have the issue with my source files but I continually do.
Very frustrating!
Hello Thuc-Nhu Vu, and welcome to the E-Learning Heroes community!
I apologize for the issues you are experiencing. I see you worked on a case with our support engineer Dexter.
Here's an article on how to fix erratic behavior on your computer.
If that doesn't resolve your issue, you may need to remove the Articulate 360 files from your computer and install them again. If you need the steps again on how to do that, feel free to respond to the email you received from support.
Please let me know if you need additional assistance!
I have done the steps several times. I have also reverted back to the update where you said that you fixed the bug.
I believe the bug is in the animate by paragraphs where the program does not recognize the character spacing (space or a carriage return) that means paragraph versus blank line verses space. If I make it animate in as a whole object. There seems to be no problems. It just meant that I had to spend several hours remaking text boxes and redoing the animation and timing for each text box.
Thuc Vu
We are having this same issue in many of our projects. Splitting up every paragraph into their own text boxes in every scene of every course we have in progress is going to be a nightmare. Not to mention having to move every text box below if we add or remove any text.
Hi Gary! I apologize for the issues you are experiencing.
Connecting with one of our Support Engineers by opening a case would be best so we can take a look at your project. We will delete the file from our servers when troubleshooting is complete.
Any updates related to this issue. We have struggled with the similar issue more than a year now.
Hello Kimmo,
I've reviewed Alistair's case, and it looks like one of the identified causes of the issue is certain fonts that were installed on their machine. If your course is using custom fonts, are you able to replicate the behavior if you switch your course's font to Arial or any of Storyline 360's built-in fonts?
If using Arial doesn't fix the issue, would you be willing to share a copy of your Storyline 360 project file with me so I can take a closer look at what's happening? You can upload it here, or in private through a support case for testing.
Just to let you know Joe, I have tried using Arial and it doesn't fix the issue. I do not need to review the project again.
The issue is still in effect so I've just trained myself to use separate text boxes when I need to animate in paragraphs.
Just letting you know, I have experienced this issue on machines without any custom fonts installed, across multiple different projects, many of which do not share any fonts and some which use only system fonts.
Hello Joe,
we have also tried using Arial and the issue is the same. Last thing we did was uninstalling and re-installing SL according to this instruction (https://articulate.com/support/article/Articulate-Storyline-360-How-to-Fix-Unexpected-or-Erratic-Behavior). But the problem still persist.
My colleague has already opened a support case around this issue (Case #03230580). But all the discussions I have red so far says that Articulate is not able to replicate the issue on yourside, but it is obvious that many of your clients are struggling with it. I hope that you at Articulate take this issue seriously, as it is not possible that in each case the problem is on client side.
Implementing separate boxes is really not a solution us and I don't need any workarounds. I just want to understand what causes this problem and how we can prevent it happening again.
Many thanks in advance!
I've seen this issue too and while it isn't ideal to have to do so, removing the 'animated by paragraph' instruction and reapplying it seems to clear the bug for me.
HI, you mean that removing the "animated by paragraph" from the menu and reapplying it do the thing? If so, this is one more workaround, which does not exactly solve the core problem. Thanks anyway!
That's what I meant yes.
I agree, it's a workaround, but sometimes these workarounds are life savers when we're working to a deadline.
Yes, that's how it goes and I appreciate this tip! Would still be nice to understand how we could prevent this issue beforehand.
Thanks!
That's good to know. Easiest workaround I've found is to open up the dropdown of the text in the timeline, and move each paragraph's timeline object back and forward. This seems to force Articulate to re-render the text animation.
It's extremely frustrating and time consuming to do this every time I publish a course, especially if its to SCORM and I have to watch the entire module to make sure the text hasn't messed up.
It's been happening for the better part of a year now, and it's costing me A LOT of time to fix each time.
I agree that workarounds are great in a pinch! This workaround doesn't always work for me in the last project. I haven't tried it with a different project.