It all depends on the shape, density, and surface area of the objects in your scene, and whether or not you want to simulate air friction acting on the motion of the objects. For scenes in which it doesn't need or make sense to consider air friction (for example, a mechanical device), simply give AirFrictionMult a value of zero. OR, you can turn off Air Friction by clicking the Air Friction icon at the bottom of the Algodoo screen next to gravity.
Leafy and bubble could not possibly have been born at the same time because time is relative to each observer. Because of that fact, there is no possible way to know anything for certain. We can only "guesstimate" the time of any causal event happening and we can only approximate the velocity of a moving object. If the object is accelerating then we are totally lost in the dark (literally AND figuratively!).
You need only ONE exclamation point to show that you are excited about the subject at hand. Typing a long string of extra exclamation points doesn't make the subject any more exciting, but it does show the fact that you were probably sleeping in class when your teacher was explaining basic English sentence structure!
noiq -- That's partially true. It depends on what the leaderboard is showing. For example if a leaderboard in a scene starts out with all contestants at zero, and then keeps score each time the scene runs for a new race, that is perfectly acceptable. But if a person displays a leaderboard as "RESULTS" scores of a previous race, then that would be considered an announcement which is NOT allowed. Results scenes will be deleted and the user will be banned for 10 days. Then if he/she posts another "Results" leaderboard again, the user will be banned forever.
The leaderboard in THIS scene looks to me like the Results of some other race, and so user Leaderboard must delete this scene and if he/she wants to they can repost the scene WIHOUT that leaderboard. If this scene isn't removed within one day, then I will remove it with a warning.
@Leaderboard -- Writing "Credit to the creators" in a comment is meaningless. Here is the correct way to deal with scenes or parts of scenes that you copied from another person: 1. First of all, you should ASK PERMISSION to copy and upload work that someone else has created. 2. Only after getting written permission to use their work, you can then write IN THE SCENE DESCRIPTION as an example: "Credit to user "whoever" for the red athletes". If you do not get permission to reupload someone else's work, then DON'T USE IT! Just use your own work.
It sounds like you need to learn the basics of how to use Algodoo. At the top of any Algobox page you will see a tab labeled "Learn it". Click on that tab and read the simple lessons. If there is anything that you still don't understand after reading those lessons, then contact me in comments and I will try my best to explain it to you.
Just curious, did you copy this scene from someone else?
If you made everything in this scene, how did you know how to write the script? The script looks like it was written by someone with a lot of experience. Be honest, did you really create everything in this scene including the script?
This is interesting and impressive, but doesn't the Algodoo "Combine Shapes" tool essentially do the same thing? It may take an extra step or two, but no Thyme script is required.
While the scene is Paused, I cannot read your tutorial instructions because you forced the PAN and ZOOM to be at fixed values and therefore I cannot move to read the instructions. If you want the camera to zero in on a fixed position and ZOOM value you should place that script in "PostStep" instead of in "Update".
Except for that, you did a great job on the scene!
Q: Angle slicing might also be applied to thermal FEA or to exploding objects.
A: Wow! Those subjects (especially thermal FEA) are way outside my area of understanding! But, I think it's very cool and impressive that someone (like you) can figure out how to code Thyme Script in order to make those things a reality in Algodoo. WAY COOL!
I found the code but it was too easy for me, so I won't claim it.
Suggestion for any future scenes with text... Your text in that special code box is white text over a yellow color which is very difficult to read. If you do something like that again, the text will show up better if the color of the text is different from the color of the box that the text is on. For example, black text on a white or yellow box is easy to read.
In case you didn't know this, you can EDIT the scene title. Just click on "Edit", then correct the spelling "Stay" instead of "Stat". Then click the "Submit" button. That's it!
2. Your Algodoo app may have been corrupted by one of the scenes that changes water settings (it happened to me too!). You can fix it by resetting Algodoo. To do that, launch Algodoo (it doesn't matter which scene you load), then click on the little white gear next to "File". That will get you into the Settings screen. Then click on the tab labeled "Reset" and follow the directions. Algodoo will shut down. Then when you launch it again, the problem with water should be fixed.
I inserted the example disk (letters and numbers) as explained in the scene, but it doesn't work. After pressing different keys, nothing shows on the display.
Hey, this is awesome! There's only one issue that I noticed immediately because I tried it with one of my scenes that was made with multiple layers. Ctrl-A selects only items on the current layer. Do I need to select each layer individually, or is there a way to have the tool select all items on all layers at the same time?
I got it to work now. The problem that I had before is, when I pressed the "D" key (pull in disk) it took a long time to pull the disk in, so I thought that it wasn't doing anything.
One other issue that you may want to address is, when I picked up the alphabet and numbers disk in order to insert it into the computer, it accidentally bumped into the blank disk and sent it flying away! Maybe make it easier to insert and remove disks? One suggestion would be to orient the disks in the correct position while they are stored. That way the user won't need to rotate them in order to insert them.
One more thing... Push (D) and pull (F) keys are "toggled" which means that after pressing one of those keys they remain in the same state, making it impossible for the other key to function. The fix would be to automatically disable each function when the push or pull task is completed.