Algodoo

A little sarcasm is Okay. Just don't over-do it.

Great! It works perfectly!

When Algodoo loads a scene, it defaults to layer-0 (zero). Your gun components are on layer-1, and so a user is unable to work the action unless they understand (like I do) that they need to switch to layer-1. I doubt that the kids, or new users, know how to do that.

I was just bored, so I wrote this comment.

Thanks, s_noonan! I appreciate your critique of my scenes.

Especially our illustrious President.

That would be true if he wasn't mentally unstable, extremely narcissistic, a pathological liar, and a childish bully.

Are you old enough to vote, JohnG?

I could spend hours proving to you that Trump is not fit to be President, but this is not the right place to do it. And so I will not discuss this any further. Thanks for your comments and opinions.

Xray out....

Your building and roads would look more natural (realistic 3D) if you had created them using proper perspective. If you don't know what perspective is, take a look at this video: Drawing in perspective After learning the basics of perspective, you might decide to make a few changes to your scene which would make it look much better! This is a common mistake that MOST Algodoo users make when attempting to create "3D" structures on a 2D display.

AMROfficalLime -- Thanks for the suggestions, but I don't plan to make any changes to it. Sorry...

Those cute little guys are setting a good example by wearing masks during this current pandemic!

No, wild bill is no longer an Admin and he does not plan on coming back as an Admin. He does occasionally post awesome scenes here on Algobox. Currently, I am the only Admin on Algobox.

Those names in the list in the scene are:

Xray : Me
私は日本です : I have no idea who that is.
Emanuel : He is an Algoryx employee and does all the fixes and updates to the Algodoo website. He is my "boss".
lucia : I have no idea who that is.
Dare : I think that has something to do with drugs?
electronic boy : He is an Admin located in the U.K. but is currently not active.
Algoryx : The name of the company that owns this website.
Kilinich : He is an Admin located in Russia, but is currently not active.
Paradigm 29 : I believe he is still an Admin but he hasn't been active in over 10 years.
tatt61880 : He is an Admin located in Japan, but is no longer active.

True, this strange behavior of Algodoo water is weird, but it's nothing new. We have known about this for many years, and many other people have uploaded scenes that show this odd behavior.

Nice job on the scene. I especially like how you slowed down the scene speed when the circles are close to their lowest point in the curve.

Questions: According to the Wiki page that you linked to in the scene description, the curve is defined as: "...the curve for which the time taken by an object sliding without friction in uniform gravity to its lowest point...". Not to be critical, but I just wanted to point out that the four circles in the scene have a frictional constant of 0.5, and the curved structure also has a frictional constant of 0.5. Should they all be changed to zero?

Also, I noticed that the circles in the scene are "rolling" and not "sliding" along the curve. I confirmed that by monitoring the circle's angle values while they were moving. Should that also be corrected?

Edit: OOPS! I just realized this scene was posted back in 2014! As a rule, I normally don't critique such older scenes. Sorry...

reeee -- When I press Run, nothing happens and nothing moves. What's wrong?

I'm using the latest version of Algodoo, which is the same version you use.

It's impossible for any of the circles to move because they are all glued to the background! I don't understand how they move when YOU play the scene.

in your comment above, you said: "i played and everyone files of the corners." What do you mean by "files of the corners"? Sorry, but that makes no sense.

I got bored, and I somehow wrote this comment.

Nice improvements you made!

You can get rid of the score and the lives displaying "undefined" when the scene is first loaded by initializing those variables each time the scene gets loaded. You do that in "onSpawn". An example would be:

onSpawn = (e)=> { scene.my._MRB = 0; scene.my._PAC = 1}

Because those are global (scene.my) variables, you can initialize them in ANY object. Local variables (those variables which begin with an underscore, such as _var) must be initialized within the object where they are stored and used. The underscore character that you use in global variables is not necessary.

Hope this helps.

