Algodoo

Then, nicely corrected form!

There's other problem too, what happens if there's any other surface inside of the polygon? (talking on 2D plane)

Xray - Now i can! I forgot that you told me that sorry ! I will explain my codes on the forum.
s_noonan - Thankyou!

However, this scene is not yours, this scene is a copy of kilinich's bomber game scene.

Xray thankyou.
About panning and zooming I did it on purpose

I think you should try it then.

Nice idea ! Where could I find more images like these?

Thankyou vaidas !
Edit: there's a bug on typing (number)comma(number)comma that I haven't seen before, but I can't fix it for it's complexity ; when typing two numbers with comma.

Xray I don't think that that problem is mine, because the syntax is correct.
I think it's problem of algodoo, sometimes it happens to me too.
If you don't belive me try creating a box and coding it's text as :
{
"" + (3 / 8)
}

I tried it and it gives me the value of 0 too.

Oh thankyou ! but (in the case of animated gifs), how can I split the gif per frames?

Nice .

It would be more realistic if the cables actually transfer the electricity, or, at least,
without using scene.my.variables.

Thankyou!
We could actually suggest on the forum to fix that huge problem.
Or at least it is for me because its easiest to type an integer value without typing the decimal point.

You are typing numbers instead of a variable.
Try:
scene.my.test = (a,b,c)=>{c=a+b};
> scene.my.test(1,2,scene.my.variable)
scene.my.vari­able will be equal to a+b, namely, 1+2.

> scene.my.test = (a,b,c)=>{c=a+b}
(a, b, c)=>{
c = a + b
}
> scene.my.variable = 0
0
> scene.my.test(1,2,scene.my.variable)
> scene.my.variable
3

Algodoo is not actually a good thyme / operation solver

I use Algodoo 2.1.0 b13.
I don't understand too why I don't get an error, maybe because my computer solves things that could not be avaiable to solve.

Wow really good! I have learned scripts from kilinich too but just watching it on the scenes and the scripts that I don't actually understand are the scripts form he's mouse over polygon scene, the laser that hits a polygon and changes it's surfaces an the deformable polygon scene. As you can seeall are polygoms! .

Xray, How do you get geometries unclickable?

Oh thnx!

Xray, nice idea but as chemist said this scene is nos well maded at all, it could be improved using randomness if the fish isn't near enough to move it, you could actuaclly add the possibility of moving to all directions (x,y) vectors.

However, nice game my score is 30!

Xray, I actually give you the copyright of this example to make your own game! I haven't got actually enough time to make scenes so Im not avaiable to make them because of my High School infinite exams. Oldo, I cannot do anything too on the weekend!

Edit I hope this scene helped you to have a better idea of how to make randomness or at least, help you on anything!

Sorry, but I could'nt ask your question.

Im thinking to the best fishing game with "animations"! changing velocity when ther's something frightening to the fish or to move with a schoal and a man fishing them with a fishing rod! Wow.. it could be very ,very ,very rated!

There aren't any references with the circle (light), only with the angle.

Xray, that wasn't any suggestion I was talking to you and the other people thst the scene I said could be very rated.

Nice demostration .
What uses could this scene have?

In a program, I mean, when you use the pencil tool to make straight lines.
Obviosly with the appropriate script language transcription.

(gm,tar,d_from)=>{
m=(from, to)=>{math.atan2(to(1) - from(1), to(0) - from(0))};
pv=(v)=>{v<0? -v:v};
gm_a=m(d_from,gm.pos);
tar_a=m(d_from,tar);­
[1,0,pv(gm_a-tar_a)*3,1]
};

gm= a pixel (box)
tar= target ending line point (app.mousepos), in this case there's not ending point.
d_from= starting point, (where th line stars displaying([0,0])).
m= intrinsic function with 2 arguments. Maths the angle between 2 points (startingpoint,ending point).
pv= intrinsic function with 1 argument. Makes a value to positive being negative or positive, pv(-1)= 1; pv(1)= 1;.
gm_a= Angle between the starting line point ang the pixel (box), uses the m function.
tar_a= Angle between the starting point and the ending one, uses m function.
pv(gm_a-tar_a)*3= the difference between gm_a and tar_a.
The other array variables are the rest of the colorHSVA features.

I hope you understood it, Thanks! .

Edit: The display variable is able to change in the text box, if you know how to fix the 2 problems, or at least one of them please upload the scene without the problems.

Could you please explain how math.log works please?

thanks.

I did it on purpose, I wont to make the code continuosly defined to change the code if it failed working and directly change it, why it isn't good?.
I did it o purpose to the user help me too!
By the way, do you know how to fix the problems on the function?