Flash MX 2004 Slow Code..
- Started
- Last post
- 16 Responses
- Bozilla
Ok, I've been having a lot of problems with Flash MX 2004 Pro. I have no idea but compiled SWFs are just extremely slow. Does anyone else have problems like this. I just simply don't get it. Check this out:
I did a site a while back completely in Flash MX and it was filled with onEnterFrames and packed with PNGs and stuff, but when I published the movie it ran ok. Now I'm recoding this whole Flash interface and adding some DB connectivity (besides the point) and just moving assets from Flash MX file to new one. When I publish the movie, everything is painfully SLOW! Btw, I took out all unneccessary onEnterFrames and started using Penner's easing equations, which are suppose to be much less CPU intensive. It's just aweful and a big mistery to me.
Tell me I'm not alone.
- paulrand0
I don't have it, but would also be curious to hear the answer.
- JamesEngage0
It may be something as simple as your frame rate? when I used director, i swapped machines once, and couldn't work out why it was so slow... until I noticed the frame rate
- REDWOOD0
Are your png's implemented in the .fla or are they external loaded, because when you're using a lot of png's in the fla you're movie becomes very slow.
- CyBrainX0
I'm on a Mac at home and at work, but have not noticed any performace difference.
I haven't used any Action Script 2 yet. Can you explain "Penner's easing equations"?
- MACAS00
Ok let me get this right, Your previous site was filled with enterFrames and packed with PNGs and stuff, you said "stuff", so now all of the blue you adding some DB connectivity and "moving" assets from Flash MX. Something doesn't sound right here dude. weird enough, you changed all enterFrames with Penner's EQs, now you really lost me there.
Why not code the whole thing from the ground up using the new actionscript 2 guidelines? Even though some people claim they can move assets from MX to MX2004 doesn't mean it will compatibly work as before.
The answer is yes, you're alone!
- D_Railer0
I'm actually having more problems with the program itself (flash MX 2004 professional) slowing down. I can literally type in actionscript and watch the "spinny beachball" show up and spin for a solid second while it figures our what I'm typing.
I've been wondering if it is just me... I figured my G4 with 768mb RAM would do the trick, really. So I re-built. No better. I've had my eye on G5's for awhile but I can't tell if I should make the leap or wait to see if this is mostly a Flash vs. Panther thing.
- D_Railer0
I should mention that the above is one of many problems I'm having, including publishing taking significantly longer than it used to, and just general bugginess.
- MACAS00
I use a Celeron @446MHZ with 120MB of shared RAM and it just work like a charm, read a little more on "how" to do just about anything using the new global settings, you'll see the change.
- ozhanlion0
have you got the update ?
- Bozilla0
macaso,
enterFrames is actually onClipEvent(enterFrame) or mc.onEnterFrame ...Everyone figured it out except you. PNGs are there and DB connectivity is something that I said was done in addition to the new version of FLA. Visit Penner's web site to educate yourself on Easing Equations if you're not familiar with that, a lot of Flash developers use it since it's less intensive on CPUs as onEnterFrame event.
Engage, the framerate is set to 31, the same as the previous FLA. I just can't get to the bottom of this. Tell me, do you know if a multiple calls to one globally predefined function during SWF execution might slow down everything? ie. I have one button (mc), containg empty dynamic field and I set that text field to certain values during onLoad, so I have 10 same library buttons on the stage with different 'inside labels' but the instances themselves call upon one global function on rollover. So I'm wondering if those multiple calls to one function might slow down execution.
- MACAS00
Bozilla
I know exactly the exact definition of all the mumbo jumbo you're talking about, in this case the one who doesn't understand is you, the only point I wanted to get across is that why in heaven are you developing in MX2004 if you don't have an idea as of how to effectively "move" assets from the previous versions, if you would've read some more before you jump into doing it yourself you could've save a lot of time by coming back and forth to this thread. If you want to make a smooth transition I recomend you do some reading and then decide to build your site from the ground up using MX2004, instead of just coding the easy way using MX and then get lazy by just cutting and pasting code to MX2004, it is not possible, but you know you have to hand code on PRO right?
Good night, and good luck!
- Bozilla0
macaso,
I indeed am building this site from the ground up in AS2, I'm using all of the Macromedia guidelines for developing in fmx2k4 and using new classes and methods in coding, however it seems that compiler itself has some problems. Assets as assets are the same, that's why I said I moved them from previous version, assets as in "pictures, sounds...". The whole process is called upgrading the site, not being lazy. You have a lot of reading and learning to do before we even start discussing Flash. Then we might talk, otherwise please keep your smart comments to yourself and revisit Flashkit so you can get armed with a couple of more development tips.
- MACAS00
Ok, well, good luck!
- clint0
i'm using kung fu uebercode!
no sorry, but i've been using flash mx 2004 pro for a while now, png, external movies, dynamic xml studd, everything really, and i must say, it works pretty well for me...
(by the way, i don't work for macromedia)but hey! i've had a problem.
importing images into dynamic textfields caused a lot of crashes and text weirdly changing postion whilst rolling over style links.
anyone had trouble with that as well?
- vespa0
i had similar problems and that was on a super speedy G5. never really worked it out but noticed that every time i had any components in my library, even if i wasn't actually using them, publishing became painfully slow.
- clint0
yeah, the more stuff you've got in your library, the more flash will struggle, as it still needs to handle all the files in the fla. if you think you don't need those items anymore, just delete them, it will make it easier on flash. also, once you've deleted, make a new version of your fla using save as, and work with this one, you'll notice it will get much smaller, well, depending on the files you've deleted.