After returning from the result slide, the Correct and Incorrect layers on the questions are hidden
I've run into an issue and would love your help. My course contains many questions that are aggregated in a result slide. The questions are located in different scenes. When I reach the result slide and the Submit results trigger is executed, the “Correct” and “Incorrect” feedback layers on the question slides no longer appear when I go back to them. The slides and layers are set to Resume saved state, but the feedback layers remain hidden after returning from the result slide. Is there any way to work around this limitation? I was thinking of manually forcing the layers to show using variables, but with a large number of questions, it would be quite a bit of work. If anyone has other ideas, I’d really appreciate it!Can't see the base from a layer? Or is it just dimmed? Here's how to control visibility...
There are different ways to control what appears—or disappears—on a slide. It's good to know these options in case you need to troubleshoot a file that isn't displaying as expected. Dim the base while editing a layer The Dim button slightly fades base objects while editing a layer. This can help you focus on the objects on the layer. Dim is selected by default, but you can deselect it so the base appears without fading. Dim only fades the base during editing. It does not impact how the slide will look when previewed or published. Hide the base while editing the layer The visibility of the base can be locked (visible while editing a layer) or unlocked (hidden while editing a layer). This image shows the base unlocked: The default is locked, which reveals an eye icon. If you don't see that icon, just click the designated area to lock the visibility. Like the Dim button, this only affects the base while you're editing layers. It doesn't hide the base when the slide is previewed or published. Hide or dim the entire base during editing and when previewed or published If a layer has a solid fill for the background, that will hide the base completely. A semi-transparent fill will dim the base. How that looks depends on the fill color and transparency setting. The background setting is accessed via DESIGN tab > Background Styles > Format Background. If the base is dimmed when viewing a layer, check the background setting. The layer might have a semi-transparent background. If the base doesn't show at all when viewing a layer, the layer might have a solid background with no transparency. The default background for layers is set via the Feedback Masters. (See Storyline 360: Using Feedback Masters | Articulate - Community ) Warning: A layer's filled background hides the base so the user can't see it. However, it doesn't prevent the user from accessing interactive objects on the base. The Slide Layer Properties could be set to prevent the user from clicking on other layers, including the base. To prevent the user from interacting with other layers and the Player elements, set the layer to present as a Dialog. For more information, see Storyline 360: Working with Layers | Articulate - Community. Another option would be to hide all interactive objects on the base by deselecting their eye icon on the layer's timeline. (That option is described below.) Hide all objects on the base during editing and when previewed or published The Slide Layer Properties let you hide all objects on the base when a user visits a layer in the published course. With this setting, the base will also be hidden when you're editing the layer. Permanent objects (for example, shapes and images) that are on the Slide Master or one of its layouts can't be hidden with this method. Hide only designated objects on the base during editing and when previewed or published You don't have to use triggers to hide certain base objects when viewing a layer. You can set the visibility of each base object by selecting or deselecting the eye icons in the layer's Timeline. For example, the image below shows a deselected eye icon for Button 1 on the base. Thus, that button won't be visible when viewing the layer during editing nor when the course is previewed /published. Note: Permanent objects (for example, shapes and images) that are on the Slide Master or one of its layouts don't appear in the "Base Layer Objects" list. While editing, view only objects that are visible at a given point in the Timeline Here's another function that can hide some objects while you're editing: Timeline Visualization. When Timeline Visualization is turned on, you'll only see the objects that will be visible at the point in the Timeline where the playhead is. This is very handy, because it makes it easier to edit overlapping objects. It can always be scary! If you don't realize it is on, you might wonder why you aren't seeing everything on the slide. This image shows a slide with Timeline Visualization off. You can't see the details in the overlapping shapes at the bottom of the slide. This image shows the same slide with Timeline Visualization on. The playhead is at 4 seconds in the Timeline. Now, you only see the objects that will be visible at that time.Storyline: Motion Menu
This animated menu is a great way to catch your learner's eye and keep them engaged. Check out the gif below for a sneak preview of this Storyline template*. *This template will work for folks using Storyline 360, the continuously updated version of Storyline included in Articulate 360. Want to try it out? Get a free trial of Articulate 360 right here.Is AI Text-to-Speech mp3 encoding during Publishing necessary?
G’day, I have a project that uses AI Text-to-speech .mp3 files. When I Publish the course it is taking 7 minutes to complete, which can be painful when you need to do it a few times in a row (eg. Like if you’ve made a small change and want to re-publish again for testing purposes). In case you're wondering, yes, I use the slide preview feature for most of my testing but there are some parts of my course that are best tested in the browser (especially Lightboxing). From what I’m observing with the progress bar of the publish process, most of the time taken is the encoding of the audio files (6 of the 7 mins). I’d like to know if there is any benefit for me to leave the Storyline-generated AI Text-to-Speech audio files, on each of the Storyline slides, set to “Automatic” (meaning they will be encoded during Publishing) or if I can change them all to “None”? I'm wondering about this, considering that Storyline has created them, so I assume they are compressed and ready to go, as-is, yes?. What are the implications if I were to set all of them to “None”. For example, would the resulting published folder be larger? Is there anything else being done to these AI TTS mp3 files when the publishing process re-encodes them? Many thanks! BrettChanging all Feedback layers
I hope I'm missing something. I have imported 25 test questions into a test bank. Now I want to use different Feedback layers than are in them. All layers are the same, just custom lay I have made. I can change each slide, but I want to change all at once, faster. What am I missing to do this?Small gap between slide content and player
This is something I've noticed in Storyline for a few years now. 9 times out of 10, there is usually a small 1px gap between the edge of my slide content and the player, making it impossible to create seamless content. The small gap also shows some content, but not others. The location of the small gap also seems to be random across the 4 sides. For example, below is a screenshot from one of my latest courses (in both Chrome and Edge). You can see the small gap between all edges of the slide and the player, with the edges more prominent in Chrome. The gap does appear slightly in the Storyline Preview, but is much worse in published content (either to SCORM or Review 360). The slides are 1080x1920. For reference, the below screenshots were all taken on a 4k monitor at 100% page zoom. It appears to be a responsive scaling issue, as the gaps change affect edges depending on the window size, the browsers zoom, etc. To try and mitigate this issue, I extended the edges of the blue rectangle shapes outside of the slide bounds, but those objects get culled so you can see the gap, but some objects that are beneath those objects are still visible. Has anyone else come across this issue (my entire team have), and if so, have you tried anything that has fixed the issue? Making edits to the SCORM package JS or CSS sheets isn't a viable workaround, as it needs to be corrected in the Review 360 versions (for client reviews). Additionally, can anyone at Articulate touch on whether this is a known bug and/or if its on a patch roadmap? Please note: I can't upload the Storyline file due to privacy, however, I can confirm this has happened in almost all of the Storyline modules we produce across multiple versions, browsers, and operating systems. Above: Storyline Preview. Very small gap between the left and right edge of the blue banner at the bottom. Above: Review 360 - Chrome. Very visible gaps along all edges of the slide, where you can also see objects that go outside the edges of the slide. Above: Review 360 - Edge. Barely visible gaps along the blue edges of the slide. Above - Left: Zoomed in screenshot of the bottom of a slide with custom navigation arrows, where you can see the button between the bottom of the blue rectangle and the player. Above - Right: Zoomed in screenshot of the Master slide showing the blue rectangle is extended past the slide bounds completely covering the bottom of the button so its not visible. The blue bar has been moved on the right edge to show where the edge of the slide is, purely for the purpose of the screenshot. Note: Interestingly, when I tried to screenshot the button being visible in the gap, if the browser window lost focus, the button would disappear from the gap.🚀 Storyline 360 hits Update #100! 🎉
Back in November 2016, we launched the very first version of Storyline 360. Fast forward 8.5 years—and today we’re celebrating a big milestone: our 100th update release! To mark the occasion, we’ve rolled out a batch of exciting new features: 🎙️ AI-generated closed captions 🔷 Shape merging tools 🟦 Expanded rounded corner controls But the one I’m most excited about? The brand-new Accessibility Checker. We built it to make meeting WCAG guidelines easier and more actionable for course creators. It scans your course for 24 different types of accessibility issues, flags potential violations, links to the specific WCAG criteria, and explains how to fix each one. 💡 Bonus: 🔨Some issues can be resolved instantly with a “Fix it for me” button. 🤖If you use our AI Assistant, you can even auto-generate missing alt text or captions. We hope this helps you create even more inclusive learning experiences. We're already planning future enhancements—so if you give it a spin, I’d love to hear your thoughts in the comments 👇 🧪 Want early access to upcoming features? Join the Storyline 360 private beta program and help shape what’s next. Just email us at beta@articulate.com to sign up!Multiple Closed Captions and Languages using simple Javascript
I cracked the code! Well, my manager and I did it together so, I can't take full credit but needed to share with my fellow StoryLiners. TL;DR - SL File attached. We added very simple Javascript at the beginning AND you only have to add it once! Very important steps/Instructions are as follows: Inspired by this thread - You have to kill the captions from the video file. You probably have to initially do your captions on the video file to time it with the audio waves. Just export it (for translation) then delete the captions. You then add a blank audio file - the easiest way to do this is just record 1-2 seconds of audio right in SL, edit, cut out the recorded audio and then manually add however amount of silence to match the length of your video. Once you translate the exported captions file, import it to your blank file. In my case, I captioned english first so the first blank file was easy - Just imported the english caption. Import/export for the rest of the languages. IMPORTANT - you must use the same timing. If not, you will see the different languages, with the different timing, peeking behind the CC bar. I will elaborate on that in a sec. When you stack your language files on the timeline, you have to do it in the same order across all slides. The DOM reads the audio file's captions from bottom to top on StoryLines timeline. This also matches the Javascript on the first slide. Ex: If English is the first language (blank) audio file, that will be nth-child(1) in the Javascript. If Spanish is the second language (stacked on top of the english file in the timeline) that will be nth-child(2). Etc... The first block of Javascript is used if the user goes back to that slide and picks a different language - for some reason(?). It "kills" any other instances of Javascript by removing the "children". The reason for the importance of using the exact timing when translating from your original caption file, is that the Javascript is hiding the children that were not selected behind the child that you selected. Its weird, I know. And it does not matter if the length of the caption bubble is different across the languages. Tested in Chrome and firefox. Hope this helps some projects/deadlines! We've all been there and if you haven't, "You will be... you will be" (in the voice of Yoda).Multilingual Toggle Support in Storyline
Hey team, I’ve created a course in Articulate Storyline with English voiceovers, and I’d like to provide users the option to toggle between English and Spanish. For the Spanish version, I’ve used a different AI text-to-speech tool and not the built-in Articulate text-to-speech feature. Is there a recommended way to implement a language toggle that would allow users to switch between English and Spanish—ideally changing both on-screen text and audio based on their selection? Any best practices or guidance on how to set this up using external audio files would be greatly appreciated.
