Skip to main content
M
Metapod
Inspiring
November 24, 2015
Question

Preloader set 100% files, still downloading

  • November 24, 2015
  • 1 reply
  • 302 views

Hi all

Using Captivate 7. I set the preloader % to 100%

I see the animation appear

In Chrome or IE I go to developer tools and network

As I move between slides, I still see images and assets being downloaded. Isn't the whole idea of the preloader to stop this from happening ?

The reason why its an issue for me, is we have an inconsistent issue where parts if the screen just do not appear. See below slide 1 where everything appears:

and now slide 2, missing things from the screen.

As far as I know, I cannot narrow it down to browser, or operating system or even internet provider and speed. It is just intermittent. The only thing that makes sense is that the images haven't been downloaded from the web server in these situations. Would love some help understanding this.

Thanks

This topic has been closed for replies.

1 reply

RodWard
Community Expert
RodWardCommunity Expert
Community Expert
November 24, 2015

Are you publishing to HTML5 by any chance?

M
MetapodAuthor
Inspiring
November 24, 2015

Yes I am

Is that an evil combination ?

Am I correct in assuming the only way around this is to include all the images etc on the first slide and hide them somehow ?

RodWard
Community Expert
RodWardCommunity Expert
Community Expert
November 24, 2015

Preloaders in Captivate are usually SWF objects.  They're NOT going to work in HTML5 output.

Furthermore, whereas you COULD preload 100% of an SWF project into your desktop browser and avoid buffering that way, HTML5 is intended to run on mobile devices which are often starved for resources.  In many cases they simply would NOT be able to cache your entire course.

So, as you have observed, preloading in HTML5 courses works differently to SWF. 

I haven't worked out the algorithm yet but it seems some slide assets are only loaded when you get to each slide, and those same assets are deleted after you move a certain point beyond the slide where they were loaded.  This means rapidly clicking back through slides or scrubbing the playbar in an HTML5 project will almost always cause some issues.

This also means that your idea of caching up all the images on the initial slide is more likely to crash your mobile browser than solve your preloading issue.  But you're welcome to try!

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices