Oh, and by the way, Copsicle, message scenes ARE allowed under most circumstances now (yes, rules have changed since last year). Message
scenes are Okay to post in the following conditions:
1. To alert other users that you will be gone from Algobox for some period of time.
2. To alert other users that you are back, so that you can continue with activities.
3. To alert other users of special events (use this one sparingly).
The type of message scenes that are NOT allowed are:
1. A message directed to another specific user (in other words, do not use Algobox like a chat room).
2. For publicize your political or personal opinions on a subject.
3. To sell something or a request to buy something.
4. In general, do not use Algobox like Facebook or Twitter.
Thanks, tomski! That was done though the magic of Thyme Scripting. Scripting gives you much more power to do things with your scenes which cannot easily be done with mechanical things like revolving lasers, gears, and spinners.
If you are interested, I suggest that you learn some of the basic commands, and over time you will learn more advanced techniques. Nearly all of my scenes were made with Thyme scripting because I love to program, and this is a fun way to do it!
tomski -- In case you did not know this, the collision layers are not limited to letters A through J (ten layers), but actually you can have 1023 layers! You do that by setting "collideSet" in the script menu to any integer between 1 and 1023. So, for example if you set collideSet = 3, then collision layers A and B will be enabled (their checkboxes will automatically be checked). It's Okay to enable more than one collision layer at a time in this type of animation process because it does not rely on actual collisions, only hitByLaser. Experiment with collideSet and you will see that your animations can have a lot more frames than you thought they can have!
How many do you want? It's almost limitless. But of course if you load too many frames into memory, they might cause a lot of computer lag, and no one likes computer lag!
MegaGate164 - Explain what "ADWT" is, and why it's different from other scenes that you have uploaded. And my other question is, have you tried to upload any other scenes? If so, did they upload without problems? If not, then you should try it just to see if the problem is that particular AWDT scene or if the problem is with your copy of Algodoo.
Well, I recommend that you start over with your scene, and do not create so many assets and bodies. Try it with, say, half as many, and then see if you can upload it. If other scenes upload without problems, then that is what's happening with your awdt camp scene. You have too many objects in it, and Algodoo just cannot handle it.
earthlycreations -- I don't usually comment on marble race or algocathlon Camp type children's scenes, but this one caught my eye. You put something in your scene that I rarely ever see in this type of scene, and that is a SHADOW! The shadow looks correct. It seems to have the correct proportions and is at a believable angle as if the son was above the person in the image, high in the sky. GREAT JOB! NICELY DONE!
Great idea! Here are a couple of suggestions to improve it....
1. Ungroup the pin from the rest of the assembly so that ONLY the pin gets selected when clicked on.
2. Make the pin/unpin process reversible. I tried to put the gun back together after taking it apart and it was quite difficult because the barrel wants to keep falling down before I had a chance to reset the pin.
Antonton - Please stop using the REPORT link for making nonsense comments. The REPORT link should only be used for REPORTING other users who break the rules (such as when they use profanity in scenes or in comments).
Nice job! I know how difficult it is to make physically accurate 4-leg walkers with Algodoo. In my opinion, the most talented walker-maker on Algobox is user mori-d His dog and horse walker/runner scenes are outstanding. Check them out if you haven't already one so!
Ultragamer564 - When you report another user who uploads your scenes or parts of your scenes, you must be very specific about what it was that they copied. Don't just say things like "He stole from me and didn't give me credit". You need to explain WHAT was copied and also you must provide a link to YOUR scene that was copied. If you don't do that, then I won't be able to help you.
Also, It's always better if you can try to work things out with the other person who copied your stuff, but if that doesn't work, then you can report it.
Stormstar and Ultragamer654 -- I received reports from both of you complaining about the other person was being insulting and was claiming that the other person was presenting fake information. It's my job to keep the peace here on Algobox, and I do whatever is necessary to ensure that happens. I start by warning people, and if that doesn't work, then I sometimes have to resort to banning people. I hope that I won't have to ban anyone here, and so you guys should try your best to stop insulting each other. I will delete the insulting comments, and I hope that's all I will need to do!
The RPM meter reads 100 RPM higher than the RPM of the input shaft. I did a test by attaching a motor/axle to the input shaft (circle) and it confirms the result that I am getting.
Whatever you did corrected that issue but it apparently created a new one! Now the indicator needle bounces (or oscillates) at a rate of about 2 per second between zero and the indicated RPM. It does that regardless of the RPM.
I wonder if a digital readout for this application might be better and less troublesome than the analog meter readout. Just a suggestion.