Algodoo

That's a good idea and it's possible, but I'm not sure if or when I would make that change.

This is epic. Very well done.

Thanks for the compliments and suggestions. I'm finished playing with this scene for a while, so feel free to modify the scene and post the results. I'm sure you can do items #1 and #2 without too much trouble.

Item #3 for one die shouldn't be too bad if you substitute die face images for the animal images. The refPts in _3pts2tm are the corner points of a texture centered on [0,0] that has textureMatrix = [1, 0, 0.5, 0, 1, 0.5, 0, 0, 1]. The images are off screen to the left. X, y, and z offsets can be added to the _ra3DPoints array to move the position of a die.

Nice work. Now you just need a white cross like those seen on gambling recovery centers.

Nice work. I see how you did that.

Nice work.

Your check is in the mail.

Thanks guys.

T_Reißig,
Mechanical Toolbox

Start sim. Click the orange button. Stop sim. Select just the blue base form. Copy box and paste into text editor. Code is based on AGMA Standard.

There a restriction in Algodoo that limits the amount of surfaces a Polygon can have. One way to improve resolution is to set sim.polygonMeshSize = [1024,1024] or some other big number, create the gear, it is low resolution, use "Combine Shapes" to add a small circle on top of one of the teeth, the gear becomes higher resolution. There must be a better way of improving polygon resolution. If anybody knows, then please post an answer below.

in pink box onSpawn:
scene.my.pinkBoxEID = entityID

in blue box postStep:
pinkBox := entityByID(scene.my.pinkBoxEID);
text = pinKbox.text;
pinkBox =""

Save and then open the scene for it to work.

Now I understand. I will change the code...

xFor doesn't apply in this case since you want the output to span multiple steps.

The following will work:

_i := -1;
_raMsg := [];
_n := 0;
_dt := 0.05;
_startTime := 0;

onClick = (e)=>{
text = "";
pinkBox := entityByID(scene.my.pinkBoxEID);
msg := pinkBox.text;
_raMsg = string.str2List(msg);
_n = string.length(_raMsg);
_startTime = sim.time;
_i = 0
};

postStep = (e)=>{
_i > -1 && _i < _n ? {
sim.time - _startTime > _dt ? {
text = text + _raMsg(_i);
_i + 1 == _n ? {_i = -1} : {
_i = _i + 1;
_startTime = sim.time
}
} : {}
} : {}
};

Thanks for the update.

Looks like I will need to block my webcam or put a piece of paper over it.

Nice work. 1 meter H2O = 0.098 bar so 200 m H20 is approximately 20 bar.

See Transmission Hinge.

I concur. Thanks.

I like the scene idea. Algobox has been around for 14 years and this is the first scene that tries to prevent plagiarism by using algoboxID. Correct me if I'm wrong, but this scene assumes that scene.algoboxID gets updated when a scene is posted to Algobox. I'm not sure that's the case. My Rotate 3D Cube,which I copied from Xray, has scene.algoboxID = 48330, which is 3D Box by RBS16.

Here's a couple of ideas that could be implemented by Algobox (but don't hold your breath):
1. Highlight all scenes where scene.algoboxID does not match the Algobox ID. This would highlight possible plagiarisms.
2. Set up a web page where a user can delete possible plagiarisms of their work by being able to delete any scene that has scene.algoboxID = their original Algobox ID.
3. Set up a web page where a user can see possible plagiarisms of their work an request that specific scenes be deleted.

P.S. Modified Rotate 3D Cube so that its Scene.algoboxID = 259159, so it doesn't "appear" that I am a plagiarizer.

1. Save GUI in the "Components" (phunlets) folder.
2. Add the GUI to a new scene. The string functions load with the phunlet and remain with the scene after the phunlet is closed.
3. Add "scene.my.str_" before any string function to use it. For example, scene.my.str_instr("The cat in the hat","cat",false) = [4].

I concur.

This scene was uploaded to Algobox as a phunlet. The scene description starts with "This phunlet ...", so I should have known. If you already have a different scene open, and you download this scene, then the phunlet automatically gets inserted into the original scene. If your original scene has a camera position where this phunlet is not seen, and you don't realize that this scene is a phunlet, then it appears that Algobox has failed to load this scene.

Man by BrAzAs. Walker Bike by s_noonan.

Maze Generation: Algorithm Recap

Looking good.

The birds are my favorite part of the scene.

Q: Is something supposed to happen when clicking the balloon?
A: No, "**Click**" is the sound of the camera shutter.

At first I thought that the stairs should work like the toggle button on top of a pen where each stair could click down on the way down and store the energy in a spring and then click up when the person goes up stairs returning the spring energy to help them up the stairs. I couldn't think of a simple way of doing that. Another approach (based on your comment) would be to make a motor/generator and connect it to a battery where the motor/generator acts like a generator when someone is going down stairs and acts as a motor when someone is going up stairs.

That book is a real page turner.

I agree, but that won't stop me from making another stair scene.

Thanks. Yes, I'm not sure how to handle that problem. Also, there is a problem if a second person follows the first person up or down the stairs. Maybe there needs to be a sensor that detects the direction of the user and presets the stair accordingly.