Forum Discussion
How to troubleshoot the difference between ALL SCENES, and ENTIRE PROJECT.
Equipment/Software:
- Storyline360 v3.87.32265.0
- Dell Precision 7560, Windows 11 Enterprise 23H2
- My *.story files are on OneDrive, but ALL of my major projects are, with no problems.
I have a Storyline 360 project with 7 Scenes in it
Scene 1 contains intro and exit, surrounding a main menu.
The main menu has buttons to branch off to each of the 6 topic scenes.
Once all scenes are completed, the learner can continue to the exit in scene 1.
There are no extraneous or unused scenes in the project.
The menu in the player has been properly trimmed to only look at the active scenes.
I am able to Preview any one scene, and any combination of Main scene (1) and any other scene.
I can use the menu to navigate to the secondary scene and back again.
it all seems to work fine individually, and in groups of scenes.
And, when I select ALL the Scenes and preview it works fine.
However, when I try to publish or preview the Entire Project it goes through all the steps, I even get a Publish Successful screen.
When it attempts to load the course in Review360 and just sits with a black screen and three dots loading. And that is what it does with Preview Entire Project, without involving Review360.
That is all it does. 3 dots marching.
I have an earlier build of the course that was published to Review360 successfully, so the course was working yesterday.
then with some additions and changes this condition developed. I do not see any problems with the individual changes I made.
I have rebooted, restarted everything, and the condition persists. Other projects are working fine.
The Diagnostics panel/logs is clear, no message.
I am not sure how to approach troubleshooting this since all the individual pieces work fine. I don't know what the net difference is between selecting ALL the scenes, and just picking Entire Project.
It sounds like something in the file might have been corrupted due to working on OneDrive. You might not notice a millisecond of network lag, but Storyline does. That's why Articulate guidance says to always open .story files from a local drive.
You could try importing all the slides into a new project to see if that clears up the problem.
You could also submit the case directly to Articulate: https://access.articulate.com/support/contact
3 Replies
It sounds like something in the file might have been corrupted due to working on OneDrive. You might not notice a millisecond of network lag, but Storyline does. That's why Articulate guidance says to always open .story files from a local drive.
You could try importing all the slides into a new project to see if that clears up the problem.
You could also submit the case directly to Articulate: https://access.articulate.com/support/contact
Much as I hate this to be at cause...I created a net new project saved on my local C: and imported all the content from the OneDrive file. Then Preview Entire Project, and that worked perfectly.
The good news is that I didn't hose it up with a bad slide or fat finger something. The bad news is our environment is becoming increasingly ensconced in OneDrive as an enterprise solution for collaboration and sharing.
Hurray! I'm glad that worked for your project.
Having to work locally does mean extra steps when you need to collaborate. It's good to get into a habit of backing up files at the end of the day (or whenever you've done a lot of work). And if multiple folks need to work on the same file, be sure to establish a good process for ensuring no one's updates get overwritten.
BTW, years ago (i.e., pre 360), an early Super Hero told me it's also a good practice to close Storyline files before your PC goes to sleep. I don't know if it'd still be an issue at this point, but apparently the sleep/wake process would occasionally disrupt an open file. So another good habit is to close .story files when you're going to take a break.
