Forum Discussion
How to make Scenario blocks more efficient (file size)
Whenever you include a character in a scenario all of their pose images get bundled into the published output, not just the ones you use. As these images are high resolution – needlessly so for the use case, in my opinion – each one weighs in at over 1MB, and each character has ~25 poses, so you're looking at around 30MB per character.
Presumably end users won't need to download the unused images as they aren't displayed in the scenario itself; I haven't checked to see if it does any background caching or anything like that. As such they should only be taking up a bit of hosting space, which typically won't be a big deal.
In terms of what you can do, you could optimise the published output yourself. For example, if you open up the zip and navigate to scormcontent then look in assets you'll see all of the images used in your course. You could then:
- Delete any of the character poses you don't use. (Could be annoying to keep track of this.)
- Resize, and replace, the pose image files you do use; make sure the randomised file name is retained exactly. Here's a comparison where I've halved the dimensions, for example, which still looks fine in the scenario block itself but reduces the file size by 80%.
As you'd need to do the above every time you publish the course I'd generally suggest you don't bother. However, those workarounds might be useful if you're receiving specific complaints or the module is likely to be viewed by people with limited internet connections.
Thanks for this detailed explanation, Sam! :)
Related Content
- 4 months ago
- 3 months ago
- 4 months ago