Problem with the screen recording in Articulate. HELP!
Hi everybody. Ok, there is a big problem which I am facing. 😬 Screen recording I have. Screen recording as simulation was done by me by selecting an 'x' size of screen size, which is never a trouble maker. Now I put that same recording as simulation where slide by slide test mode was selected by me. Now my smart colleague chose to change the screen size to 720x540. I had kept it 960x540 earlier. Now she wants me to simply copy and paste the slide as shown in below screenshots for ref. I 'simply' copy it and by doing ctrl+v I could duplicate the slide.😒 (Note: this is happening for any slide that I try to duplicate). As shown below in the SS, the recording size or ratio gets distorted and goes out of the slide size or canvas. Since its a recording, I get no option to fix this by adjusting the edges of it like how we increase or decrease the picture or image size. It 'simply' doesn't allow me to have a clean duplicate file or slide of the ones created. Therefore, I seek for help from anyone who could do some miracle. Else, I have to redo everything or to think about some something else. Because these things aren't in my control. Watch the SS attached carefully. Thanks. 😇Storyline's 2025 Year In Review
🎉 Wrapping up 2025 with a grateful (and honestly pretty tired) smile. It’s been a big year for Storyline 360, so I wanted to share a few highlights before we close the book. This year was about making Storyline more helpful in very real, practical ways, not just adding shiny features for the sake of it. A few things I’m especially proud of: 🚀 AI started pulling its weight This wasn’t about slapping a chatbot into the product. We focused on tangible wins that save time and reduce friction. Things like high-quality text-to-speech, automatic captions for audio and video, AI-generated alt text, image generation, and even quiz question generation. These are the kinds of tasks that used to slow authors down but should now feel easy or even trivial. We also introduced AI-generated JavaScript entrance animations, which might look like a small feature on the surface, but it’s actually a big deal for the future of AI in Storyline. We reworked how the AI Assistant chat works and laid the foundation for a whole new wave of AI-powered features. In 2026, we’re excited to keep pushing this further, helping you create objects and triggers, sync things on the timeline, and design better, more interactive courses without needing to be a power user on day one. ♿ Accessibility made meaningful progress The new Accessibility Checker, better screen reader support, Set Focus triggers, and captioning improvements were all driven directly by customer feedback. There’s still more to do, but this year delivered real improvements that authors and learners can feel. 🎨 More expressive interactivity and design tools Fluid morph transitions, new emphasis animations, shape merging, and a new JavaScript API opened up a lot of creative space. Courses don’t have to feel static anymore, and we’re seeing authors do some really impressive things with these tools. 🎥 Media just works better now We made some investments in media support this year for cleaner caption workflows, better playback reliability, and fewer weird edge cases. We also snuck in support for WebM, which enables videos with transparent backgrounds and unlocks some really fun design possibilities. A lot of unglamorous work here, but it makes a big difference day to day. 🛠️ A mountain of fixes and polish Hundreds of quality-of-life improvements landed this year. Some tiny, some massive, all aimed at making the authoring experience smoother and more predictable. None of this happens without customers pushing us, questioning us, and telling us when something feels off. That feedback keeps us honest, so please keep it coming. If you’ve used any of these features, I’d genuinely love to hear what’s working for you and what still feels rough. Tell me straight. What helped the most this year, and where did we miss? Here’s to an even better 2026!Morph not working with standard states
Greetings, I want to use the Morph transition with buttons that have both Hover and Visited states, using Storyline's own coded states, but to my surprise, the buttons don't follow along, unless I make custom states that I manually program with triggers. This seems like extra work for something that shouldn't be that jarring. Is there any plan to make the Morph transition work with SL's own states? The transition happens a lot of possibilities, but "not working with standard states" and "not working with layers" really grind my progress to a halt. Thanks in advance.Accessibility Issue: All-Caps Button Text
I am currently developing an accessibility-focused course, so it MUST meet accessibility standards. One issue I’ve identified is the use of all caps on buttons, which is not accessible. I can change this for the "Start Course" button; however, in other components, such as button stacks, the text appears locked in all caps. Is there a way to modify this so the button text uses standard capitalization?Variables used onscreen disappear when browser is resized (high resolution only!)
Hello, I know this sounds like the issue from 2022 titled "Variables used onscreen disappear when browser is resized" but this issue only occurs for me as I have a high-resolution (5120x1440px) monitor and I typically test SL360 courses in a browser utilising the full screen height. In our course, after completing an assessment we display the user's score (perent) and passing score (percent) which use variables. If I run my browser at full screen height and wide enough to accomodate a fully scaled up SL360 slide then I don't see the text fields whereas if I run the window smaller (e.g. full HD) then they do appear. If I enter the side below the threshold the text shows but if I scale up, it disappers and scalling down doesn't restore the text. Entering the slide when the window is above the threshold, the text never appears and again, scaling down the window won't show it. I can see in the HTML that the font size is the issue. SL is scaling font sizes and a billion other things when you resize the window. However, when I scale above the threshold, I can see that the font-size (and line-height) becomes a minute value e.g. font-size:"2.66454e-15px" (about the size of a proton!). I've attached: A minimal SL360 story file that reproduces the problem (large display resolution requried). [Embedded quiz used to generate the variables for the text boxes] Screenshot of the before and after issue Screenshot of the HTML elements showing the font-size (and line-height) going down to epsilon values. The javascript is minimalised so I can't really debug any further, otherwise I would. NOTES: My display resolution is 5120 x 1440 pixels. I am typically testing a SL360 course in a browser window full height and around 1800pixels wide. The issue occurs if I have my brower window full height and I then widen the browser above 1590 pixels. As the scaling of the course is constrained by the browser width at this point the slide is still growing as I resize. At the point of failure the SL360 frame is around 1583+ x 1214 pixels. Thanks, ChrisTable with row headings
I need to be able to create a table in either Storyline or Rise that has both column headings AND row headings, and I need it to be 508 accessible and properly read out both headings along with cell contents. As best I can tell, both products only support column headings. The recommendation is to use an image of a table and then describe it in alt text, which I know my 508 auditor will not accept. Has anyone found a solution to this?storyline 3 user guide
i only need storyline every few months so i can't justify a subscription. i only need to access the storyline 3 user guide once or twice a year. i just tried today and Articulate has nixed all access. such an unjustifiable, unkind action ranks with the best of those by trump. you disgust me, Articulate, and as soon as i send this i will close my account.
