Algodoo

If "Every time to sphere is hit by a laser it is shrunk 5% of its area and its density is increased 5%", then its mass would not change. The circle's mass in this scene does change.

This works:
in onHitByLaser:
radius = radius * 0.95^0.5;
density = density/0.95;

Math:
A1 = 0.95 * A0
pi * r1^2 = 0.95 * pi * r0^2
r1 = (0.95 * r0^2)^0.5
r1 = r0 * 0.95^0.5

Q: If I was able to do this in real life, by compressing a sphere 5%, would its density increase 5%?
A: No, it would increase more than 5%.

Looks like you are going to have to study algebra and geometry a little harder. I gave you the answer above and will repeat it here for convenience:

in onHitByLaser:
radius = radius * 0.95^0.5;
density = density/0.95

The density increases by 1.0526 (=1/0.95). JUST CALL IT Basic Math! Feel free to use it in any of your scenes. The formulas relate to circles. Algodoo does not have spheres. Spheres would use a different formula.

Maybe I'm a little harsh on you by assuming you are familiar with algebra and geometry. At an rate, the scene's formula for radius is wrong. It appears that you assumed it was correct and then experimentally determined the corresponding factor for density. I guess that shows some creativity and ingenuity.

These mechanisms are slightly modified versions from Figure 8 in "Classification and type synthesis of 1-DOF remote center of motion mechanisms" by Guanghua Zong, Xu Pei * , Jingjun Yu, and Shusheng Bi.

Google "1-DOF RCM pdf"

faytree,

Mechanical Engineer.

Xray,

Good idea.

Well, in that case, good work. I've been one of your subscribers for a while and am looking forward to seeing your new scenes.

There's a man who knows all his organs are old
And he's buy-y-ying a ropeway to heaven.

Nice work.

I think that the ability to filter the Algobox home page may help alleviate the problem. If I go to the "Search" page and don't enter any search criteria and sort by date, descending, then I get the equivalent of the home page. If I were able to exclude scenes with certain words ("marble" for instance), then I would get to see what I am most interested in. Marble racers, on the other hand, could include all scenes with the word "marble".

If the home (or Search) page was bookmarked, then it would save the search criteria with it. If you give the Search page utility the ability to exclude certain words, then that would be good enough for me.

P.S. The "Marble races" category is not working out too well, seeing that there are only 91 scenes in that category while there are over 3000 marble scenes outside that category.

Thanks guys.

The home page should be customized to the user. Look at YouTube, it tracks what you look at and then makes suggestions. I don't like the fact that it tracks your selections, but still it's a lot better than looking at every single YouTube video listed in reverse chronological order. YouTube allows you to search by using Boolean "+" and "-" operators. "Categories" won't fix the problem. Only 3% of the marble race scenes are in the Marble race category. Scenes you don't want to look at are just "noise". A search filter can block that noise. At a very minimum, the Algobox Search page should allow Boolean searches.

Everybody is free to use any of my stuff anywhere.

Nice work. You took what I did and went one step further. This is the way Algobox should work. This scene is a lot more user friendly than the original.

Nice work.

Nice game. Works good now.

Thanks.

Well done.

Nice discovery. I had not seen that effect before.

g := entityByGeomID((readable(owner)).geom);
v := g.color

g := entityByGeomID((readable(owner)).geom);
color = g.color

Nicely done.

Good.

Nice work.

Yes, that sums it up fairly well. I'm responding late because I initially missed this scene due to all the marble and Algicosathlon spam.

Nice work.

12.8 sec with old version

I choose orange! Oops, wrong scene.

Now the best I can get is 17.6 sec manually and 14.4 sec with code.

I was trying to figure out what is the shortest time possible. Judging form Rivet's response, I'm not there yet.

P.S. Now 14.4 sec with code that tries to imitate optimal response.

Nice work.

Yes, nice effect.