so i have 2 flash movies a 900 kilobye movie is what loads on the home
page. this movie includes a menu system. rather then load a different
movie without the intro in all the other pages on my website, i want a
simple 1k loader movie to be in all other pages. this movie should
simply load the 900k movie and jump to a certain frame which will
bypass the intro. i cant seem to do this with load movie. it works
locally but not online.

can someone tell me exactly how to do this. basically 

basically have movie 1 load movie 2 and go to frame in movie 2.
remember movie 1 has to tell movie 2 to go to the frame or..if this
wont work..feel free to suggest something that will! thanks!

---

Clarification of Question by binarian-ga on 03 Oct 2003 23:59 PDT

ok so this doesnt seem to be working right...so if i were to change
this a little..maybe a cookie needs to be created and if the user has
seen the intro in the last 30 minutes lets say..then the flash movie
just skips right past the intro. i dunno how to do this..cookie ?
session ? how do i get flash to communicate then?

Sounds like it might be simpler to just create a separate movie (which
is really just another version of the main movie, but starting at the
frame you want) for the non-intro pages. So it's 2 flash movies--1 for
the intro page, and another one for all the other pages.

omniscientbeing-ga
Google Answers Reseacher

yeah the thought had occurred to me..its just the first flash intro is
fairly long...and i wouldnt want the user to wait even more for this
shorter flash intro to load.

Just so I understand this, you have a main swf file (let's call it
main.swf) which is 900kb, contains a long flash intro and the
navigation. You also have another swf file (other.swf) which needs to
load the main.swf movie and bypass the intro animation to another
frame. Is that basically correct?

If so, this is what I'd suggest as a possible solution to your
situation:

In the main.swf file
1. create a label at the frame where you'd like the other.swf movie to
jump to (ie. "nav").

2. on that frame create a stop action as well as a varible that
signals that you've hit this frame (I'll explain later).

stop();
loaded = true;

3. publish this movie

In the other.swf file
1. load the main.swf file in the first frame using loadMovieNum. This
allows you to specify the level at which the movieclip will live.
(I've specified level 100)

loadMovieNum("main.swf", 100);

2. create a keyframe in the THIRD frame of the other.swf movie. It's
important to have an empty frame between the loading action and the
next actions.

3. in the third frame, tell the main.swf movie to goto the frame that
you're interested in.

(After playing around with this one, I found out that you have to wait
until the your target frame is loaded for this to work so I added an
if/else statement to loop until our jump works)

if (_level100.loaded) {
	stop();
} else {
	_level100.gotoAndPlay("nav");
	this.gotoAndPlay(2);
}

I've posted a zip file with a working example for you to go through.
The main.swf file loops through the animation 5 times before coming to
rest on the target navigation frame. You can download the archive
here: http://lunatic.ca/example/example.zip

On a somewhat related note, I'd suggest coming about this in a
different way. Instead of having the other swf files bypass the large
animation, I'd have the homepage load it as a separate movie.
Basically, take your animation and put it into a new movie (be sure to
have some sort of loading animation, cause 900kb is HUGE). In your
homepage file, load your animation, wait for it to finish, unload the
animation and then continue to your navigation frame.

I hope this helps, good luck.

Maybe you're not considering browser cache.

I believe what you are trying to do is typically accomplished with one
file.  The file has 2 scenes.  One is a loading sequence and the other
is the main file.  The loading sequence scene runs first, looping
until the main scene is loaded completely.  Once the main scene is
loaded, the loading sequence stops and the main scene plays.

Now, on a subsequent page, instead of having some smaller file, the
same file can be used.  There will be no additional download time as
the file is stored in all of your users' cache.  It's actually
*faster* if you don't create a second file at all, no matter how
small.  The browser doesn't need to download a second file. It can
merely use the same original large file from a local copy, and can
load it almost instantly.

Prophet