I think the secret to those numbers lies in what times per frame they represent
2500 fps = .0004 sec/frame
2000 fps = .0005 sec/frame
1666.7 fps = .0006 sec/frame
As they have a linear difference, it seems somewhere the calculations have a value being aliased. It may be that the timer used on your system to get timing information is running at a 100 microsecond resolution, so all timing samples are aliased to one of those 3 values.
On Thu, Aug 21, 2008 at 12:49 AM, Ian Mallett
<geometrian@xxxxxxxxx> wrote:
...runs at one of three values: 5000/3, 2000, and 2500. These are nice big numbers, but I can't help but notice that they are significant in their roundness (or niceness). Is there a particular reason for this?
Ian