Oh yeah I sometimes try to do maths before scripting in Phun because otherwise I wouldn't know how things have to be set. For me personally it's important if I want to script things dynamical. For constant things I just try different settings and choose the best - no need of maths.

This is an example of doing maths before Phun


Author: KarateBrot
Title: Pointer (works with torque)
File Size: 46.25 kB
Rating:


You can see the formula for the acceleration of the motor (and i mean acceleration and not velocity of the motor). So depending on how much the angle of the pointer deviates from the angle to the block the acceleration of the motor is bigger and the pointer will be affected by a stronger force that pulls it's direction towards the block.


[Edit]
btw... look at scenes from Kilinich or someone else who uses scripting very often and is 1337 at it. You will often recognize formulas.

Last edited by KarateBrot (2009-08-29 11:02:42)

Lol. Phun is a Thyme interpreter. This(SS-P) will be the second time I ever had to use math in Phun


@arinlares: IDLE

Last edited by cdh473 (2009-08-30 08:18:33)

Some scenes where precision is seriously necessary.

Torpedo wrote:

Thats quite neat, where did you hide half the scripting, i like taking scenes like that appart and trying to find them, but i cant find what makes scene.my.v, or scene.my.alpha lol. its a mystery!

there are three oncollides. the first one in the center of the pointer, the second one in the center of the box and the third one behind the black rectangle that says "angular deviation". most of the scripting was done in the third one. the other two are only to get the positions and the angle of the pointer.

i named the variables like the physical variables so "scene.my.v" would be velocity (it's the velocity for the motor), "scene.my.a" is the acceleration of the motor, "scene.my.k" is only a constant so that i can change the strength /speed the pointer does its turns so if i attach the pointer to a very big mass you have to set a very small constant so that the force is strong enough to let the big mass point towards the box fast.
"scene.my.hJavelin" is the height of the pointer, "scene.my.hTarget" is the height of the box. "scene.my.sJavelin" and "scene.my.sTarget" are the widths of the two objects from the origin. (i know i could have put 2 values into one variable so there are only two position variables but at this point in time i wans't good enough at scripting to know that.
"scene.my.alpha" is the direct angle between the pointer and the box (you also could say it's the angle between the two points). There's an image in the scene (the upper one). there you can see what i mean.
"scene.my.beta" is the angle of the pointer. i need this two angles to calculate how much beta is different from alpha so that the motor can make a correction until alpha = beta. (btw: the acceleration is the difference between the two angles divided by the constant) so if the angles are the same the acceleration is 0 and the motor speed will stay the same so there is no force that pulls the pointer into a direction.

you can fell this effect in real life by turning on/off an angle grinder. as long as the disc accelerates you will notice a force in the opposite direction of the spinning circle.