Algodoo

Okay, now the scene works as expected.

BTW - The flickering when both A and D keys are held down is caused by Algodoo attempting to determine which tool the user wants to select. You can stop that flickering by putting the scene in "play" mode when running. Add the following script in upDate of any object:

app.gui.playmode = sim.running

Oh yes, now I see what you are talking about. It doesn't happen very often for me, maybe once every 3 to 5 times I change inputs. It flickers after going from on to off state. I tried different sim frequencies, but that did not make any difference. Just a gut feeling that the flicker is caused by the relatively complex logic and math calculations that you do for the xor logic. The other gates are much simpler and therefore less likely to hiccup. I wouldn't be too concerned about it because this is just an educational scene. If those gates were controlling the trigger circuitry of a nuclear weapon, then I would be just a tad more concerned about it.

It flickers occasionally for me when I press either the A or D key by itself. I think it's caused by the propagation delay of the signal through the logic and math routines, which is causing erratic timing. It seems overly complex for a basic xor gate.


If you slow the "Simulation Speed" down to 0.5 then the flickering becomes more obvious.

Bruh, i mean like the oof is sus even when they yeet a dude. It be like ya know when they oof the dude an coz him to be like ya know woke. Every black hole is sus! Ya wit me bruh?

!?

While playing around with this more than five years later, I discovered that I can drop more than six red and black discs ( <4 each color in a row) in any column which messes up the game (just like it would in the real life version). I'm letting you know this in case you did not realize it, and if you care about making the game more idiot-proof. If not, then just ignore this comment.

That's a hullova hull maker!

All kidding aside, it's easy to use and works flawlessly.

No, Algodoo is not being updated. That happens every April Fools Day.

Actually, it requires no "AI" at all. Just some basic logic and array manipulation.

Instead of a "destroyable" Big Ben, why not make a clock that actually works and tells time accurately? You CAN do that, right?

I don't pretend to understand mechanical engineering as a discipline but I do try to educate myself when I happen to discover an interesting mechanism that intrigues me. Linkages are one of those mechanisms that not only intrigues me but fascinates me! So, while surfing the Web for interesting information on mechanical linkages, I found this chapter of an on-line book titled "Fundamentals of Design" by Alexander Slocum: Linkages . There's a lot of interesting information in that book concerning mechanical linkages which I believe even a person with a passing interest would find captivating.


Here's an idea of mine which I think would be useful to demonstrate how a linkage becomes progressively defective over time especially if not properly maintained (periodically cleaned and lubricated). You can show how the "slop" or backlash affects the accuracy of the process that the linkage is connected to. Maybe show the difference of a lissajous pattern made by a new, close tolerance linkage compared to a pattern made by a worn "sloppy" linkage.

Good job on the scene (as usual)!

s_noonan.... You referenced the wrong scene for WezorX. It was actually a comment for your scene titled "Motor Power".

14724 downloads in less than 2 months? Holy cow! That must be a record here on Algobox!

Oh. Okay.

It reminds me of how I get when I'm hungry!

Nice job!

Square marbles? Now that's interesting!

ezpz(fib)5 -- As I've said many times before, it's very difficult for me to determine who stole what from whom here on Algobox because there is so much of that happening. For example, if someone reports one of your scenes because you stole their blue marble, I have no way to determine whether or not the person reporting stole that blue marble from someone else! I won't waste my time by spending hours trying to find out who originally made that blue marble!

So, in other words.... GO FOR IT!

An Allegory.

bilalniazi31 -- You were banned twice. Once for posting a personal message in a scene, and then again for posting a "Results" scene. Each time was for 10 days. After the 10 day bans your account was no longer banned. That's why you can do things now.

Cool!

I see you discovered "groovyON".

I think I see a possible "issue" here (sorry, Faytree). I ran the simulation many times, and occasionally (more often than not) one of those super long springs would make contact with the timer, stopping it well before the car's body actually reaches it. It may make a difference of only a few milliseconds, but that might be enough to win over someone else's car.

In any case, good job!

You can hide the outline of those gears by doing this: Right click on a gear, then hover your cursor over the word "Appearance". When another panel opens, uncheck the check box labeled "draw borders". Then save the scene on your computer. When ready, you can edit your posted scene on Algobox by uploading the scene that you edited on your computer. Now the outline of the gears will not show in your scene!

I'm not "bruh", I'm Xray. Yes, it's the flag of Ukraine. Do you now understand the allegory? If you don't know what an allegory is, then Google it.

I assume this is not a playable scene because when I click the Run button, it all falls apart. Is it your intention to make a playable game out of it?

Cool!

I was confused about that too, Little. Maybe instructions that explain all three of your AHOX computers in one location would be a good idea, especially if the intent is to use them together (as you described above). Just a suggestion.

Thanks!

Yeah, I am too.

idk why i made this comment.

It took you 45 seconds to make this? WHAT TOOK YOU SO LONG?