Layers Overlapping in Storyline360
On one of my courses, the base layer slide has 14 buttons, each which opens an associated layer. A few of those layers link to other layers with additional information. This has worked since the course was developed in 2023. When I reviewed it today, not so much. When I click each of the 14 buttons (without clicking links to sub-layers), it works fine. Each layer appears as it should. However, when I click a button on one of the sub-layers to direct it back to the base layer, the layers start stacking, as in the attached screen capture. This occurs on slides 1.1 and 1.2, buttons 2 (Trace to Risk Record) & 10 (Mitigated Probability of Occurrence). All layers have the "Hide other slide layers" box checked. Before I change my layout and make each layer its own slide, I'm hoping there's a quicker fix.Think About It!! Quiz, with Quiz Builder
💡My take on the challenge: I looked at this from a slightly different perspective. Building a quiz is easy! so I wanted to create something useful for the entire community. I didn't just create a quiz, I built an app right inside Rise that allows users to craft, preview, and export their own high-impact, standalone quiz right inside Rise for use in their own courses. Everything in the quiz is customisable! Use it along with the native rise style and format block controls to create something amazing! 🖥️ The tech bit! The tool is a dynamic, client-side web application built using standard web technologies (HTML5, CSS3, and Vanilla JavaScript). It allows you to build, configure, and export self-contained, interactive quiz blocks engineered specifically for iframe integration within Rise. ⚙️The really techy bit! The system relies on a centralized State Management Pattern (const S). Every interaction, from a slider adjustment to an input keypress or color hex alteration, fires a non-blocking UI update sequence: Mutates the values directly inside the global state object. Formats strings safely using contextual HTML/JS escaping helpers (esc() / escJs()) to prevent injection or rendering errors in the exported markup. Automatically serialises the state to compile a completely isolated, valid HTML document inside a data URI stream (srcdoc). 😤Problems encountered! Because the live preview runs inside an iframe wrapper to preserve strict CSS sandboxing and style isolation, standard DOM access is blocked. To solve this, a robust cross-document messaging pipeline was implemented: The Frame: Houses an active ResizeObserver API loop monitoring its own document height. The Message: The child window securely transmits payload data (window.parent.postMessage({type:'frameHeight', ...})) upward to the host application window upon asset load. The Host: Automatically catches the event listener and dynamically resizes the frame height down to the exact pixel, eliminating double scrollbars and layout shifting entirely. 🔎LMS/Rise Compatibility & Performance The exported codebase is mathematically pure Vanilla JavaScript (ES5 standard for runtime compatibility). It relies on no external dependencies, CDNs, or UI libraries, ensuring lightning-fast load times. It also features a programmatic native browser hook that fires standard completion messages ({type: 'complete'}) across to the parent window automatically upon a user hitting the customisable passing threshold. I hope you enjoy it 😊 Think About It!! Quiz With Quiz BuilderMaking a Storyline so users can click on it as a desktop icon and open from there?
I apologize if this has been posted before but I couldnt find conclusive results. My boss is requesting us to use storyline to create a "tool" format that they can click on from their desktop (like an icon) and it open from there rather than an LMS. I have only ever done Review, LMS, or a Weblink before so I was unsure if this is possible? Thank you so much for your review on this!Issue with syncing in scenario scenes
I have got the scenario as a way to check knowledge using a small case study. I have two response options per scene - one is a correct answer, and the other is incorrect. For some reason, when I type the answer, it is syncing with the next scene's response options. If I change one or the other, it syncs back and forth with the wording. eg. first scene responses says: You do X. Feedback: Correct. X is correct because of ABC You do Y. Feedback. Incorrect Y is incorrect because of MNO. Second scene response says: You do X. Feedback: Correct. X is correct because of ABC I change second scene response to say: You do W. Feedback: Incorrect. W is incorrect because of PQR. I check back and First scene response first response is now saying: You do W. Feedback: Incorrect. W is incorrect because of PQR. I change it back to the accurate one and it changes the second scene back again. How do I fix this?Pause, Confirm, Continue: A Confirmation Prompt Demo
For my demo, I explored how confirmation prompts can do more than just validate an action. Throughout the course, learners encounter simple prompts that encourage them to pause and confirm before moving forward—whether it's understanding the course navigation, acknowledging key concepts, or preparing for a quiz. I often use these types of prompts in my eLearning projects, especially for navigation. They help learners feel more in control of their experience while ensuring they don't miss important information. Sometimes, a simple "Are you sure?" can improve engagement and create a smoother learning journey. Demo: https://www.sarkgcreation.com/elc555c/AI Assistant Can No Longer Upscale Images?
Hi there, I'm working on a Storyline project that includes a screen recording that, unfortunately, resulted in blurry images. I was using the AI Assistant last week to upscale the images and was very impressed by the quality of the upscaled images. However, this morning, the AI Assistant is stating that it is unable to upscale images at all (doesn't appear to be related to last week's partial outage - it is claiming it has never had the functionality at all). Was this capability removed over the weekend as part of the outage fix, or could it be an isolated issue? I've included a screenshot of one of last week's input/outputs, and one of today's. I appreciate any assistance!AI‑powered, real‑time role‑play platforms
Hello Heroes! Has anyone cracked this yet? I’m exploring AI‑powered, real‑time role‑play platforms that can be embedded directly into an Articulate Rise Multimedia Embed block and run within the Rise frame—without sending learners outside the course or requiring a separate login. I’ve tested a few options, including Yoodli, but that experience redirects learners out of Rise. Other platforms I’ve reviewed are either cost‑prohibitive or not transparent with pricing. Has anyone successfully integrated a truly seamless, experiential role‑play experience into Rise? I’d love to hear what you’ve tried, what’s come close, or where you hit barriers. Thank you!Behind the Scenes: Storyline’s Move to Modern .NET
We just wrapped a project that’s been hanging over Storyline for a long time: Moving from .NET Framework 4.8 to modern .NET (now .NET 10). This one goes deeper than it might sound. Back when Storyline was first built, choosing .NET Framework was the obvious call. This was 2010-ish. Windows dominated our space, and the .NET ecosystem gave us a lot of what we needed to move fast and build a really capable tool. That decision worked. For a long time. It also shaped some of the realities of the product today. Questions about platform support come up a lot, and early architectural choices like this are a big part of that story. They helped us move fast early on, but they also made certain paths more complex later. Fast forward to now… Microsoft has effectively stopped evolving .NET Framework and put their energy into modern .NET. Meanwhile, we were still running on a foundation that wasn’t keeping pace with where things were going. So we made the call to move. This wasn’t a simple upgrade. We relied on parts of .NET Framework that don’t exist anymore. AppDomains. Binary serialization. A handful of “seemed like a great idea at the time” features that modern .NET intentionally left behind. We had to rethink and rebuild some pretty fundamental parts of the product. So what did all of this actually get us? We’re now on a modern, actively supported runtime. It’s easier for us to keep improving performance, adopt new capabilities, and evolve the platform without constantly working around legacy constraints. We also retired some very old pieces of the system along the way, which… felt pretty great 😅 And then there's performance. Microsoft has invested heavily at performance improvements in modern .NET, and we're seeing that surface in Storyline. We ran benchmarks across 18 Storyline projects, measuring open, save, and publish times. Every single project got faster with improvements ranging from 0.4% to nearly 30%. The larger the project, the larger the improvement. In the animated gif below, I put .NET Framework (left) head-to-head with modern .NET publishing the same course. Neither project was pre-published to warm the cache, and I even gave .NET Framework a slight head start by clicking Publish there first. The gif is sped up for easier viewing, but the result is real: modern .NET finishes publishing well before .NET Framework. Big credit to the team that pulled this off. This was deep, risky work in some of the most critical parts of the product. Curious to hear from folks here: If you're on the latest Storyline 360, have you noticed any performance improvements when opening, saving, or publishing your projects?
