RequestAnimationFrame = Every Tick?

Is Every Tick RequestAnimationFrame?

Huh?

Uh, I don't think so. Every tick = CPU ticks.

en.wikipedia.org/wiki/CPU_time

Oh okay :)

I though Ticks are Frame rate dependent, which is why we always type * dt

Schoening - I'm not sure what your original question is actually asking, but in browsers which do support it, the main game loop is driven by requestAnimationFrame (otherwise a simple timer if not supported).

andreyin - I think CPU ticks usually refers to a single cycle, i.e. 1 out of the 3,000,000,000 cycles per second in a 3GHz processor.

All you really need to know about "Every tick" is it aims to run 60 times a second, but if the system is slow it could run less frequently.

Sorry for asking many questions :)

Just interested because I learn a lot of JS at the moment.

And thanks for the answer ^^

Schoening - I'm not sure what your original question is actually asking, but in browsers which do support it, the main game loop is driven by requestAnimationFrame (otherwise a simple timer if not supported).

andreyin - I think CPU ticks usually refers to a single cycle, i.e. 1 out of the 3,000,000,000 cycles per second in a 3GHz processor.

All you really need to know about "Every tick" is it aims to run 60 times a second, but if the system is slow it could run less frequently.

That still amazes me, 3 MILLION cycles a SECOND! I love technology.

Carry on.

That still amazes me, 3 MILLION cycles a SECOND! I love technology.

Billion ;)

I made a quick demo comparing JavaScript ServerSide to ClientSide Speed:

Client:

http://dl.dropbox.com/u/53738503/LoopTest.html

Server:

http://dl.dropbox.com/u/53738503/TestSocket1/index.html