Forum Discussion
(loading) speed of Storyline 360 slides
Hi all,
Does anyone know what influences the loading time of storyline 360 slides? We are creating educational games with storyline, and are trying to figure out how we can decrease the amount of loading (with the three loading dots) between slides.
I have a few ideas on what impacts the slide loading time, for example:
- Amount of layers on a slide
- Amount of objects on a slide
- Amount of images in a slide
- The length of javascript functions
- The amount of audio files
- The size of audio files
- The amount of video files
And maybe other that I haven't thought of yet..
And a few questions:
- Does it matter if you put objects / images / video / audio on timeline start, or after let's say 1 second?
- How does Storyline internal "pre-load" slide work? I have read somewhere it makes an educated guess which slide comes next, and preloads it. But, as we make a slide selection based on variables, that won't work.
- Is there any way we can feed storyline information about the upcoming slide, so it can preload it already?
I'm very curious to your insights.
I will also do some research myself the next few months, and share the outcome, but it will help to gather some input and thoughts from other users before diving in further!
1 Reply
A few first findings I had myself:
- The number of objects on a slide matters: The most objects seem to be loaded synchronous, so the more objects, the longer your loading time is. Especially if the end-user internet is a bit slower and you have big file sizes (or a lot small size files).
- All SVG files (articulate objects or your own) are loaded via a JS script and calls a function. I'm not sure on the speed on that specific function, but that can give overhead
- It does not matter where on the timeline the objects are, all objects are loaded before showing the slide.