Algodoo

Q: Is this a new fashion?
A: I thought it would be, but after some searching, I found that bark prints are not uncommon.

Nice work. I like how you comment your code.

I messed up here so I figured I try some white on white and see if anybody notices.

T h a n k s .
Put a space in front of each letter.

Nice work as usual.
⭐⭐⭐⭐⭐

Thanks.

I used to do
    rem := "This is a comment";
but I recently noticed that Ky13harbor9 does
    THIS_IS_A_COMMENT;
and Algodoo doesn't seem to care.

So your idea of
    (comment);
is as good as any.

Thanks Xray. I will fix my original comment in case users try using it before reading your comment.

You are getting there. I'm seeing 15 seconds load time. You initially had:
2151 geometries
10142 narrow collision tests

You now have:
1665 geometries
7221 narrow collision tests

After modifying your scene, I had:
181 geometries
688 narrow collision tests

This is what I did:
Instructions above the main chess board that were not text were converted to images. Tiles and chess pieces below the main chess board were replaced with (24) distinct tiles and (12) distinct chess pieces.

I like your new chess pieces.

P.S. Another idea to reduce geometries and collisions would be to convert the chess boards into 1 box with 1 texture. That will replace 64 geometries and 210 collisions per board to 1 geometry and zero collisions per board.

P.P.S. If you take the white chess pieces and invert the colors on the transparent .png then you will end up with black pieces with white outlines.

You might want to ask sombra permission to use his walker legs design(runner robot).

Thanks.

I will add a response scene. Use what you need. Let me know when you have it and then I will delete my response scene.

Q: Does setting collideSet = 0 reduce lag.
A: No, for some reason Algodoo still does narrow collision tests.

Response scene has 105 geometries and 254 narrow collision tests.

Q: Is there a way to delete a custom variable?
A: Copy the object. Paste into text editor. Delete dead variables. Copy All. Paste into scene. Delete original object.

Other than giving young children nightmares, this is a good scene. I like that he can jump.

in laser:
_x := "hello";
_makeVarInBox := {
g := entityByGeomID((readable(entity)).geom);
g._y := _x
};
onClick = (e)=>{_makeVarInBox};

Thanks.

Thanks. I spent a couple hours checking both of those links out. I couldn't find the same linkage that's in this scene but suspect that the linkage would be obvious to "A person having ordinary skill in the art" (patent wise) since it's made of two common linkages.

Q: Does this mechanism have better linearity compared to your previous scene?
A: Theoretically both have perfect linearity, so the deviation displayed is the limitation of Algodoo. In real life the linearity would be due to the accuracy of machining the parts, deflection of the components due to gravity, and free play in the bearings. Effects of those (3) factors could also be modeled in Algodoo, but I'm not planning on doing that anytime soon.

Nice scene. Easy to use. Very well done.
⭐⭐⭐⭐⭐

Thanks. I downloaded this book in 2008. The website is a lot easier to navigate than the book and there are some animations on the website. I reviewed the first 300 mechanisms and now my head hurts.

Looks to me like you unsuccessfully copied my Animated Alphabet scene. I suggest making your own scenes instead of trying to copy somebody else's scene and passing it off as your own.

Looks to me like you unsuccessfully copied my Animated Alphabet scene. I suggest making your own scenes instead of trying to copy somebody else's scene and passing it off as your own.

I was bored so I watched this scene and then checked out the code.

Nice scene.
⭐⭐⭐⭐⭐

I suggest select head and then check Selection>Follow.

Thanks.

Thanks guys.

You can't. Running man doesn't work in other scenes. Running man controls are hidden behind a black box just over his head. Even if you copy the controls he will still flake out. I think you would need to create and initialize a bunch of scene.my variables in order for him to work in another scene. I might make this phunlettable but make no promises. Subscribe to this scene and you will be notified if I make any changes.

Nice work. I rated this highly even though I don't completely understand it, but suspect that you do. I'm presently checking out the LiquidPiston engine on the web.

JakubKubo,

Nice work. I like your concise method of coding.

Xray,

I can see this being used for steam, smoke, or fire where you want to limit the maximum number of particles in order to reduce lag.

Ethan Farparan,

See response scene.