Phun User - You need to give more information than just "Stole my wheels". In order for me to confirm if what you are claiming is true, you need to provide YOUR scene title that you claim he stole from you. Then I will decide what to do about it.
Okay, I found your scene, and I compared your wheels with the wheels in this scene. I don't believe they are the same. There are similarities, but there are enough differences that I cannot say for certain that he copied your wheels. If he did, then he made quite a few changes to them. Anyhow, I wouldn't worry about it. The world isn't going to come to an end because someone copied your wheels! Just don't worry about it. Okay?
There are a lot of users who want to become an Admin, but they are either too young or too immature and they lack good judgment. Besides all that, we currently don't need any more Admins. But that could change down the road. Are you at least 18 years old? I doubt that Algoryx would allow anyone under 18 to be an Admin.
The problem is the "NAN" values in the axles that make up the chain that holds the lamp. NAN means "Not A Number". Thyme will sometimes put NAN in variables that have not been preloaded with a valid number. Select each axle and click on the script menu. In the script menu you will see bendConstant = NAN. Click on NAN and change the value to any large number such as 999999. Do that in all four axles and your glitch will magically go away!
EDIT: Also change legacyMode from 1 to 0. If you do not do that, then the chain will be very stiff and will not act like a chain.
Those are variables that are used by the Thyme scripting language, and they determine how the axles (also called hinges) behave under certain conditions. You do not need to know the details of how those variable are used unless you plan to learn Thyme scripting.
First of all, Algodoo is not a "game". It is a physics simulation program. You can make games with it (like I have), and you can make a lot of really cool simulations with it. But it is not a game.
Secondly, I agree that all of the "algi-whatever-thons" and camps, and marble races are a big pain in the (you know what). Algobox has been taken over by a large group of toddlers and young children, but Emanuel is working on some changes that hopefully will improve this situation. If his changes end up doing little or nothing to fix this situation, then I will probably leave it also. So, I say stick around and give his changes a chance to see if things will improve. I don't know when these changes will be finished, but I sure do hope it will be very soon!
Oh, and those blue circles in your scene are not "water". They are just blue circles, and you made them to behave like they do. So, it's not "Glitchy strange water", it's something that YOU made!
Please stop posting so many scenes in such a short time period. Take the time to do a good job and make scenes that people will enjoy playing. No one likes your "dumb ways to fail" scenes, and in fact, some people are complaining about them. Do not post more than 3 scenes per day.
@s_noonan - I assume that you are referring to the transparent background (not translucent). Algodoo does it automatically, and so it's very easy to do! You just need to have a png or gif image with a solid background color that you (the user) defines as transparent.
For anyone not knowing the difference, "transparent" means that it passes light in varying intensity, and it passes clearly defined images. "translucent" means that it passes light in varying intensity, but it does not pass clearly defined images. Translucent material typically has a "milky" appearance (clouds are translucent), while transparent material is clear glass or plastic that you can see through and make out images.
Oh, sorry. I shouldn't presume that everyone knows what I'm talking about when I convey a fact. I use Google Images for nearly all of my textures in my Algodoo scenes. Some of the images can be directly copied and pasted directly in the scene, and others need some pre-processing from my image editing program, PaintShop Pro. It is probably similar to Lunapic, but not sure. For Google Images that have solid white backgrounds (must be png or gif (not jpg)) I can click on the image to select it, and then press Ctl-C (copy). I then open Algodoo, and place the cursor where I want the image to be pasted, and then I press Ctl-V (paste). If the image has the correct solid color background, then Algodoo automatically tries to create a polygon of the image with the background removed. That's the part that I stated was automatic. If the polygon looks too ragged or chopped up, you can select it and press Ctl-Z, and Algodoo will undo the polygon that it made and the image will become a box with a texture, including the unmodified background.
If all this still doesn't make sense, maybe it would help if I posted a scene that actually shows the various steps of the process. Let me know....
MoBuilds, Hey thanks for those suggestions for other simulation websites! I had no idea they existed because I was always very happy with Algodoo, and so I had no reason for looking for anything else. But, as everyone knows, things happen and changes occur! If the "improvements" being worked on prove to be well below my expectations, then there's a good chance that I might take my interests to other websites. Time will tell....
I noticed that the drive wheel sits in one spot and jitters even when no torque is applied. I think there's a problem in your control algorithm, although I don't know what it is. If I were doing a similar scene, I would use a simple proportional control scheme (the "P" in "PID"). I might add a bit of derivative ("D") if it needed to be stabilized during accel/decal. And in place of the load cell, I would use a spring to monitor the pulling force from the hand. Just some ideas for ya!
Oh yeah, the old NAN (Not A Number) issue! If Emil were still updating Algodoo I would suggest to him to preload those variables with sensible values instead of garbage (NAN). But unfortunately, it doesn't look like Algodoo will ever get updated again.