Algodoo

Yup, pausing the sim when changing attachments seems to work just fine.


This looks to me a bit like a low-resolution version of your "fractal vise".

uygfhjtfvbjihgvcvbhjiuyhgfcxcvbhjkkijg?

Please elaborate, and be more specific about what you are asking.

Wait... If you think of an idea that might work, THEN TRY IT YOURSELF! Please don't suggest things that might or might not work without first experimenting with it yourself. THEN I may be able to help you if you cannot make it work.

I like it. If I were into woodworking I would likely make one, but I happen to be mostly into metalworking as a hobby, and so this type of vise would not be precise and rigid enough for that type of work. It is cool though!

Yes it does! Thamks

Interesting! I also discovered that the AirFrictionMult setting in the circle (or other objects) has similar behavior. For example, if the multiplier in the air control panel (at the bottom of the Algodoo screen) is set to a negative value AND the AirFrictionMult value in the circle is also set negative, then the resulting air friction effect on the object is normal. I also discovered that setting either mult value to a large negative value, the object disappears after moving at some very high velocity! Weird!

What are the control keys? Arrow keys don't seem to do anything.

Also, you say "Try to land on the moon!" So, where is the moon? I see the green planet, but no moon.

WAIT... I think I see the problem. You have TWO versions of this scene stuck together. There is a green planet located at pos [0,0] and another one at pos [1528.0, 1536.0]! Download this scene and see for yourself!

I believe Kirk and other vise manufacturers already use a spherical element against a flat steel jaw in their vises. Even my Chinese mill vise uses that type of design. I believe that it's a better design than a simple lead-screw pushing against a flat steel jaw which tends to cam out of position when applying torque to the vise crank.

It's an overly complex machine, but it gets the job done! Nice work.

It's a triangle. What do YOU think it is?

I like to make stuff doing red things.

No, it won't work with blue things. It has to be red things.

Yes, of course I meant "Kurt". That's what happens when I try to compose a text message when I'm half asleep. LOL

Quote: "An improvement to the whiffletree vise jaw would be to have the elements return to their nominal position when unloaded."

I agree that would be an improvement. Probably can be done with 2 springs on each element that would force them into a center position when unloaded. Another possible improvement might be an over-center cam of some sort that would lock the elements in their loaded position. But that might overly complicate the design. Keep in mind: I'm not an M.E., just a weekend hobbyist, and so some things I suggest may seem silly or impractical to you.

Okay, all kidding aside, here is why those triangle-shaped objects skim across the surface of the plane. The user "greenrid" added a simple script to each triangular object which forces the angle of the object to always be zero. This is the script: angle = 0

When the angle of an object is forced to be a certain value, it will always try to remain in that orientation no matter how much external force is applied to it. The triangular shaped objects in this scene will always attempt to remain standing on their pointed end of the triangle shape because that's what the script is forcing them to do. BUT they are not perfectly upright. They are leaning to the left or to the right slightly. Because they are leaning, Algodoo attempts to return them to the position that the script is forcing them to (in this case it's zero). Each time they rotate slightly because of gravity pulling them in the direction they are leaning, Algodoo attempts to bring them back to the zero angle point. This battle of lean-correct, lean-correct, lean-correct, happens very quickly, many times per seconds, and that oscillating motion is what causes the object to appear like it's skimming across the surface of the plane.

That is what I believe is happening.

This AK works flawlessly and smoothly. Good job!

Are you sure that you took care of the things I mentioned earlier? The WASD keys control a tiny rocket (a white circle) which is very far away from the planet and moon. In fact it is near the other planet in your scene which is at origin [0,0]. It is not near the planet that has 4 lasers. Did you see that you have TWO planets and TWO moons in this scene?

TIP: Each time I upload a scene to Algobox, I immediately download the same scene and test it just to make sure I didn't miss something. I don't believe you did that, because if you did, you would see the problem that I am seeing. There is something weird in this scene which I don't think you see!

Okay, I can understand that. But (yup, there's still a but) the tiny circle you call a rocket, which is controlled with WASD keys, is SOOOOOOOOOOOO far away from the planet with the lasers that a user cannot possibly see what he/she is controlling. The scene starts with the planet/lasers and the moon being displayed in the center of the screen but the rocket is no where in sight. That's because it is located way over next to the planet that you call the scale model. Was that intentional?

Working car (no engine XD).

Notice anything worng? Yes, you misspelled the word "wrong".

I say it counts. Anyhow, I don't see anything wrong in your scene. It is nothing but a rectangle box that slowly falls down to the plane and then disappears. Nothing unusual.

That's really silly because such a simple scene wouldn't fool anyone, even the children who play marble races can see what you did!

Instead of posting silly nonsense scenes like this one, why not spend some time on a really good scene that other people would enjoy playing? I think you can do much better than this one!

We already know about this glitch. Someone reported it a couple of weeks ago.

It also has to do with the "sim frequency". If set too low, objects will not always collide with each other especially if they are moving relatively fast. If set too high, the overall execution speed of the scene will bog down, especially if there are a lot of objects in the scene, and if the computer has a slow processor. The default sim frequency of 60Hz is about right for most scenes and computer types.

This is cool! I don't understand much about neural networks, but I do understand delay lines (I made a delay line scene here on Algobox a few years ago).

Nice job.


Delay Line Memory

I have one question for you: osdhfeuiohffh?

It's not really a motor simulation. Just a spinning disc that continues to rotate due to angular momentum. I removed the "magnets" and the motor continued to spin.

QD -- Deedatski is correct. When you force the circle's angle to always be 0 (zero) or any other value, it cannot rotate no matter what other things bump into it. When the circle is free to rotate, the attached laser will rotate along with it at the same rate.

That's odd because if I hold the circle still with the grab tool and then let it go, it does not start to spin. In a real motor the armature has to be commutated. That is, the magnetic force has to alternate very rapidly to make the motor spin. By having both magnets the exact same value and polarity, it cannot work as a motor. I think that you might have accidentally bumped the circle to make it start to spin.

Anyhow, it's your scene and you can do what you want to it. I am only making a suggestion which you can learn from if you want to.

QD - Now you're not making any sense. WHAT bullet are you talking about? All I see is a circle and a laser.

Look man.... If you want help from people you have to give us clear, concise, and accurate details. We cannot help you when you say things that don't make sense.

Okay, now I think I understand what you want. Just to confirm, you want the laser to point in the same direction that the circle will move in after it collides with an object. Is that right?