Algodoo

Jon_joy_1999 - Thanks for the info. I have that bug fixed already, but before I update the scene, I'm going to put it through the wringer and make sure that the scoring system is correct for all situations (strikes, spares, and open frames) before I update it. I should have it completed in a day or two.

EDIT - Scoring now FIXED!

For what it's worth, I prefer using the scroll wheel for aiming because it feels more realistic, and I have much better control for aiming.

Nice start for a great future game!

Where did you learn that mouseover trick? Is there a tutorial in the forum?

Oh, Okay! Maybe that's what you stated above, but I cannot read cyrillic.

Nice Ragdoll!

Very confusing to program.

Can it handle hardware interrupts?

Show me a real bow that can shoot an arrow 1430 meters, and I'll BUY it!

SWEET!

Angle is in units of Radians, not degrees. The scene seems to work, but it's not flipping heads and tails every 180 degrees as you probably thought it would, based on your code.

Stick an axle in the middle of your coin, and make it rotate slowly. You will see that the coin doesn't flip every 180 degrees. If you want to use degrees, the conversion is Deg = Rads * 180/pi.

This works:
{
angle > math.pi ? {scene.my.tails = 1} : {};
angle > 0 ? {scene.my.tails = 0} : {};
1.0
}

Since there are 2pi radians in 360 degrees, this flips each time the angle changes positive and negative with each rotation.

actually, this is simpler and it works just as well:
{
angle < 0 ? {scene.my.tails = 1} : {};
angle > 0 ? {scene.my.tails = 0} : {};
1.0
}

It works because in Algodoo, a complete rotation goes from zero to +pi (3.14) in the first 180 degrees, and -pi (-3.14) in the second 180 degrees, back to zero. So, you only need to check if the angle is positive or negative in order to make something happen twice per rotation!

EDIT: After thinking about it, I realized that the script can be made even simpler!

{
angle < 0 ? {scene.my.tails = 1} : {scene.my.tails = 0};
1.0
}

Only one toss? Why not make it so that it tosses each time T is pressed? That way, a person can test its statistics to see if it's a fair coin toss!

EDIT: Maybe even provide heads/tails counters? (that would be a great feature in my wonderful opinion! )

@s_noonan - TOUCHE'!

I'll make a counter and get it uploaded as soon as I have Thyme.


EDIT -- NEW VERSION HAS BEEN UPLOADED!

Nice job!

jon_joy_1999 -- Thanks for the kudos! I also wish that my real life undo function worked so I could undo my first marriage.

And of course we all would like to be able to undo that tragic school shooting.

and the point of this scene is...... ??????

It's a little shakey and difficult to control, but with a little more work, I'm sure you can improve it.

I see that you still use Phun. Why not upgrade to Algodoo?

Nice job! I have a suggestion which would make the drawing easier to view. Select all of the vertical and horizontal beams that currently block the drawing and make them transparent with the "A" slider in the "Appearance" selection of the pull-down menu. Also uncheck the "borders" check boxes. After doing that, the drawing will be completely clear except for the circle and the tracer that draws the pattern.

Mechanically, it moves very smoothly. Again, nice job.

s_noonan - The coin OnHitByLaser generates a script that gets placed in the ControllerAcc variable. That script starts running, which toggles the heads and tails. That toggling of the heads and tails is done this way:
The texture image is a picture of a both sides of a U.S. Nickel (they are side-by-side, right next to each other). The image changes by SHIFTING the X position of the image in the textureMatrix. For a few milliseconds, the heads image shows, then the X-position changes so that the Tails image then shows for a few milliseconds, and the sequence repeats until the coin collides with a wall. The OnCollide code sticks a constant (11.0) in the ControllerAcc variable which overwrites the script that was originally put there by the OnHitByLaser code. With the script that toggles the coin image now gone, the image stays on either heads or tails depending on what was showing when the collision took place. That's it!

Kilinich - Check out my Polygon Raster Scanner scene. I added a little code to your scene to make a simple raster scanner. It just shows that you can use your scene to make many other things just by using the output of your code that detects the polygon surface to do other things. FUN STUFF!

Kilinich - Yes, I realized how slow it is when I implemented my scanner scene. I would like to do my own version of the scanner with faster code, but I do not know how to do it. Any suggestions from you, my Russian comrade, would be greatly appreciated.

s_noonan - That's only true if the person using the scanner is already messed up in the head.

s_noonan - I'm glad that I was able to pass a technique along to someone else. Have fun with it!

EXCELLENT JOB! THIS IS AWESOME!

Just wondering where you store the steps? I haven't found it yet.

EDIT -- I think I found it... "scene.my.angleList" Right?

I don't get it.

Thingy??? LOL

So, is that what it's like to be drunk?

Luezma - Thanks!

One suggestion with efficiency in mind. I noticed that your code continues storing steps even while no commands are being given. In the real world, that would be a waste of memory, and would make the program data files unnecessarily large. My suggestion is to store steps only when any of the motion keys is being pressed. Just a gut feeling that this would not be too difficult to do. If you have no interest in doing this, I would be happy to work on it myself because this is a truly awesome scene. In my opinion it is your best work!

Kilinich has stated publicly more than once that Algodoo is his hobby. So even if he decided to program games as a professional, I suspect that he will always remain here with Algodoo as his hobby.