Movieclips starting in frame 2?

[Protected]

I have a large .fla in CS3 (more than 1000 objects in the library). I seem to be experiencing a strange problem I'd never seen before, and I don't find anything about it on the web: My latest movieclip, which is exported via the Linkage dialog and then created via AS3.0 (that is, using new NameOfTheMovieClip(); ) contains a series of statically created movieclips inside it, some of the same type, the others of different types. Every single one of these movieclips is starting in frame 2! when the "father" movieclip is made visible (with addChild), everything inside it is on frame 2, or cycling through the frames (which would be impossible if the stop() in their first frames had been read). Does anyone know what can be causing this?

[Protected]

If it helps, when I place the parent movieclip in the stage manually (rather than with actionscript) without changing any of its properties or any .fla settings, its contents start in frame 1 as expected.

[Protected]

Alright, it looks like this is an actual bug in Flash CS3/Flash Player 9. If you add a movieclip (via actionscript) that has only one frame and it has movieclips with 2 or more frames inside it, those movieclips will start on frame 2. To fix this problem on CS3, one must either manually set each of the inner movieclips with gotoAndStop or gotoAndPlay or artificially inflate the parent movieclip by inserting a blank keyframe in frame 1 and putting the content in frame 2 (yes, this will make the inner movieclips start in frame 1). In flash player 10 this problem shouldn't happen at all, but it's annoying if you only own CS3 and want to test your work in it!

[Denvish]

Not a problem I've seen, but I'm still on AS2. On the whole, when you attach a MovieClip, you'll be telling it to stop(), or gotoAndStop(frame/random(_totalframes)+1 ); anyway, so this shouldn't really affect.

[Johnny]

At 2/17/09 12:14 PM, Denvish wrote: Not a problem I've seen, but I'm still on AS2. On the whole, when you attach a MovieClip, you'll be telling it to stop(), or gotoAndStop(frame/random(_totalframes)+1 ); anyway, so this shouldn't really affect.

I know many people put the stop on the first frame of said movieClip, instead of after the attachMovie statement, so it would skip right over that.

That's an odd bug though.

[jonathanasdf]

This JUST happened to me. Yeah, it seems like a bug with flash, because when I added a second frame to the movieclip with 1 frame it was solved. Weird.