PS, man. 70-120MB swf's are way too big. You need to start loading some of your content!
-Scott On 12/21/06, ben gomez farrell <[EMAIL PROTECTED]> wrote:
I was having this problem a while back, I never really solved it, just ended up working around it. I think, taking a wild stab at what's going on, is that a tween is one of those things stored in RAM along with a million other things. In my case my flash movies were 70-120MB. So I think when memory started getting tight my tweens would disappear. Actually going in and doing something to the offending clips would make Flash recalculate and put it in RAM again, fixing them. Thats my theory. I wrote to Adobe who was really no help telling me to make my Flash movies smaller. You'd also be amazed at what cleaning up your timeline will do in this situation if it's disorganized. I also found that a save and compact will generally do the same thing as delving into the offending timeline....but will do it for your whole project at once. If your project is particularly large, a save and compact won't work 100% of the time, but often helps. I think we've also found that throwing more RAM into your computer will help. And the last real kicker is, Flash MX 2004 does NOT have this problem. So if you can work in 2004, do so, and you'll be trouble free in regards to this problem. ben slangeberg wrote: > I have a strange problem (Flash 8) where the designer created motion > tweens > on the timeline, which causes clips to fade in / out. She used the > properties dropdown box to set alpha, then created a motion tween between > two keyframes to accomplish her fades. > > This site is built dynamically, through attaching clips from library. > Sometimes the tweens magically disappear, and you just see the clips > visibly > pop in and out, rather than fading smoothly. NOW, this is the kicker - > when > the tweens disappear, my fix is to delve down into the offending > timeline, > check that it's all there, then compile. POOF - the tween is magically > working again! > > So - I can get the tweens back, but it's rather annoying to do this > all the > time. Also, I hate leaving random Flash bugs floating around, so any > insights appreciated. Have a feeling this will be just one more phantom > Flash problem floating in a project. For some reason, I must have at > least > one per project! > > Thanks, > > : : ) Scott > _______________________________________________ > [email protected] > To change your subscription options or search the archive: > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > Brought to you by Fig Leaf Software > Premier Authorized Adobe Consulting and Training > http://www.figleaf.com > http://training.figleaf.com > _______________________________________________ [email protected] To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
-- : : ) Scott _______________________________________________ [email protected] To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
