flash frame rate
- Started
- Last post
- 23 Responses
- BonSeff
whats a good rate to work with? In the past I heard 32, but now I'm hearing 18.. Soo what do ya'll use?
- emecks0
1.
depends really BonSeff, don't use frame rate to control anything in your SWFs and your fine.
Use SetInterval();
- blaw0
by default i go with 24 fps.
- smielke0
31 or 41 depending upon how big the canvas is. If it's smaller you can get away with 41 without chugging on older computers.
As far as the earlier comment goes with controlling all your stuff with an Interval, only do that if you're a programmer and know what the F is up. Otherwise the timeline is God.
- ********0
31.
Can't remember why now. But I was told by someone long ago that it was good.
But I do try to do most of my motion in code now so it's not of such importance.
- ********0
(x32+y18)/6+283-18(95x23)-32/2+1... - by2 + cy - d + y - x + b/3 (x2 + p + y)2 = px2 - qx - r + p2 + 2y(x2 + p) + y2 + (q2 - 4p3 + 4 pr) + (-16p2 + 8r)y - 20 py2 - 8y3 e3(e3 - 2c3) = b6 so that b6/e3 = -c3 +√(b6 + c6)
= 2
- lvl_130
31 or 34
- UndoUndo0
31 cos of dem pesky macs
- monoboy0
I use 35, just to be awkward.
- play0
Why the number 31? seems like a funny number
- UndoUndo0
who knows, it fixed a few problems with animation on the mac, this might have been sorted with the new player release but i'm happy to work with it and also agree its a funny number...but then flash is...funny
- blaw0
re: 31fps
http://www.ariaware.com/products…still, i think it depends upon how much you have going on. i try to use the lowest possible framerate that still renders smoothly. for me that generally works out to be 24.
- alloyd0
The 31 for Mac's isn't documented by Macromedia/Adobe. I think someone made that up and a lot of ppl have just followed it during the years.
Frame rate: Depends on what you are trying to do and if a high frame rate is necessary. For example, if you have a ton of stuff going on and a lot of objects bitmaps etc, then a lower FR would be ideal (18 FPS). If you are using simple stuff and mainly vector objects, then you could get away with a high FR (30 FPS or higher). Also, depends on what kind of computer you might expect ur demographics to be viewing it on. You can go high, but ur asking Flash to compute a lot of stuff a lot of times per second. I would try to base your code or animation on time instead of frames, this way you can adjust the FR later on during testing.
- blaw0
undo, i was under that impression that everything was sorted out pc/mac-wise. now the 31fps is more of a secret handshake between folks that have been working in flash for a longer time.
- kravatronic0
12fps is the animation standard, established way back when...24 is the standard film frame rate...anything over 30, the eye won't notice.
- emecks0
just because it isn't documented by Adobe I wouldn't not believe it.
In general the FlashPlayer will always *TRY* to play at the frame rate that is set in the SWF. It will actually never achieve that frame rate - how much it lags by is dependent on what it has to do every frame.
hence using setInterval being wiser where ever it is possible, it removes dependency on the Timeline.
- UndoUndo0
I dont think the issues have been completely sorted...there are still ppl complaining about flash on macs albeit it being in teh authouring tool. it terms of the frame rate i also dont think 31 was a myth, but as MX said setInterval should be used where possible
or setTimeout() in flash8 (not documented)
- emecks0
aye Undo, also not everything that isn't documented by Adobe doesn't exist. I don't recall them documenting a good number of FH bugs and a number of nice DW ones either.
That said neither did MM, there's not one better than the other.
- alloyd0
yep, you both are right. setTimeOut() , ASSetPropFlags()...undocumented by Adobe at one point in time, and then well-documented by experts in the Flash community later on.
31 FPS myth, never well-documented with tests, charts, etc by an expert in the Flash community or by Adobe. I've heard about this since 2001 or so and have yet to see any real tests on it. I feel like I do a big search on this once every year and never find any solid reasoning/logic behind it. I just don't see how the extra frame per second will do anything but just offset things. Maybe someone tested this on a specific MAC-based system at one point in time and the myth has just kept. What logic is there for it working correctly on a PC and not a MAC. Has this been tested on more than one Mac-based system.
Guess the best way to find out, is to do it urself tho. Throw a FPS counter in and check.
- mrbee28280
There was a game presentation in like 2001 at Flash Forward where the guys (maybe James Baker & co.) showed the same swfs running on Mac and PC at different frame rates. What they discovered was that using even numbers on PC would run like 10 frames or more slower per sec. But, if you went to a odd # like 31 the difference on the Mac was only like 3 frames per second. This used to hold true for everything.. 40/41, 60/61 etc. I don't know if all that holds up anymore.... that was like F5 :)
- st33d0
Hrmm, I've just been using 24.
Most users (friends) I visit have shit computers, and I tend to make Flash work quite hard.
I might step up to 25, but 30 is a bit overkill when I want consistent animation on all machines.
I think I will follow that setInterval advice in future though. I use it instead of onEnterFrame more and more.