Algodoo

42flowermaster -- Okay, NP!

Maybe the confusion lies in the definitions of global vs local variables. A global variable is one that's shared by all objects in the scene, and begin with "scene.my". Any object can write or read a global variable. A local variable is one that can only be accessed within a single object. Local variables that you want saved with the scene begin with the underscore character (such as _var1). There are some exceptions to these rules but that would require more complex coding techniques. All variables, local and global, must be defined before they can be used. If not defined, the error message "undefined" will be displayed when an attempt to use them is made.

Wow, nice job on the scene! You obviously put a lot of time and energy into making it.


Suggestion: Maybe as an Easter Egg (or whatever) you can stick an image of Voyager1 at the outer boundary of the known Universe.

Good idea UDG04! I made the circle rotate with a very simple script in "angle" as follows:

{
sim.time * 2
}

You can change the rotation rate by changing the multiplier value.

Even at max zoom-out it's really difficult to navigate such a huge scene that has stuff spread out over such a large area. So, I'm sad to report that I was not able to find any item that you may have added to the scene in my honor. But I do thank you for the honor in any case.

Thanks!

I was wondering if anyone would figure out the obvious "secret" to winning round 3. Well, here it is: Just wait until the pendulum's arc is short enough or comes to a full stop before launching the balls so that it won't interfere with them! It's not cheating because there are no rules that state you may not do that, and the game doesn't prevent you from doing that.


But if you insist on doing it the hard way, yes it's possible to time the launching of the balls so that the pendulum swings in between them. It's very difficult but it's possible with practice and with some luck.

T_Reißig -- No, the counter should not start counting before any balls start falling into the bucket.

The only thing I can think of that might cause that is if you messed around with the game while in the scene "edit" mode and accidentally did something to corrupt the game. If you did, then I would suggest downloading a fresh copy of the game and try it again.

Thanks for playing!

Algodoo water can also be stacked!

Stacked Water

What's the point of this?

Thanks Cool_S

"A working black hole". Funny!

Cool galaxy but there are no clouds in space! You can disable the clouds by right click on the background. Then in the background panel that shows, uncheck the "Draw Clouds" checkbox. Then save the edited scene and use it to edit the uploaded scene on Algobox.

Good job on the scene overall!

I have a suggestion that I found was helpful to me: When the Drag tool is showing, there's a panel that shows that allows the user to select various configurations of the tool. One of them is "Disable Rotation". If you check that checkbox, then the paddle will be easier to move around without it rotating. Of course, if you want the game to be harder to play, then leave that checkbox unchecked!

@AndyHappyGuy -- Nice job on the scene! All the ships look great but I was wondering why you put those long spikes on them.

Also, what is the giant rectangle used for? It just falls on top of the spikes when I run the scene.

Physics A -- This scene seems to work Okay for me, so can you give me an example of an actual script that I can test?

Great idea! After I played around with your scene, all kinds of ideas for different ways of doing a programmable drone swarm swarmed my brain!


Merry Christmas!

Um... "vel == 10 ?" is not a Boolean logic expression. The example you gave is checking "vel" to find out if the numeric value in vel is equal to 10. An example of a Boolean logic expression is "var1 && var2 ? {do this if true}:{do this if false}"

Is there something in THIS scene that doesn't work for you? If you can be specific about which lines of code don't seem to be working, then I should be able to figure out what's going on.

Well, then I cannot help you. No one else has reported similar issues, and so it must be caused by something related to your computer. It's also possible that your Algodoo app was corrupted some way, so you can try to uninstall it from your computer and then install a fresh copy of it from the Algodoo website.

Good luck!

Try this....

Go into the edit menu of any object in your scene.
Define a local variable by entering it into the text entry window in the upper-left corner as follows: _temp = 0.0. After doing that you should see the variable show up in the list of variables on the left side of the edit menu. Then add the following script to the upDate event between the existing curly brackets: _temp = math.vec.len(vel) Then in the vel text box change whatever value is showing to: [1.0,1.0]. DO NOT RUN THE SIM. After entering the X and Y values of 1.0 for the velocity, the resulting value in _temp should be 1.4142135 (which is the square root of 2). If that's what you see then the function math.vec.len(vel) is working correctly.

Actually, the value in attraction DOES change but it doesn't update the displayed value in the list of variables. I know this is weird, but some of the variables in the list update constantly and others only update when you put your cursor on the value and click it!

Try this: Create a local variable by typing this in the text window in the upper-left corner of the circle's script menu: _test = 0
You should see "_test" show up in the variable list. Then add _test to your script in postStep. It should look like this: _test = attraction = math.vec.len(vel)

When you run the simulation and drag the circle around, the value in _test should update constantly, but the value in attraction will not update. Attraction WILL change as it's value changes but you just won't see it change in the variables list.

Yes, exactly!

Most cats do not like getting wet, but this kitty seems to be Okay with it as long as he/she has some ducks to eat..... um..... I mean play with!

Nice job on the scene!

By the way, you CAN see the attraction value continuously updating if you view it in the "Material" panel. To get there, right click on the circle, then move your cursor down to "Material". Another panel will open that has the Attraction value continuously displayed as it changes. If the value changes while you move the circle around, then the script is functioning correctly.

I checked your scene just as you coded it and it updates the attraction value as expected. So, I don't know why it may not be working for you.

Nicely done!

Wow, this is an amazing cat who can swim with only one arm and no legs!

I don't think you can place emoji's in your comments if you use the Algodoo built-in browser because it is very limited. You would have much more control and capabilities if you use a standard Internet browser such as Chrome or FireFox for things like uploading and downloading scenes, and for posting comments.

Use this script instead:

angle = math.atan2(app.mousePos(1) - pos(1), app.mousePos(0) - pos(0))

Rather than calculating angle off no reference [0.0,0.0] the angle gets calculated off the current position of the circle. The circle then can be located anywhere you desire (even while moving!).

YW!

Billy Mays died in 2009. That's the year Algodoo and Algobox were launched, and it was a time before many kids who use Algodoo were born!

Thanks,

Yes, I tried many different ways (without cheating) to get a higher score than 16 but I was not able to. Maybe some fast-fingered young gamer could find a way!

On the other end of the scale, you can (theoretically) reach -inf by moving rivets into different holes, but that might get a little boring after the first 10 or 12 years of playing.