Algodoo

It's right above the Rating bar graph.

Sorry, but things falling on the ground and smashing into pieces is not satisfying to me. Satisfying is when someone scratches my back. Satisfying is eating a thick, tender, and juicy steak. Satisfying is..... ummmmm..... I'd better stop right here!

Cool! Nicely done.

Crazy4aqua711_v2 -- I agree with you that your marble race was poorly made. So, why post it? Do you want to get a bad reputation among the other marble race fans? I looked through the other scenes that you have posted, and so I know that you can do much better than this! So, my suggestions for future scenes are the following: 1. Take some time to THINK about the kind of marble race that you want to make. Don't just start randomly placing things into a scene just so that you have something to post no matter how poorly made or ugly it is. 2. Take the time to design, build, and test your creation before you post it. 3. Get some ideas from other people's scenes. I'm not suggesting that you copy anyone's scenes, but you can certainly be inspired by them!

I don't want to see you or anyone else fail at being the best that they can be here on Algobox. When you post a good scene that others enjoy, you are contributing to this community, which other users will appreciate.

Another suggestion: I noticed that when I stop the auto-zoom and then restart it a few seconds later, the image makes a "jump" to a different zoom level. That's because you are using sim.time as your timer. When the zoom is stopped, sim-time continues to advance at its normal rate. Then when the zoom is restarted, it jumps to an updated zoom value because that value is always changing even when the zoom motion is stopped. That can be fixed so that the zoom picks up exactly where it was when the zoom gets stopped. Instead of using sim.time as the time base, simply use a timer! Here is the script that I came up with:

scene.my.stopzoom == 1 ? {
_timer = _timer + 0.02;
scene.camera.zoom = sin(_timer * 0.2) ^ 2 * 55 + 17;
scene.camera.pan = [cos(_timer * 0.2) ^ 2 * 4.0 + 4, 0.0]
} : {
scene.my.zoomvalue = scene.camera.zoom;
scene.my.panvalue = scene.camera.pan
}

You also need to initialize the timer each time the scene gets loaded by placing the following script in onSpawn: _timer = 0

Try this and see if you like it.
Oh, by the way, you can adjust the zoom in and out speed by changing the value which gets added to the timer in this script line: _timer = _timer + 0.02;
The value 0.02 seemed about right to me, but you might decide to change it.

Yeah, so? It does exactly what you made it do.

Of course it's free! We don't allow anyone to make a profit on their scenes.

sus amongus? Okay, if you say so!

odd thing:

quister

high senstus

I like that orange slice! YUM

My vise is not my vice.

Yes, this truly is a cool vise. It's kind of ugly but quite functional.

Nice work on the scene.

I've done that more than once, and it's an easy mistake to make, even for super-smart people like you and me.

Okay, if you say so!

I bet you also like my multi-megawatt Cesium-137 RADAR system. It will cook your Pop-Tarts before you can say, "Pass the butter capacitor please".

Great explanation, JP! Your scenes are not only educational, but they are also quite entertaining!

Here's another one you might like: ASCII Girl Dancer

Here's one I was planning on doing but never did. Be my guest if you would like to tackle it as an Algodoo scene: Einstein's Equivalence Principle.

If I were going to do it, I would show a ragdoll man standing in a rocket (with no windows) in deep space (micro gravity). The rocket would accelerate at 9.8 M/S^2 (same as gravity acceleration on Earth). While accelerating, the man would not know if he was in space accelerating in a rocket, or if he was standing in a stationary rocket on the ground here on Earth. I think that would be a great science lesson!

If you decide to make such a scene, then I will not. If you do not, then I might do it within the next couple of years.

Thanks dsfops. At least you can speak English, unlike that other kid whose ball got yeeted.

Should be: "Double Slit Experiment"

Except for the typo's, nicely done!

Wow, awesome scene, and great scripting!

When people don't understand something, they seem to automatically assume that it's caused by magic or by Aliens. That's because of our superstitious nature.

This scene was posted in 2016 and the user Scientific Accuracy stopped posting stuff in 2017, so you will likely not get an answer from him.

Works great! Good job!

JP - I have a couple of suggestions which you may want to consider:

1. The blob in the moving rocket should be at a constant acceleration (same as gravity). Therefore, the velocity should be continuously increasing over time (similar to a falling object). Remember, the formula for the acceleration of gravity here on Earth is approximately: v = 9.8m/s^2 (don't forget the ^2)
2. I struggled somewhat with my own version of this scene, and that's why I have not posted it. It's difficult to show a person or object at rest on the Earth while at the same time show a person or object accelerating in a rocket! In order to show the person in the accelerating rocket, the "Follow" function must be turned on (I used the "rocket" structure to follow, and I turned on the y vs x plot which shows the increasing velocity over time). I did that in your scene, but after a few seconds of travel, the rocket started to spin, and then the velocity took on a sinusoidal pattern! So, there are some issues there to work on.
3. Remember that most of the people who use and love Algodoo are young kids. So, we try to be somewhat simple in our scientific explanations of the scene while still trying to remain technically accurate. Sometimes that's hard to do!

Yes, area value for a box does not update. So if you need to use the area in a calculation, you will have to use size(0) * size(1). I know its annoying, but at lease that will work. As far as I know, Algodoo will not be updated, at least in the foreseeable future.

WAIT! I just noticed something strange happening. When I downloaded your scene, and changed the size of your box, the area did not change. BUT when I opened either a new scene or one of my older scenes, the area of a box changes normally like it should when I change its size! So, something strange my be going on with YOUR computer or your setup. One thing you can try is to RESET Algodoo. With Algodoo launched, click on the little gear icon. Then you will see a tab labeled "Reset". Click on that to reset Algodoo to see if that corrects the issue. This original scene my still be corrupted from before the reset, so try creating a new scene with a box to see if that issue is still there.

I subscribe to EVERY scene that I leave a comment on. That way I'll be automatically notified when anyone else leaves a comment. I probably subscribed to hundreds of scenes over the past 8 or 9 years!

Yeah, it freezes with me too. I think the problem is those thousands of "stars" that you created. Algodoo has trouble handling so many of them. It would be better to delete most of them and just leave a few. Then Algodoo will load and save much faster. Scenes that have a lot of water in them are very slow loading too.

Just a side note. This kind of scene cannot be stamped out in one day. In order to do it right, it would probably end up taking me a week or two of my spare time of designing, testing, and debugging the scene. I already spent a few hours on my version of it, and it's still far from "finished". I just lost interest in it, so that's why I suggested it to you. If it turns out to be too difficult or it takes too much of your time, I'll try working on it again. Let me know. Thanks!

So, did you try resetting ALgodoo as I mentioned above?

It does weird things because you set the axle motor speed to infinity (+inf). That is an invalid value which causes the glitch. Here is how to prevent that from ever happening again: Don't set the speed of a motor to +inf!

That's a toilet??? I would never use a toilet that looks like that no matter how badly I needed to go!

What did Pig do to deserve such a horrific punishment? Did he call your red marble a name Like "blue" or something awful like that?