speed of move

krousty_bat

I was wondering, If you use the "move", can we know the values you enter in Speed in terms of pixel per seconds or some other way to calculate it.

I mean, Yes, 1, 50 or 120 are cool, but If I would like ot be more precise, can I know what those values are the calculate results of ?

Thx a lot !

JohnPapiomitis

Like tshirt i dont know what the set per pixel per every increment of one, but i made this so you can tell about how many pixels something moves per second depending on the speed set in the move behavior:



The move behavior isnt the most precise, so you might get a couple pixel difference here and there, but its on for the most part and will probably give you your best answer if your using the more behavior.

How it works is it has the intial x position stored in a attribute. The speed in the move behavior is set to a global speed attribute and will act the same if 200 is directly typed in the speed section of the move rule, or if the attributes set to 200. It then moves at that speed for 1 second, then subtracts the end position from the start position to give you the amount of pixels it moved. All you ahve to do is change the speed attribute to whatever speed you would type in the move behavior, and it will read it for you

The pixels per seconds display is in a floor expression, so it will round to a even number for you.Again move isnt exactly precise, so you might get a range in a couple pixels here and there if you keep doing it over and over, but if u need to use move instead of interpolate, this will give you a pretty close idea of what it is.

This is the best i could come up with without knowing the set pixels per incrament or anything. IF you want a copy you can email me at papiomitis at yahoo dot com

cheers

krousty_bat

@TSB: well, thx, It's true that right now, I would find this info pretty useful to calculate for precision matter. My guess is that it's in cm per secondes probably, not in Pixel per seconds, but i would need to know on a 72 DPI, how to calculate all this.

@John: pretty good idea, thx for the tip !!!
I was wondering, did you try this with the same values on a different screen resolution (IPod/Ipad let's say) ? and do you get then the same values for 100, 200 and 300?