Algodoo

Yes, animated gears are friction-less and have no interference. Perfect real gears are friction-less too, since the teeth have pure rolling contact when meshed perfectly.

Nice work.

How to make a perfectly circular track.
1. Make a straight track.
2. Select all the hinges.
3. Set bend = true, bendConstant = 1000.0, bendTarget = 0, and motorTorque = 1000.0 for all hinges.
4. Apply some torque to the free end of of the chain (using 2 thrusters or a motor with a low hingeConstant value).
5. Start the scene. The chain will curve with a radius inversely proportional to the applied torque.

See Cantilever Beam, Large Deflection for an example.

P.S. I tried the procedure above and the response is too slow.

Thanks.

Nice work. Regarding sound, see AlgoSound (Algodoo Sound) on YouTube.

Thanks.

Q: Does this work with Mac?
A: Most likely, but I have not tried it on a Mac. I wrote AlgoSound in (2) programming languages; vbSript and Python. VBScript works on Windows. Python works in Windows and should also work on a Mac. The only thing with Python is you need to download and install Python, pygame, numpy, and gtts. See AlgoSound for details.

Faytree,

Thanks. As you know, it's very difficult to get anything to run at high RPM without destroying itself of causing excessive lag, so I cheated a little.

JakubKubo,

Read the comments on your cockpit scene.

You asked me to check out your rolling numbers. I assume they are on the altimeter. They don't work. I don't see any numbers. I don't see any code to change the texture matrix in the number boxes. I don't see any response or scene changes regarding my previous response.

I do now.

Two things I don't understand:
1. How did you figure out that you could use vecs := _X; in addPolygon?
2. What is forcing the new polygons into position?

Looks like all the indicators are working OK.

Looks good. Excellent scene. Some spelling errors[difgital, subary, poen]. 1245/100,000 kg should probably be 1245/1,000 kg. Looks like I won't have any excuses for making junky cars anymore (other than I'm lazy, my shoes untied, the sun was in my eyes, I need to floss my cat ...).

Statement: I think that I can remove that "/100,000kg" text because it is not so important here.
Response: I wasn't referring to the importance or capacity. I thought the value was wrong. If 1.0t = 1000 kg then 1245kg/(1000kg/t) = 1.245t. Now I see that 100,000 is the scale capacity and not an indication of the scale units.

Q: Could you make a car following that? Post it as response!
A: I will most likely do that.

Q: Do you think I should make TUTORIAL series?
A: Yes.

Q: Was this form good?
A: Yes. You could get rid of the clouds. I find them distracting.

P.S. Just before "Unpause for the first time", you should instruct the user to select the whole car and select "no self collision", otherwise the wheels may collide with the fender skirts.

The best way to save money on a car, besides not having one at all, is to drive a clunker. There are several advantages to having a clunker:

1. You won't lose much to depreciation.
2. You usually can buy the car with cash, so you don't have to pay interest on a loan.
3. Insurance costs are less, because you don't need collision insurance.
4. Your car taxes will be much lower than a new car.
5. You don't have to worry about getting dents.
6. You can be king of the road, since nobody in their right mind is going to try to cut you off.
7. You don't have to wash the car.
8. Some clunkers also have the advantage of being fuel efficient. My car has 299,334 miles on it and gets 35 mpg.
9. The environmental toll of car production per mile is reduced the longer you keep the car on the road. It is estimated that production of a car contributes 10 to 20 percent of its total lifetime CO2 emissions.
10. It's easy to find repair parts.
11. Mechanics are less apt to overcharge you, since they may feel sorry for you or be hesitant to give you a bill that's many times the car's worth.

Thanks.

My grandsons really enjoyed this scene. They each took turns and did it a couple times. The next day, they turned on the computer, found the scene (I had it stored locally), and played it again.

Q: How did you put video in description?
A: Click on the help hyperlink at he bottom of this page next to the "Add reply" button.

Yes, well done. This should be helpful to users learning how to script.

Nice work. I like the quantity, but not the color, of the smoke. The green smoke looks toxic. Also, in some cases, the smoke shows up in front of the car. The driver of the car needs to stop looking for his phone that dropped on the floor. For visual effects that are not accuracy dependent, I sometimes use the update() event handler, since it always runs at 60 Hz, regardless of the sim.frequency value. I'm giving this scene a 10, even with those minor criticisms, to offset the down-rating that somebody gave you.

xFor := (n1, n2, code)=>{
n2 > n1 ? {
m := (n1 + n2) / 2;
xFor(n1, m, code);
xFor(m + 1, n2, code)
} : {code(n1)}
};

Regarding "update event runs even when scene is paused, that's why I don't like to use it, and DEPENT on sim.frequency too":

update := (e)=>{
sim.running ? {put code in here}:{}
};

update does not depend on sim.frequency.

Regarding xFor, you don't need to know how it works, you just need to know how to use it. You can search for xFor in the Algodoo forum. It works just like the for loop where "code" = "(i)=>{}" so in use it looks like this: xFor(n1,n2,(i)=>{code goes in here}). Kilinich is the one who invented xFor.

Even though I used red capital letters, I was not angry, I just figured since you used caps, I had to go one level higher.

P.S. Looks like xFor doesn't handle negative counts, so you will need to do positive counts and do subtraction in the code. I've used scene.my.xFor, _xFor, and xFor depending on the desired scope. See Polygon Modifier for an example of xFor and _xFor usage.

Q: Is that how you intended this to work?
A: No then yes. I initially wasn't thinking of that but wanted to give the user the ability to push and pull the knobs. When I saw that you could preload all the knobs except one trigger knob, I though that that was something kids might enjoy discovering and also thought that it may allow a different way of playing the puzzle. You could play the puzzle by clicking all the knobs except the trigger knob and then set it off with the click of one knob. If you hit the trigger knob prematurely, then you didn't solve the puzzle. In normal use, if the user makes a mistake, then he can just click the knob a second time.

1. Download Python and verify it is working.
2. Download the correct version of PyGame for your OS.
3. Use Python to install pygame, numpy, and gtts. Using Python to install the other programs puts the programs in the right location on your PC.
4. pyAlgoSound_05.py has import statements that automatically link the other programs to it. You can open pyAlgoSound_05.py with a text editor and see the import statements at the beginning of the program. pyAlgoSound_05.py must be running while running the AlgoSound test scene.

Statement: I'm not suggesting that either one is better or worse than the other.
Response: Your way is better. It gives the user a choice of reading or not reading the instructions. It also gives the user a chance to read the instructions after they try to do it without instructions and fail.

I purposely left the instructions somewhat vague because I wanted kids to explore the mechanism and discover how it works. Also I'm lazy.

Thanks guys.

Xray,

Thanks for the suggestion. I did make a random color generator that excluded pairs that used directly opposed knobs. It would sometimes fail if the last pair selected turned out to be an opposed pair. It also failed to check for repeat combinations. Your idea is good and solves the problem. The only issue I see is that the puzzles would come from a limited set. In reality, that wouldn't be much of a limitation, because the set could be made large enough where people get bored, figure out the shortcut to solving the puzzle, or forget the initial puzzles, before completing the set.

Nicely done. I like the minimum file size, minimum code, and minimum processor load. Your design is elegant.

This subject was already addressed in the forum. Your method is fairly concise but "for" has an upper limit that will break on larger arrays.

How do I change gears?