Forum Discussion
Behind the Scenes: Storyline’s Move to Modern .NET
Hello everyone,
Happy to share that we've just released a new update for Articulate Localization!
In our latest update (June 9, 2026), we've included a fix for:
- After publishing a multi-language project to an LMS, text-to-speech audio in the source language was out of sync.
You'll need to be working with the latest version of Storyline 360 (Update 119) to take advantage of this fix. Launch the Articulate 360 desktop app on your computer, and click the Update button next to Storyline 360. You’ll find our step-by-step instructions here.
Please let me know if you need additional help.
This support article (Storyline 360: How to Correct Unexpected or Erratic Behavior) states that if you're having issues with storyline erratic behavior to go in and make sure you're set to framework 4.8. Is this no longer the recommendation? I've been having some publish issues with multi-language files (publishing messes up the timelines). Could this different .NET thing be affecting it? I noticed the error some time in the last couple of months. It's still present on the 5/12/2026 release.
Just checked and my windows version is up to date.
How/what should I change my .NET thing to? Here's my current settings:
Hi lorraineS,
Sorry to hear that you've been struggling with publishing a Localized Storyline file.
I see that you've also been working with my teammate Genelyn through a support case. As she shared, the Timeline behavior you're seeing is being caused by a Storyline Localization bug. It is not directly related to Windows .NET Framework settings.
This bug causes:
- Source language Text-to-Speech audio Timeline placement changes, after publishing a multi-language course to LMS.
We've included your voice in the bug report that's being tracked, so we can notify you as soon as a fix is ready.
Thank you for your patience. I'm sorry if this has been slowing you down!
