Algodoo

???????????????

Comment: "Spend a few extra bucks and buy a better hang glider."
Response: Contact Google customer service with your suggestions.

Comment: "The first time I see a dog use the Hang Gliding."
Response: Really? You must live in a cave!

mlgdash -- I figured out how to unglue a box from the background for you. Look for my scene titled "Loosen Fixate" which I recently posted.

Cheers!

Xray

1. There are no instructions of how to start/stop the motor and how to change speed.

2. It's not good programming practice to write data to a variable from two different locations. For example, you show "text = scene.my.attract3" in "PostStep" and in "update" within a geometry. That could cause conflicting data. Hint: "PostStep" executes code only when the scene is in RUN mode. "update" executes code when scene is in RUN or PAUSE. Do not put code in "update" unless you have a very good reason for doing so!

Other than those suggestions, you did a great job on the scene!

You: "I was just afraid of getting banned for uploading stuff too many times."

Me: You will not get banned for EDITING a scene many times! You may edit a scene a hundred times if needed. What will get a person banned for a few days is if they post more than 3 individual scenes in one day.

Also, I'll take a look at your script to see what the problem is, and I'll respond here after I figure it out.

UPDATE: Okay, here's the problem. In your code:
text = scene.my.attract1, the value located in the variable scene.my.attract1 is not in the correct format. In order to display text, the value must be in TEXT format, and not just a numeric value. You can do that by adding quotes to the code, which forces the text display to correctly display the data that's in the variable. So, you need to change the code to: text = "" + scene.my.attract1. When the text function sees the double quotes, it then assumes that the value in the associated variable is text and not simply a numeric value. Do the same with scene.my.attract2 and 3.

One more thing. By enabling both lasers, you run into the same problem that I mentioned earlier. That is, you are forcing the code to write different values to the same variables at the same time which is not recommended. By doing that, the scene might run erratically or may possibly freeze up. Besides, it doesn't make sense to try to run a rotating device in two different directions at the same time. Instead of telling users to delete a laser to change direction, why not just tell them to press the i instead of the u, or vice versa!

Hope this helps.

mlgdash -- Hmmmm... If you want all of the script to be in the laser, then I'm not sure if it can be done that way. I'll take another look at it, but no promises. You might have to "take it or leave it as-is".

Oh well.... We are not programming ICBM's with nuclear warheads, and so a little messy code is no big deal!

why

Comment (not finished yet)

He's Russian.

Nice job!

Shift key does not detach the face plate.

That's just a lazy way to fix a problem! The best way to fix it is to make it work the way it states in the scene description. You can do that by right-clicking on the face plate, then hover down to "Control". Slide over to the words "Destroy Key" and left click on it. Then press the SHIFT key. Now save the scene and upload it as an EDITED scene. The Shift key will then make the face plate disappear. Easy Peasy!

Your instructions state: "If you try to overwind, the weight will be deleted."
Well, that's really a silly way to make a clock! You went through the trouble of making those complex gears and escapement, now you should put that same kind of effort into making the clock work like a REAL one (weights don't disappear if you over-wind the spring in a real clock). Here's how to fix it. In those blue rectangles you made that kill the weights during a collision, remove the check mark from the "Killer" check box. Then, in the axle which runs the spring winding mechanism change the motor torque from 400 to 330. Make these same changes for both the time and the chime winding mechanisms. Upload the edited scene to Algobox. Now you won't need to worry about over-winding and the weights disappearing. They will simply stop moving when they hit those blue rectangles.

Yup, it works perfectly. Good job!

Okay, it's your scene, so you can do what you want with it. I only make suggestions.

I was bored so I left this comment.

Unity.... I already banned that user.

No, comments are not the proper place to report things. To report a scene that breaks the rules, use the "Report" link at the top right corner of the scene you are reporting, and to report a comment (such as cussing or threatening another user) then use the blue paper and yellow pencil symbol in the top right corner of the comment that you are reporting.

Thanks for your help. I appreciate it.

Unity.... I made a mistake when I told you how to report a comment. The symbol that I described is for EDITING your own comment. It's not for reporting. The symbol to click on to report a comment is the yellow triangle with "!" in the middle of it. Sorry about that. I was tired and half-asleep when I tried to explain it to you earlier. LOL

Who is "Brilliance"? I checked and that user name has not posted any scenes or comments here on Algobox, so how are you communicating with that person?

Yep, that and the insanity that our childish and corrupt President is causing in our government. It's all very exhausting.

Nice job on the scene! It's really fun to play around with.

I made it that way!

Thanks

Thanks, Cat....


and Merry Christmas to you too, wild bill!

Before Emil Emerfeldt (he was the inventor and lead software engineer for Algodoo) left the company (Algoryx) he made some final updates to the latest version of Algodoo, and I was hoping that he would add the one feature that most of us who use Thyme scripting have a need for, and that is being able to write to a single array element. But I guess he did not have the time to do that. There is a simple way to do it if you are working with a simple array with very few elements in it. But if you have a very large array, and want to randomly read and write values to any element, then currently we have to use one of the workarounds (as described in the Algodoo Forum) that some smart users have come up with.

So, who did you copy this from?

why why why why

Epic? Really?

shkshskadkswerwgsb

I posted this for you a long time ago, and then I deleted it because I thought you had seen it. Well, I undeleted it for you now, so let me know if it is what you were looking for.....
For UDG04