Forum Discussion
Storyline 360 - Animate In By Paragraph Missing Words and Lines
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;
Completely skips lines in the paragraph,
...
- 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!
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:
- Removing user defined text styles
- Adjusting the timing on the animation
- Moving the entire text block in the timeline back and forth.
- 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.
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!
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.
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 !
