1. When you publish your file, there is an option to create a file that
gives you a progressive look at your use of memory.
2. Perhaps your animation needs more pieces so it won't look choppy when the
server can't keep up with the framerate or bit (not byte) rate of the
sequencing. Typically the eye uses 24 frame/sec and animation can be done
at 12 frame/sec with a double up to fool the eye rate. So, your animation
will need 12 different frames per second at a minimum playback to be useful
online. If you can figure this out on your own computer at 12 fps, you will
probably have a hit, but you are just hiding the problem by advancing the
frame rate to 41 fps.
3. You are covering a large area with the hand pulling down the curtain.
If you do the pull in one second you need 12 pieces, if faster you need more
pieces. Maybe changning the drawing of the arm for each part of the pull
will help, maybe adding more pieces to the curtain will help....maybe your
are just stressing the limits of the online technology. Anyone familiar
with early1990s multimedia well remembers this problem as it related to TV
animation or CDs.
4. Ultimately you have to solve your own problem. It doesn't help to be
insulting because of your own frustration.
r
[quoted text, click to view] "tommyguns" <webforumsuser@macromedia.com> wrote in message
news:cjpstb$p72$1@forums.macromedia.com...
> if anyone wants their sh*t answered go to flashkit.com, this crap's stupid