Storyline Master Slide object states flickering
A bug seems to have crept into the September 2026 versions of Storyline which has broken how I use objects on the master slide. I often use Rectangles with multiple states for topic titles, which I change with triggers depending on which topic the learner is viewing. In the September 2026 versions of Storyline the Normal state is briefly shown when I move from slide to slide. This never used to be the case. I also noticed that the flicker occurs when the initial state is set to something other than Normal. Even without using triggers, the Normal state is displayed for a few milliseconds. Here is a screenshot of the rectangle set to the initial state of Topic 1, which I would expect to persist seamlessly between slides. Please take a look at these examples. In the first example, the flicker is very noticeable when you move from slide to slide. https://360.articulate.com/review/content/75207938-075a-4cc8-a250-428ce0c1baf2/review?version=1 In this example, adding an image to the Master slide fixes the issue. It's very odd. https://360.articulate.com/review/content/75207938-075a-4cc8-a250-428ce0c1baf2/review Has anyone else noticed this?Problem with automatically generated xAPI statements in Articulate Storyline
Hello Storyline community, I'm experiencing issues when publishing a course for LRS. Unlike in earlier exports, the automatically generated xAPI statements (e.g. "experienced/left slide XY") don't display the slide title anymore but only the slide ID. How do I get displayed slide titles in the xAPI statement again? The attached screenshot shows xAPI statements generated from an earlier export with displayed slide titles as well as statements from the current export with only slide IDs. Thanks in advanceSeekbar Locked After Course Completion Relaunch
I’m trying to confirm whether this is a known Storyline limitation/bug or if there is a supported workaround. On the learner’s first pass through the course, the seekbar should be locked so they cannot scrub ahead. When slide is complete, the seekbar should be unlocked. Once the course has been completed, the learner should be able to relaunch it later and freely scrub through previously viewed content. Current Storyline setup: Player seekbar: Allow drag after completion Slide revisiting: tested Automatically Decide, Resume Saved State, and Reset to Initial State Tracking: Viewed 1 of 1 slides (SCORM Cloud confirms Completed) Resume behavior: Prompt to resume LMS publish: SCORM 2004 Reporting: Completed/Incomplete Tested on Brave, Chrome, Firefox & Edge Test course is only a single slide, so there is very little complexity involved but am getting reports that other courses for different clients on different LMS's are having the same issue. What happens: Launch course in SCORM Cloud. Seekbar is correctly locked during initial playback. Let the slide play through completely. Course reports completion. Seekbar correctly becomes draggable during that same session. Exit the course. Relaunch and choose Resume. Seekbar is locked again. I repeated this with all three slide revisit settings listed above on SCORM Cloud. The result is identical, so slide revisit behavior does not appear to affect the seekbar state. At this point it appears that Storyline correctly changes the conditional seekbar state after completion during the active session, but does not persist that unlocked state across LMS sessions. I’ve found several older forum discussions describing similar behavior, including JavaScript-based workarounds that read the LMS completion status and then alter navigation/player behavior. Before implementing something custom, I’d like to confirm: Is this currently considered expected behavior for Allow drag after completion? Is there a supported Storyline-only method to preserve the unlocked seekbar state after relaunch? If not, is JavaScript still the recommended workaround? Is there any official guidance for handling this across both SCORM 2004 and SCORM 1.2? I’m specifically trying to avoid LMS-specific or vendor-specific hacks because this needs to be a repeatable standard across multiple developers and clients. I can provide a copy of the Story file via PM upon request by an admin. Many thanks, DerekShow Object on second visit/revisit
I simple want a text "page already visited" to appear at the second visit of a layer. But the text does not show up. 2 triggers: First Trigger: I set the status to "Normal" of the "page already visited"-textbox from status "invisible" on timelinestart of the layer IF variable Sites_Profil_ChangePassword is true. Second Trigger: I let the variable Sites_Profil_ChangePassword to switch to "Right" from initial "False" state when the timeline reaches 0,25 seconds of the layer. The textbox is on top of all elements in the layer and always visible. Layer Property is "Reset to initial state". This setup is working in a new file and also within the same file with a new test layer. Any ideas? As I can't create a new SL-file as there are weeks of work in it.Storyline for Marketing Real Estate
Hi, I posted this in the Storyline forum, but someone mentioned I might get a better response here. I was wondering if anyone has heard of Storyline being used to market properties. I would think that its ability to create interactive maps and use video for virtual tours would make it ideal for that purpose. I'm not a real estate agent, but I will be selling my condo next year, so that's what got me thinking. I'd love to see some samples if anyone knows of any, or if you have any suggestions, they'd be most appreciated.Inconsistent AI pronunciation
I have been trying to get the AI voice (specifically Matilda) to consistently pronounce Regina (reg-EYE-nu). While most instances pronounce it correctly, there are a few that still pronounce it as "REE-GEE-nu". I am a relatively new user... Is there any way to get this corrected and consistent?Anyone having this 508 issue with the scrolling panel in Storyline?
I have a scrolling panel that when used with JAWS v2025.2505.43 announces the element as “left right slider” though the slider is used to move content up and down. Additionally, JAWS announces incorrect instructions for how to use the element. Is this a known issue?Trigger not launching email in LMS player
I developed a course that includes a hotspot. The learner is supposed to click on the hotspot which triggers a "send email to" action. The items work in review 360 but do not in the lms player (vi LMS). Any suggestions on how to get the trigger/hotspot to work?
