Forum Discussion
simple file won't play even when i reduce it to one slide
I'm creating a visual only template (just picking colors etc at this point) and plopping them into a new plain file that i did not alter other than to add images to it -- like no weird triggers or player changes. i did add a couple of quiz slides i liked just for the visuals, but even when i removed those, the slides just hang. i took out one slide at a time until there was one slide with a single image on it and it still wouldn't play. I tried creating a new file and copy-pasting the stuff on each slide. nope. the only thing that works is if i delete every single slide and add a new single slide with a picture of my cat. the problem appears in all preview and publish modes.
Hm, your file works for me. I previewed and published to Review, all works as expected. I'm using Storyline v3.96.33815.0.
so you could view all of the slides, not just open the file? i just reinstalled the software for the 3rd time in the past 2 weeks because nothing i'm creating is working even though people can't find issues. what else might the problem be? i'm creating a bunch of stuff for our team to use. At this point, Captivate is the better deal. like do i need to reset my hard drive, because that would suck. :( Thanks for checking though.
I just updated my drivers and checked at least 20 other things in my system, from RAM to storage, rebooted, and ran Storyline as an admin and nothing has changed. I'm posting this here for support to view. Here is everything I tried from Chat GPT. I just got this laptop over the summer and I work at a tech company, so this is just really weird...
Step 1: Check Your Storage & RAM
- Open Task Manager (Ctrl + Shift + Esc) → Go to the Performance tab.
- Memory: Check how much RAM is in use. If you're consistently over 80%, that could be an issue.
- Disk Usage: If your disk is often at 100%, that can slow things down.
Step 2: Check Where Your Files Are Saved
- Are your Storyline files stored in:
- OneDrive, Google Drive, Dropbox, or SharePoint?
- Try moving them to C:\Users\YourName\Documents\Storyline Projects\ and see if that helps.
- A very long file path?
- Shorten it (e.g., C:\Storyline\project.story).
- OneDrive, Google Drive, Dropbox, or SharePoint?
Step 3: Check for Conflicting Software
- Open Task Manager → Look at running applications.
- Are any of these running?
- Cloud sync apps (OneDrive, Dropbox, etc.)
- Screen recording software (OBS, Loom, Teams)
- Antivirus software (McAfee, Bitdefender)
- NVIDIA Overlay (GeForce Experience)
Try closing them and see if Storyline improves.
Step 4: Check for Graphics & Windows Updates
- Update Your Graphics Driver:
- Right-click Start → Device Manager → Expand Display Adapters.
- Note the name of your graphics card (NVIDIA, AMD, or Intel).
- Go to the manufacturer’s website and download the latest driver.
- Check Windows Updates:
- Settings (Win + I) → Update & Security → Check for updates.
Step 5: Try Running Storyline as Admin
- Right-click the Storyline icon → Run as Administrator.
Step 6: Check for Corrupt Installation
- Have you tried completely uninstalling Storyline and manually deleting leftover files in:
- C:\Users\YourName\AppData\Roaming\Articulate
- C:\Users\YourName\AppData\Local\Articulate
- Then reinstalling?
Try these steps and let me know what you find! If you need more advanced help, I can guide you through generating a system report for deeper diagnostics.
- Open Task Manager (Ctrl + Shift + Esc) → Go to the Performance tab.
I was also able to open your project and preview all the slides. The only difference was that I didn't have the Oracle fonts installed on my computer. Try replacing these fonts to see if the issue persists when they are not in use. It's worth giving it a shot.
Hi KristinFiore-3a!
Sorry to hear this Storyline file has been giving you so much trouble!
Glad to see the community has been helping. I noticed you've also opened a support case. Smart move! It looks like my teammate Darwin is handling your case, and just replied to your e-mail sharing additional troubleshooting steps. Let's continue the conversation there to keep all information in one spot.
