Storyline 360 - Animate In By Paragraph Missing Words and Lines

Aug 06, 2021

I'm encountering a super frustrating bug in Storyline 360. 

Whenever I use the Animate In By Paragraph option, there is a chance that it will either;

  1. Completely skips lines in the paragraph,
  2. Completely skip an entire paragraph, or,
  3. Delay the paragraph from appearing, throwing off all timings for the rest of the slide.

I've found a "fix" where I just move the paragraph back and forth in the timeline, and it seems to fix it, but then it also appears that they just decide to break on their own. So I fix the issue, it previews correctly, I move on to other slides to fix the issue, and it just breaks again, but sometimes it doesn't break, but one that previously worked fine, now no longer works. Then, when I publish the module to Review 360 or to a SCORM, I find that they are broken again. 

I've attached a video to further demonstrate the issue. 

I've tried updating SL, rewriting the paragraphs, and even just starting again, but I have had this happen in 3 separate storyline files on multiple machines now. 

Any assistance would be great, as this bug is making the review process of making modules extremely tedious and makes SL nearly unusable. 

Pinned Reply
Lauren Connelly
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
Jürgen Schoenemeyer

I have an interesting aspect of this error in the 'animated by paragraph'. It depends on when and how you publish the function.

here is a screen capturing of a minimal example (3 text blocks with animated by paragraph)

https://360.articulate.com/review/content/d6c8b36a-23c1-465a-80c5-d92bb588a9ca/review

page 1:
-> block in the middle is the problem
-> error: line 4 delayed and line 5 missing complete

4 passes at the recording
(1) start storyline file -> publish to web -> error -> close storyline
(2) start storyline file -> open slide view -> close slide view -> publish to web -> no error -> close storyline
(3) start storyline file -> mark the slide (not open it) -> publish to web -> no error -> close storyline
(4) start storyline file -> publish to web -> error -> close storyline

page 2:
 -> only animation errors - no missing text

the cause of the error in my example is the use of user defined text styles

Jürgen

Tonya Stewart

We are still experiencing this with the latest SL360 update. Our workaround was to select all text, change font (we went from Open Sans to something custom [72]), then change font again back to original (Open Sans). That was it. Did that to all of our slides and republished. They were working as expected afterward.

Kimmo Oksanen

Hi, and thanks for sharing your experiences. Perhaps this issue is somehow related to user defined text styles. This feature was published in SL on July 2020 and this could match the time when we encountered this issue for the first time. 

If this is the case, which is the best way to fix issue in already implemented courses? Is there any other way than resetting text styles text box by text box and the manually setting correct styles? 

Jürgen Schoenemeyer

Hi,
I have the problem with 'user defined text styles' AND normal 'text styles'.

I don't think you can really solve the problem efficiently with corrections to the storyline file
- you would have to recreate all style sheets (without using text styles)
- assign them (this deletes the text styles)
- reformat all texts manually
- reassign all animations

here Articulate has to solve the initialization problem with the publish function, this would solve the problems of all previous trainings with 'animate py paragraph' and 'tables' (wrong text formating).

I have an open ticket and will get back to you if there is any news.

Jürgen

Reilly Morgan

So is there a solution in the works for this? Having to tweak one slide only to have the issue appear in an another slide destroys workflow and eats up time. 

Articulate can not be relied on in a professional environment. Especially if bugs like this occur and have been asked about for many months. I find a lot, if not most of our studio time is battling Articulate bugs rather than getting out projects to clients.

This animated text issue needs an urgent solution, not temperamental workarounds.

Alistair Arkwright

I've removed all the custom text styles from a project, and only had modified built-in text styles, but the issue is still occurring. It's now being joined by some titles being published using the wrong font as well.

I can also confirm that the following work arounds do not work for me:

  1. Removing user defined text styles
  2. Adjusting the timing on the animation
  3. Moving the entire text block in the timeline back and forth. 
  4. Saving, closing, and reopening the project. 

So far, the ONLY fix that I have seen work is moving each paragraph's timeline timings back and forth, which is a HUGELY time consuming process.

Furthermore, my team and I are losing HOURS of project time publishing and watching modules, which is fine when they're on Review, but when we've published to a SCORM that has a disabled seekbar and menu, it can take HOURS depending on the length of the module, and if we find ONE text animation glitch towards the end of the review, we have to start the entire process all over again.

Articulate, you really need to get this sorted QUICKLY. We are spending thousands (and even more now the prices have increased) for a software suite that has halved our efficiency to the point where we are considering other module authoring tools to replace Articulate. 

Jürgen Schoenemeyer

it would probably be a great simplification for you if the test via Review 360 would already show the problems.

Take a training where SCORM showed problems and export the (original unfixed) version of the training to Review 360.

publish with this particular flow:
- Close storyline completely
- then open the storyline project
- immediately publish to Review 360 (no other click before publish)

If also now the error occurs on Review 360 then it is the same error behavior as mine, if not it is another problem.

Jürgen

Alistair Arkwright
Jürgen Schoenemeyer

it would probably be a great simplification for you if the test via Review 360 would already show the problems.

Take a training where SCORM showed problems and export the (original unfixed) version of the training to Review 360.

publish with this particular flow:
- Close storyline completely
- then open the storyline project
- immediately publish to Review 360 (no other click before publish)

