HTMLIFIED [S] MAKE HER PAY but with a shorter load time
im receiving reports that this version of the flash has cut the load time down from
over 1 minute to ~10 seconds. same thing on my computer :smirk:
its thanks to cassie we were able to get the load time down by so much.
she pointed out theres a
loader in the flash's html file.
this loader...LOADS ALL THE IMAGES IN THE FLASH. the number of images
your project contains will depend on your publish settings. i exported
my images as a texture and ended up with around 800 images.
cassie pointed out the loader by default only loads ONE IMAGE AT A TIME.
YEAH THATS A PROBLEM!!!
she suggested i add this line
loader.setMaxConnections(20);
after the loader is made in this line
var loader = new createjs.LoadQueue(false);
You See...changing max connections to 20 allows 20 images to load at once. of all solutions,
this will probably make the biggest difference in your preload time.
TRYING DIFFERENT MAX CONNECTIONS
of course my first thought was well why not just change max connections to 800
so all the images load at once RIGHT?!
- 1 max connection
- 20 max connections
- 30 max connections
- 50 max connections
- 400 max connections
- 800 max connections
Wrong.
these links lead to versions of the flash each with the specified number
of max connections. if you right click > Inspect > Network you can see
at the bottom (on chrome at least) how long it takes all of those pictures to load.
50 max connections seems to be my browser's cap. after that increasing the max
connections actually seems to make the page load slower FHDSAKH
so in my experience (Of One Day) 30-50 is a good number to put there.
but even with "improved" loading time, for some the wait is only cut down to 40s.
and if you consider this on the scale of
a flash like [s] cascade (which is like 5 make her pays stitched together)
well we remain in nightmare town.
OTHER METHODS (THAT HAVEN'T WORKED (YET(?)))
- exporting images as spritesheets we thought having 3 big images as opposed to 800 small ones would help................it actually caused more problems FHDSAKJ LIKE IT WAS MESSING WITH THE VISUALS
- optimizing images used oxipng to cut the size of all images down from like 48mb to 35mb which only improved the load time by a small amount (though idk in a huge project like cascade it still might be worth it to do this)
- http2 push now we're getting Really Advanced like htaccess levels of advanced. if you have http2 enabled on your server assuming you even have a server you should IN THEORY be able to cut a huge chunk of load time by throwing all your resources at the page without it having to request them. because its that requesting that can take so much time. i didnt get very far with this one as my hosts dont have http2 enabled -_- i feel it would be extremely effective though and if you try it id like to hear about it
so um yeah gotta come back to this topic later :? if youve got any other ideas
be sure to tell me PLEASE!
special thanks to cassie witchoflight.com for
providing me basically all of the information on this entire page FHDSAJKF
<<< example: homestuck's hit flash MAKE HER PAY <<<
>>> episode 3: effects and artifacts >>>
.gif)
