Storyline issue – Layer not persisting during review since recent updates
Hello everyone, I’m encountering an issue in Storyline that seems to have appeared after the most recent updates. Context: I’m using a question slide with: one Correct layer one Incorrect layer I added a third layer called “Lock”, designed to hide the Next button. Main slide: Standard question slide Next button visible after answering Correct / Incorrect layers: Display feedback Next button available to proceed Triggers in Correct / Incorrect layers: Lock layer: Hides the Next button Trigger logic: The “Lock” layer is triggered when the learner clicks the “Next” button Its purpose is to prevent navigation when the slide is revisited This is mainly used during review mode via a lightbox (recap) Expected behavior: When the learner revisits the slide in lightbox/review mode, the “Lock” layer should remain active, ensuring that the Next button stays hidden. Current behavior: The “Lock” layer does not persist upon revisit The slide returns to its base state with the feedback The Next button becomes visible and clickable again This breaks the intended restriction logic during recap Additional info: This setup worked correctly prior to the recent updates Question: Has anyone experienced similar behavior with layer persistence or slide state reset in lightbox/review mode? Could this be linked to a recent change in how Storyline handles layer states or slide revisits? Thanks in advance for your help!Embed Youtube Video - Error 153
Hello, Has something changed in Storyline?! I'm trying to embed a YouTube video using "iframe". I'm copying the embed code from YouTube, but it says 'Watch video on Youtube - Erro 153...'. I used: <iframe width="560" height="315" src="https://www.youtube.com/embed/dqaN76shzJE?si=F_NwSZruLu5BJAU6" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe> Any/all help would be appreciated. ThanksAI Assistant & Localization in Rise- WONDERFUL!!!
I have created two courses using AI Assistant and Localization, and I am over the moon excited! The process was so very time-consuming, and the translation, per my language expert checker, was spot on! I’m a department of one supporting multiple car rental brands in 28 countries. Hooray for Localization! At least for the Spanish translation. Working on my third course now, using AI Assistant and Localization. I could never have produced three interactive courses in two different languages before these new enhancements in Articulate 360, in under two weeks. Never, never, never! Thank you, Articulate 360 team, not just for the two enhancements, but for making them very easy to use. You certainly kept it simple, streamlined, and focused on your user audience’s needs. AI Assistant is not an ordinary AI Assistant. It is a Trainer’s AI Assistant! Okay, Luminaries, you have another Articulate 360 cheerleader! (smile)🤩 Pat The TrainerChanging Color of Flash Screen Before Lesson
Hi everyone! How do you change the color of the screen that flashes before the lesson loads on the screen when you either review it in 360 or when it loads in an LMS? I changed the player screens to match the new colors my client wants but can't seem to figure out why. In the attached example, you can see when I click on it, it flashes a dark blue color then goes to the black background from the player. It does this when it is loaded into an LMS as well. Ty!My Storyline is taking forever to open. Is there a fix?
This started for me a few weeks ago after I did an update. Usually, my Storyline would take about a minute or so to open and be fully ready to use. But now it takes upwards of 5-10 minutes before it's ready, which is quite frustrating when I have work to do. It is currently fully updated. When I open it, I get the screen below (which looks different from how it used to look) and it just stays like that for the longest time. Not sure what the issue is or how to fix it. Appreciate any advice, thanks.Issue with questions being linked to the wrong result slide
Hello everyone, I am currently working on an assessment structure in Articulate and encountering an issue with how my result pages are organized. I have several evaluation components (e.g., 5.1 Comp_COM, 5.2 Comp_COS, 5.3 Comp_LTE, 5.4 Comp_GES, 5.5 Comp_SOI, etc.), each intended to be associated with a specific score category. However, when I edit the questions (even before publishing the module), some evaluations seem to be automatically reassigned to the global score (6.1 Score_Global) instead of remaining linked to their respective sections (e.g., 5.4 or 5.5). As a result, I have to manually check each question to ensure everything is still correctly assigned. I would like to understand: How to control or lock the association between questions / result slides and their corresponding score variables Why some evaluations automatically switch to the wrong result slides Whether there is a recommended method to ensure a stable and consistent structure across multiple result slides Thank you in advance for your support !! 😀Seekbar functionality issues on slides with "Resume to Saved State" layers
Hi everyone, I’ve run into an issue with the seekbar behavior. I have a slide where the layers are set to Resume to Saved State. When I revisit the slide after moving forward in the project, the seekbar doesn't track correctly. If I try to move the seekbar, it seems to control the base layer objects instead of the content on the current layer. Has anyone encountered this "overlap" issue before? I’ve attached a .story file to show what’s happening. Please review the attached file regarding the tabbing and question screens. On the question screen, the layers are failing to maintain their 'visited' state upon revisiting the slide; instead, it only displays the base layer. I would appreciate your help in ensuring the previously viewed layers remain visible when returning to this screen. Please let me know the best way to fix this glitch so that the seekbar accurately controls the active layer when the slide is revisited.