Hamster300 -- Did you ASK Dmoney1300 for PERMISSION to copy and upload his city? If you did not, then you should not use his work in your own scene. GIVING CREDIT IS NOT THE SAME THING AS ASKING PERMISSION. Giving credit means nothing if you don't get another person's permission. Remember that.

If you respond to this comment and tell me that you did not get Dmoney1300's permission to use his city, then I will delete this scene. If you do not respond to this comment by tomorrow, then I will delete this scene.

READ THE RULES!

XxxMrAlgodoo123 -- Thanks!

As a suggestion for you, users of your scenes should never have to do that list of things that you are asking me to do. If circles are glued to the background because of a mistake that YOU made, then YOU should be the one to correct that mistake and re-upload the corrected scene. If everyone who tried to play your scene had to unglue stuff from the background, then very few people would want to play it!

I noticed that when I click the RUN button, all the particles that are inside of the planes, just disappear! I don't know where they go, but they do not move in the game. I don't understand why it is working for you. A good test would be for you to DOWNLOAD a copy of your scene from Algobox and try to run it. Then maybe you will see that it does not work.

reeee -- I think I figured out what is happening to your scene. All of those circles that are located inside of the planes will collide with the planes as soon as you click RUN. In your onCollide script, the timeToLive in each circle will go to zero very quickly because the radius of the circle is being tested against the radius of the plane, but planes do not have a radius!

You need to get those circles out of the planes and make them move some other way. Then that should fix the problem.

You: "Would it be possible to gather free energy from the atmosphere in the future?"

Me: Unless someone has a crystal ball that can see into the future, there is no way to know that.

You: "This model is not realistic..."

Me: Of course not. It was made using Algodoo after all!

You: " I'm sure there is a problem somewhere with this model, but where is it?"

Me: I'm no expert, but I see at least three potential problems with it. They are: 1. In real life, air does not behave like your randomly bouncing circles. Well, actually I think it does, but only on a tiny molecular level. 2. The amount of energy transferred from each circle to the paddles, regardless of the coefficient of restitution number, would be the same on each side. Kinetic energy is: (MV^2)/2 which would give a net energy transfer of zero for each paddle blade. 3. The paddle is freely rotating which means all of the wind energy goes into simply rotating the paddle (mostly back and forth). If you were to tax the power by putting a load on the paddle (such as a generator or water pump, etc) the system would probably not turn at all, or would turn very slowly, generating extremely small amount of power, which would be totally useless.

I like vanilla cake with chocolate frosting.

Cool animation!

Score still shows "undefined" when the scene gets loaded.

Clever way to demonstrate math functions!

Jannik -- Your calculator works much better now. Good job!

It still has a few minor issues that I found. They are:

1. You have two AC buttons. One clears the numbers to the left of the operand, and the other clears the numbers to the right. In every calculator that I have used, they have only one AC button which clears everything.

2. Divide by zero gives a result of "+inf". Most real calculators will show either "NAN" or "Invalid" or "Error".

3. The result should not be displayed until the "=" is pressed.

4. There is no decimal point button for entering decimal values, and no +/- button for entering negative values.

5. When entering large values ( > 10 digits) the displayed value changes to some random weird value. (I see that you already know about this issue).

As I mentioned in an earlier comment, these issues that I found are totally up to you which ones (if any) that you want to correct. A four function calculator is not a simple programming task, even for a person with a lot of coding experience. You certainly have done a great job of it so far!

The train never gets moving because the engine car crashes as soon as I click on RUN.

Mastamastas1111 -- No. But you should have a copy of it on your computer. If you do not, then you will just have to try to resurrect it from scratch (without the cuss words, of course, if you later decide to upload it to Algobox).

By the way, In your "RIP" scene, you said: "Mods who don't know how to read a disclamer..." What did you mean by that?

Mastamastas1111 -- Do you REALLY think just because you post a "disclaimer" that it's Okay to use cuss words in your scene? If you do, then your thinking is perverted. And I don't care if it took you 10 years to make a scene. If you put cuss words in it, then it WILL get deleted. That might "suck", but that's the rules.