If also now the error occurs on Review 360 then it is the same error behavior as mine, if not it is another problem.

Jürgen

Hi Jurgen,

The problems do appear in Review 360, however, if you make any adjustment to the content (including saving and reopening the project), it re-initialises the text renderer and the issue re-occurs. It's never the same line of text or the same slide. 

Even if I completely close Storyline, reopen the project, and immediately publish it to Review 360, the glitch can (and most likely will) still reappear randomly throughout the project. 

Luciana Piazza

Hello Barbara, 

Thanks so much for sharing this with us. Sorry to hear you are experiencing this difficulty with your projects.

We do not have any updates at this time but you can see what our Support Engineers are currently working on in our Feature Roadmap. We'll be sure to update this thread with any updates we are able to share!

If you have any specific questions or would like to have us take a closer look at your project, please reach out to us in a private support case.

Have a nice weekend! 

Kimmo Oksanen

This is exactly as my thoughts! No single solution, but anything you do for the text box might or might not solve the problem temporary. Testing after any change and phase is just too time consuming and this issue is really making us work difficult. In projects where there is only one language version, we could even think putting each text on its own box, but this does not work when you working with close to twenty language versions.

I have almost give up the hope for getting this fixed by the service provider!

Alistair Arkwright

I recently had to make a 90 minute module with both standard and accessible versions, and this bug made the review process nearly impossible. I'm currently trying to publish a simple linear course, and the bug is just appearing left, right, and centre. 

The worst part is when I'm publishing to SCORM and lock the seekbar, I have to watch the entire module and just hope that it doesn't happen. And if it does, I have to re-publish it and watch the ENTIRE module again just to see if its fixed, or if any other text bugs have appeared. And I've not found a way to unlock the seekbar from read only when it's already been published to SCORM so that I can quickly review it.

I don't really want to have to watch the same module over and over again when I know that it has been reviewed and I simply just need to publish it. 

It's been over a year and not a single worthwhile peep from Articulate has been offered. Articulate, please stop adding new features, and actually iron out all the issues with the features that already exist. The more you add, the harder it will be to fix. My company is actively looking for another software to use for e-Learning authoring, because this bug has been present for over a year and nothing has been done to fix it. I'm losing hours upon hours of time and money on each project all because of a glitch in the software that I have no control over.

Storyline 360 is completely unusable at this point.

Jürgen Schoenemeyer

there is a known documented confirmed bug with "animate by paragraph" in combination with "text styles"

if you open the story file and immediately publish -> animate by paragraph is broken on many lines (and text formating in tables also)

workaround: open .story file, then click or double click one lide (perhaps on multiple slides ???), then publish -> animate by paragraph (and text in tables) is working

cause is an incomplete initialization at the start of storyline !

Jürgen Schoenemeyer

yes, there seems more than one problem with "animate by paragraph"

but fixing bug by bug should be done - but articulate will not or cannot fix the error

I'm starting to think articulate has no developer capacity planned for bug fixed

actually even more problematic is the lack of the 64 bit version

Update: and the reaction of articulate to the Firefox "not starting, if audio is used" error is is very disappointing. No fix for existing courses - although it would be possible !!!

 

Think Big1

I'll add to this thread by mentioning that I'm encountering the same issues (disappearing text, etc.) plus one more: In the Timeline, the paragraphs are lined up with the audio appropriately but several paragraphs will appear together, even when they are clearly separate elements. I have to hide particulars of the project with blurring, but I've marked up a graphic to illustrate. The first paragraph enters alone, then the 2nd and 3rd paragraph enter simultaneously, even though it's clear in the Timeline that they should appear separately. 

I'm using Calibri as my font and there are no weird fonts installed. This is an issue that's becoming more and more common and will be a disaster if I have to separate my paragraphs into separate text boxes (which is so far the only thing that fixes it). This is obviously a bug, please please please fix it.

Think Big1

I think I've made a slight discovery. The "disappearing text" seems to happen when line spacing is set to multiple, for example, 1.1 lines. Setting it to "Single" fixes it. Or, you can incorporate the line spacing into a new text style and then apply the style, and that works, too. (in other words, applying line spacing with formatting breaks it, applying it with a style doesn't.) It also seems to fix the issue of animated paragraphs appearing at different times than they're scheduled to appear according to the Timeline.

Hope this can help solve some folks' problems with this.

- Karin Carlson

Stacey Clark

Replying to: "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."

I've been doing this and it does not work. It will later break upon publishing and even if it does work, then a new slide will break.

Stacey Clark

Replying to: "I'll add to this thread by mentioning that I'm encountering the same issues (disappearing text, etc.) plus one more: In the Timeline, the paragraphs are lined up with the audio appropriately but several paragraphs will appear together, even when they are clearly separate elements. I have to hide particulars of the project with blurring, but I've marked up a graphic to illustrate. The first paragraph enters alone, then the 2nd and 3rd paragraph enter simultaneously, even though it's clear in the Timeline that they should appear separately. 

I'm using Calibri as my font and there are no weird fonts installed. This is an issue that's becoming more and more common and will be a disaster if I have to separate my paragraphs into separate text boxes (which is so far the only thing that fixes it). This is obviously a bug, please please please fix it."

 

I'm encountering the same issues.