> It's interesting to note that the reported > FPS keeps slightly growing, but the same > happens with adobe player 10 (which starts > from 10.0 FPS and goes up).
Oh, I forgot to say, you have to wait for FPS to stabilize first. (see, it doesn't even come with documentation yet. tsk...) The algorithm for computing FPS is as follows: >From the time the .swf starts running: * store timestamp of when .swf started, start counting frames rendered FPS = frames rendered / time elapsed Thus, you have to wait a bit (30secs-1min) for the FPS to be more accurately measured. I suspect there's a slight delay/freeze when the .SWF first kicks in that's why starting FPS count isn't as accurate. I'll add a delay before TeddyMark starts of the frame counting and start time stamp recording. Regards, -Naz -- Carlos Nazareno http://twitter.com/naz404 http://www.object404.com -- interactive media specialist zen graffiti studios http://www.zengraffiti.com -- User Group Manager Phlashers: Philippine Flash ActionScripters Adobe Flash/Flex User Group http://www.phlashers.com -- "if you don't like the way the world is running, then change it instead of just complaining." _______________________________________________ Gnash-dev mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnash-dev
