SamBoy8,
This scene can be improved and it won't cause lag like it currently does. Here's how:
1. In the orange box that sits on top of the larger green box, uncheck the box for collision layer "A". Then nothing will collide with it, and people will then be able to drop text boxes down on top of it and they will hit the green box from above.
2. In the script for the green box, add this code:
e.other.collideset = 2;
directly after the first line that reads:
App.GUI.Showmessage("I think it says ''" + e.other.text + "''");
3. Disable the clouds because they serve no purpose in this type of scene.
4. Add the following instructions: "Pick up a text box and drop it down on top of the large green box. The text will then be revealed"
NOTE: The scene will no longer lag no matter how long the text is displayed because it will only be displayed one time instead of hundreds of times like it was before. Any questions or problems, just leave a comment for me.
I don't know if you are using a standard Internet browser, or if you use the Algodoo built-in browser for uploading and downloading scenes (scenes are the things that you call a "map"). Also, I don't know the exact procedure that you use for downloading scenes. I have not received any other complaints from people concerning the problem that you are having, and so I tend to think that there is something that you are not doing correctly rather than a "glitch" in the software.
The only thing that I can suggest for you to do is to try loading scenes with a standard browser (like firefox or chrome) if you are using the Algodoo built-in browser for loading scenes. That Algodoo browser is old and has many problems which will never be fixed.
Then what anniversary are you celebrating? By the way, you cannot have a "month anniversary" because the word anniversary relates to an annual (yearly) event.
Sorry, ThingExtreme, but I no longer investigate complaints of stealing scenes or parts of scenes. As you can imagine, scenes get copied and uploaded every day here on Algobox, and it's nearly impossible to prove who the original maker of a scene or part of a scene actually is. For example, you cannot prove that you did not copy the lava or the lava script from someone else. That's the kind of thing that I often come up against, and it can be very frustrating for me. So rather than to waste my time tracking down who the original maker of a scene is, I just don't bother with it any more and I suggest the following: If you believe that someone copied and uploaded your work, then contact that person via the comments section and tell them that you believe the scene or part of the scene was originally made by you and that you ask that they either delete it, or to give you credit for it. If they either ignore your request or tell you to "bug off!", then there's nothing more that you can do. We want to avoid any verbal attacks or war of words here on Algobox which might get YOU into trouble if Rules get violated. I hope that you understand and appreciate my situation in regards to this issue.
I had to look at the user name multiple times because I couldn't believe that the real s_noonan uploaded this scene! What I mean is, this scene deviates enormously from the usual accurate and precise very technical scenes that Engineer s_noonan typically posts here on Algobox. Let us hope that this deviation from the norm is transient!
About 20 years ago I was playing around with a strip (about 5.0cm long) of Nitinol and a cup of boiling water. I coiled up the Nitinol and dropped it into the boiling water. The Nitinol expanded so quickly that it shot out of the water and across the room. I never did find it!
vinimed,
I don't think anything having to do with Algodoo or Algobox is broken because if it was, I would have been getting complaints from a lot of other people but I am not. The problem is likely something that you are not doing correctly, OR there is a problem with your computer, your Internet access, or with whatever software that you are using. I cannot help you any more than that. Sorry....
Nice job on the excavator, but I have a suggestion for you. There are no "limits" on the motion of any parts of the machine. For example, if you hold the key down which rotates the bucket, it continues to wrap around without stopping, which often breaks or destroys something. In a real machine, every hydraulic action has a limit which prevents the machine component from moving beyond its safe limits.
You, of course, do not have to make those changes just because I suggested them. The decision is totally up to you if you want to do that or not.
It doesn't matter to me because I am not worried about it. Some people get so wrapped up in trying to predict if or when certain events are going to happen, but that's not what we should be doing. I have faith in the Almighty, and that's the most important thing, as far as I am concerned.
As much as I would like to continue with this type of discussion, I really should not go any further. Algodoo is not a platform for promoting or for discussing religion, politics, or other such topics in which people have extremely divergent views and opinions. It would not be proper for me to discuss subjects that I have warned others about discussing in the past. It appears that you and I have similar views and beliefs about religion, and let's just leave it there.
I don't understand why you would want the bucket or any other part of the machine to "rotate all the way, and flip around". It would be more realistic for each hydraulically controlled item to simply stop moving when it is up against its forward or reverse limit. That can be done in a number of ways as follows:
1. You can place a hard stop (such as a small box) at the end of travel for each direction. Just keep in mind that doing it that way can sometimes result in erratic behavior. Things might violently shake when the item bumps up against the stop in either direction.
2. You can monitor the rotational angle of the actuator (the motor or axle) and make the script stop motion when the angle gets to or past a specific number.
3. You can place a box at each limit with script in the onCollide section that stops further rotation when the collision occurs.
I looked at your list of scenes, and I see that the last scene you posted was two years ago! You have made many really awesome scenes, and it would be great if you could find the time to make and post more scenes in the not-too-distant future.