A Flash Developer Resource Site
|
Internet Commerce
Developer ChannelFlashKit.com
JavaScript.com JavaScriptSource Developer Jobs ScriptSearch StreamingMediaWorld Web Developer's Journal Web Developer's Virtual Library WebDeveloper.com Webreference Web Hosts XMLfiles.com
internet.com
|
  Tutorials HomeWhat's NewTop RatedSubmitmyTutesRandom!
Search Tutorials
 Tutorials » Getting_Started
Flash creates compact web animations so a trade off occurs - smaller file sizes and less CPU intensive movies for slightly chunkier animations. At 12 fps, the end result is still pretty good. What will determine the quality of your movie on the web will be the complexity of the animation and the speed of the computer on which the animation is being played on.
An fast animation or one with lots of objects can be CPU intensive which means the computer will have to "draw" the images much faster, and the more complex they are, the harder it will be.
Sure, you can bump it up to 30 fps, but beware, if you have a groovy but CPU intensive animation many of your visitor's computers will grind away leaving them most unsatisfied - thus defeating the reason why you are using flash in the first place. You could use a preloader which would take out the bumps caused by a slow download but the CPU issue remains. (I can hear all those artist's hearts breaking :)
THE Rule: Test your animations on a variety of machines to determine optimum frame rates. Easier said that done, I know, but this is where common sense comes in. If you pII stuggles at times in an animation, can you imagine what a p100 will do with several applications running in the background?
|
||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|||||||||||||||||||||||||||||||||||||||||||||||||||
Figuring Frame Rates
|
 |
 |
|