This content has been marked as final. Show 7 replies
your first 3 frames should only have the preloader and your preloader should not be that large.
Thanks for the quick responce.
I know my preloader is not that large because I used the same exact preloader on another site, and it started just fine.
The way it's set up is that the first frame is the preloader, and then it goes to "s7" which is the secound frame and plays the animation of the preloader fading, then the rest of my site is after that. I guess me real question is how does flash know what to load first is it by layers (ie. layer1 then 2 etc.), or is it by frames (1,2 etc)?
if you are using components they might be set to export in the first frame causing your first frame to be heavy. if you are using components, check the proporties of them and uncheck "export in first frame" .
I'm not using any components in this site. I did notice that my background music had "Export in first frame" checked, but it's still starting at around 60% even with that unchecked.
Thanks for the the reply though.
There must be something that is hosing up your preloader. Is there still a meg on the first frame when you check the bandwidth profiler? Check out this article and see if it has a remedy;
That looked like it would have been exactly what I needed, but I followed his directions, changing the publish settings to export in frame 5. I then made sure all of my library items were not exporting in the first frame. The strainge part is that I didn't see a change at all, it still starts around 60%, and the bandwidth profiler shows about 1meg in the first frame :/
I just got it working! I used his .jsfl script and that did the trick! Thanks to everyone that helped, much appreciated.