Algodoo

It does work differently than mine. Even the up and down arrow keys are reversed, and if I were you, I would HIDE those ugly springs!

Otherwise, good job!

I didn't know about lethalsquirl's suggestion until I saw the comment in s_noonan's metronome. I would have tried it, but s_noonan beat me to it, and I doubt that I could do a better job than he did. I do tend to rely quite heavily on scripting instead of on mechanical physics, and I want to change that. So, I will be doing more scenes with mechanical components and less scripting. A good balance is about 50/50 in my opinion, although many guys would rather do 100 % mechanical.

s_noonan --
I'm currently racking my brain on that 3D bowling game that I did a POC on a while ago. It's extremely challenging because there are so many different parts of the game that must be considered, such as: Handling downed pins, scoring, ball physics, and much more. So, at least for some time, I will not be working on another metronome. And even if I do, you do not need to delete your version. Mine would probably be done quite differently than yours, so I don't feel there would be any conflict at all.

Power loss at high speed? That's the same problem with my 1995 Dodge pickup truck! LOL

If the cursor is far away from the arm when the scene starts, then the mechanism falls apart as soon as the scene is started. It happens when the cursor is BELOW the plane surface.

Just for experiment, I increased the bend constant by an order of magnitude for each axle, and now they are much more responsive. Anyhow, GOOD JOB!

WOW! What an incredible machine! Amazing!!!

There's a little bit of overshoot on the leading edge of the red pulse, so you need to compensate your oscilloscope probe. (he he, just kidding!). NICE JOB on such a complex mechanical device!

When I put my car's gearshift into "Park", the indicator on your speedometer still shows "Drive". Get that fixed!!!

(he he, just kidding!) This speedometer works very well. GOOD JOB!

Your code can be simplified with {scene.my.joy = angle} and it works just as well.

EDIT -- Well, it works with v2.0.2 b15. It may not work with earlier version. Thought I'd better state that!

That's what I would like to do to slow drivers in front of me.

WOW! AWESOME SCENE! COOL!

You can use some help with cutting around texture images. But besides that, cool scene!!

I agree with Kilinich. Upgrade to 2.0.2 b15 and all your troubles with go away! (Well, at least your troubles with Algodoo! )

Hydraulics operate just like real ones. Nicely done!

Kilinich is right. The output of the modulator is the unmodulted oscillator. Also, the output of the phase detector isn't right either. Sorry, Steve, but it appears that this scene needs some fixin'.

Yes, it's working as you described. I was looking to see a much bigger change in the output of the modulator, which I did not see, so I assumed that it wasn't working (I suspect that Kilinich reached the same conclusion). With only 7% FM, the output is very difficult to see visually on the scope. And now I see the PWM waveform on the output of the phase detector. I wasn't expecting that, but it's definitely working! Good job!

In addition to a built-in sound generator, I hope the new Algodoo will allow the use of sound (WAV) files. That will open up a whole new world of possibilities for us!

lethalsquirl - Thanks! Yes, as I mention in my comments, the ball does some funny things at times, but I see that as adding a little extra "challenge" to the game!

s_noonan - Thanks!

faytree - Because the game is "digital" it is very repeatable, which means that if you can find a "sweet spot" starting position for the ball, you can bowl a 300 nearly every time.

Banjerboef - The scoring process for ten-pin bowling is not easily done in software, especially in script types of programs such as Thyme. It is easier to code using other languages that allow calling subroutines and passing arguments, such as C++ and Visual Basic. Thanks for your comments!

Kilinich - If I had made it too easy, then no one would want to play it!
Besides, it's my first version, and I knew that it would need some work to improve it. IF I decide to work on an upgraded version, it will have more features, and I will improve the ball physics so that it translates more naturally. Thanks for your comments!

Interesting scene. Were you planning on making a complete Portals game?

faytree - Sorry, I found a bug that prevents you from getting 300. I fixed it and confirmed that it works correctly. Please try again.

Luezma - DUH! (Crappy comment)

faytree - Good game! My highest is 300, but that's because I know where the sweetspot is, and I can bowl a strike every frame!

Here's a little hint for ya..... After each frame, stop Algodoo, then restart it (in other words, tap your spacebar twice). That way, if you do not knock down the correct number of pins that you wanted to, you can click on the BACK arrow, and the scene will go back to the last time you stopped Algodoo. If you do not do that, then when you click on the BACK arrow, the game will start from the beginning.

Wow, this works better than Viagra!

This is a truly amazing scene! It would be even MORE amazing if you could make it so that it has a selectable horse gait, such as:
1. Walk
2. Trot
3. Canter
4. Gallup

Just a suggestion!

No, faytree.... I'm high on ALGODOO!

@faytree - Thanks for your suggestion. I may go ahead and post it in the forum.

What exactly does this scene do? You give no instructions, so how is anyone supposed to know what keys to press?

I love those funky gears!

I had the same experience. At sim.frequency = 100 (default) the walker flies apart into oblivion. At 500, it walks correctly. This may be because the scene was made with an old version of Algodoo, and we are now using a newer version (just a guess).

That mouseover trick is cool! How did you learn to do that?

EDIT - Thanks for explaining it in the comments section of your Gumby scene.