Forum Discussion
Slides Auto-Advancing in Storyline?
Hello all! I'm having some challenges with Storyline currently when I create a new project. I set my slide advance triggers to happen when the user clicks the NEXT button, but when I preview the project, the slides will auto-advance even though I have deleted the "advance when the timeline ends on this slide" trigger. The only solution I have discovered is to delete the slide entirely and create a new one.
I've noticed this specifically has happened when I import slides from Powerpoint, which I do often due to a lot of my Storyline files having edited screen captures that I edit in Powerpoint.
Is this an issue others have also encountered? Are there other solutions to this challenge I can use? Or is this an issue with Storyline itself? Thank you!
5 Replies
When you import from a PPT, the Slide Properties often come in set to advance Automatically. Just change that to advance By user.
FYI: You can change that setting for multiple slides in STORY VIEW. Simply select the slides, and then change the setting in the Slide Properties panel in the lower right.
My team has also recently experienced some auto-advance triggers and the slide settings changing from user-controlled to auto-advance, and we have never imported from PowerPoint.
I've paid close attention, and it sometimes happens (new triggers for auto advance) when we copy a slide or even just a button that may have a "jump to next" trigger associated with it. I think there's something squirrely going on in the Properties panel and/or triggers.Hi JulieYamamoto! Thanks for letting us know that you're also seeing this behavior in a course where slides weren't imported from PowerPoint. It would be helpful to take a look at your project file so we can test the behavior. Would you mind sharing your .story with us? You can share it privately in a support case.
Thanks for reaching out, Lauren. Upon further investigation, I learned that a team member did initially import some slides from PowerPoint, so that was likely where it started. I have lost track of which version of the project had the odd behavior and we seem to have it all working now. Thanks again for offering support.
