Scratch

I don't think it has a set framerate. Every single image-manipulative block is done completely, before it moves onto the next block (I'm pretty sure, although I could be wrong since I don't see the source of scratch a lot).

If you want to be able to control the frame rate, you could just have all the rendering scripts run at around the same time (you would need to have either a bunch of broadcast and wait's running in sequence, or just a 1 sprite 1 script project), and to slow it down put wait blocks.

codeblue wrote:

I'd imagine that could get buggy.. Normally what is done in programming if the update isn't set you get the change in time between two frames then multiply the movement of an object by that time to keep it consistent, but the timer only keeps track out to on decimal point of accuracy. I need three decimal points for this method to work. Any ideas of how to get more accuracy in measurements?
Thanks,
Cody

Instead of using Scratch's timer, you could create an artificial timer, though this isn't too much more accurate. In fact, it's only accurate to the fortieth of a second. Anyway, here's the script for the artificial timer:

when gf clicked
set [timer v] to (0)
forever
 change [timer v] by (.025)

Last edited by ErnieParke (2012-11-18 15:34:06)

remember that scratch takes 0.2 seconds to process a block btw

Thanks everyone for your replies. Apparently the fps implementation will not work in scratch for whatever reason. I have conceded to a fall back method where I simply calculate the position of the object based on the formulas of newtons law of motion instead of incrementing the acceleration every frame. Thanks again for your input!