Maybe I just don't understand what you're trying to get at. Do you want there to be multiple ticks per frame?
That would implie that i drop V-synced. And that is a no-no-situation.
[quote:1vwdpoaf]What exactly is so inaccurate about 60 ticks per second unless you have incredibly fast moving objects?
I would say: try it yourself. A few behavior based bouncing balls and try to catch EVERY collission. Its not the speed of the balls thats the problem. Its the event of the collission thats very short. When i give u a tick on the shoulder, its not the speed of my arm that needs dedection. Its the very small time frame in wich i touch you that needs dedection. A bounce happens in 1/400 of a second.
Look at this:
I run it at 60 frames/second. I can optimize the dedection loops with my Cpu and Graphics card. Now build it so it auto-adjust for other CPU's and faster graphic cards.
Is the CPU faster, it can handle a bigger loop.
Is the Graphics card faster, it dont have to handle a bigger loop.