Algodoo

No, I made this scene as an example for another user but it has too many flaws to be very useful.

Sorry

Eight ate eighty eight eights before eating eight PI's and then he became irrational.

Little - It's an interesting engine, but (as I'm sure you'll agree) is very finicky. If I even THINK to load it down, it stalls. And then when I try to start it again the whole thing bursts into a googol number of Algodoo pieces, and they all disappear! LOL It's an interesting concept, but not very practical. But, hey.... maybe with some elbow grease and time, it will work!

Suggestion: In the "update" method of any object place the following script:

app.gui.playMode = sim.running

Why: Because the control keys (W,S,A,D and others) change the cursor from a simple pointing finger to whatever tools those keys stand for. For example, after I pressed the S key to zoom, the cursor became the placement pointer for the spring tool. So every time I wanted to click on something to select it, a spring was placed in the scene! Very annoying. That script will fix that issue by forcing the scene to go in and out of play mode dependent on if sim is running or not.

Except for that, the scene is pretty cool!

The eyes don't just fall, they explode! Cool!

Suggestion: Before you save the scene on your device, zoom the scene in or out and center the main objects on the screen. Then when you save the scene, that final placement of objects will be the image that shows in the thumbnail image on Algobox. Your current thumbnail image is nothing but a GREEN background because that's what was showing during the time you saved the scene on your device. A solid green background image is not very exciting!

Cool!

Nicely done. It's very pretty!

OUCH! Kevin and his brother should find a safer job.

Nice job on making the perspective correct!
.
.
.
.
.

perspective: The art of drawing solid objects on a two-dimensional surface so as to give the right impression of their height, width, depth, and position in relation to each other when viewed from a particular point.
"a perspective drawing"

Ummm... what exactly are we supposed to do?

Wow, whatvaheck, I had no idea that you were so handsome!

¡Los gatos no saben nadar!

Okay, I'm waiting. What's up bro?

Nicely done!


With Homer gone who's going to save the Springfield nuclear power plant next time it goes critical?

What exactly are you testing?

So?

Get an oil change.

I have an old ThinkJet lap-top running Win-XP. It still runs older versions of some popular apps but when I download the newer versions, it can't handle it and just freezes! I hate to just toss it out, so I let my grandkids play with it.

@Temmie -- The reason why those red circles spawn where they do is because you do not tell Algodoo where to spawn the circles, and so it automatically defaults to pos[0.0,0.0]. You can make the circles spawn at the point of collisions by adding pos := e.pos to the script. The actual script should look like the following:

(e)=>{
e.other.materialName == "fire" ? {
scene.addCircle({
radius = 0.3;
colorHSVA = [1, 1, 1, 1];
timeToLive = 0.4;
pos := e.pos
})
} : {}
}

Warning: The original way that you wrote the script caused the circles to spawn a huge number of red circles that spawned even more circles! That caused computer lag and crashing. So, change the script in each black circle as shown above AND give each one the materialName = "fire". By making these changes the scene will no longer cause lag and/or crashes!

Thanks everyone.

s_noonan -- Yes, I like to think so, but I also smoked cigarettes during the late '60s and early '70s when it was fashionable and publicly acceptable. I was smart enough to quit when my wife was pregnant (1971) and since then I have become a vocal (and sometimes obnoxious) anti-smoking advocate.

Very well stated, Little!

@AngryBirdAlgodoo -- If your computer is smoking I think you should call the Fire Department!

Empty scene.

I made some awesome Algodoo scenes bc I'm bored!

Thanks!

Nicely done! Perfectly smooth and precise action.

Thanks Little! I appreciate your comments.

I understand what you are saying. This issue of copying other people's scenes has been a real headache for me ever since I took on the responsibility of Algobox admin back in 2014. Because of the fact that scenes and parts of scenes get copied and republished nearly every day, it's almost impossible for me to determine who is the original author of a scene or parts of a scene. A few years ago, a user sent me a report that someone copied the wheels from his car and used them in their own scene. After I warned the guy for copying someone else's work without permission, I later found out that the person who complained, copied the wheels from someone else's scene! After that experience I decided I will no longer waste my time trying to track down who was the original author of scenes or scene components. I have better things to do with my time! Also, most people who use Algobox are under the incorrect assumption that if you simply write "Credit to username" then it's Okay to copy and publish their work. WRONG! I tell people if you want to copy and then publish another person's work, you must first ASK THEM PERMISSION to do so. Only then if they give you permission to use their work, you can then write "Credit goes to (username) for the wheels" or whatever was copied.

Here's anther thing that many people don't know because they didn't read the Algobox TOS (Terms of service). Everything that users upload to Algobox becomes the property of Algoryx (the company that created Algodoo and the Algobox website). So, nothing that you post actually belongs to you. Everyone who registers an account on Algobox must agree to the TOS if they want to use the website.