Re: Re[2]: [Gnash-commit] gnash ChangeLog server/parser/movie_def_impl.cpp [gnash_0_8_3_branch]

[zou lunkai]

> Hello Sandro,
>
> Thursday, May 15, 2008, 8:00:25 PM, you wrote:
> >> Normal limit is 120 fps!
>
> To clarify: this is the maximum value you can set in the IDE.
>

120 should be better. The real fps can be even much higher than 120
though, but doesn't make much sense. '84' sounds like a mystery
number, which is a bit misleading for future improvment.

>
> SS> If you have a debugging version of the adobe player, please
> SS> try running this movie and tell me what's reported:
>
> SS> http://foo.keybit.net/~strk/tmp/fpsdebug.swf
>
> SS> It will return (totaltime/advances).
> SS> Is 12 with my version of pp, which is 84fps.
>
> It keeps reporting something like this:
>
>  avg fps after 7132 iterations: 5.72139652271453
>
> However it starts with a higher rate and slowly goes down. Note that
> after 15 seconds it says:
>
>  avg fps after 1542 iterations: 10.0771725032425
>
> note that 1542 iterations in 15 seconds means ~100 fps IMHO...
>
>
The test itself should be improved for highest frame rate testing.
(1)The frame rate is not stable as the iterations increase(I confirmed
Udog's results). (2)too much traces in the test, which affect the
frame rate a lot. TRACE for pp is pretty slow!!!


improved code for testing the highest fps:

total = 0;
num = 0;
avgFPS = 0;
_root.onEnterFrame = function ()
{
    total = getTimer(); // time unit: ms
    ++num;
    avgFPS = num*1000 / total;
    // print the result every 100 frames, trace is pretty slow
    if(num % 100 == 0)
    {
        trace ("avg fps after " + num + " iterations: " + avgFPS);
    }
};

With FPS set to zero in SWF file, the average FPS I got is around 600.
And probably it could be higher if less printings involved.

--zou