The FPSCounter class should invoke refresh() upon construction, or simply
set the lastCount private variable to equal System.currentTimeMillis().
Otherwise, the first call to calculateFPS() will store 1 to be returned as
the program's FPS for the first counting. Subsequent calls will be
accurate.
This may affect games which log the FPS via AOP to use as a debugging
tool, but this issue is of low priority.
Original issue reported on code.google.com by MetroidF...@gmail.com on 20 Apr 2008 at 8:23
Original issue reported on code.google.com by
MetroidF...@gmail.com
on 20 Apr 2008 at 8:23