Overall, you did a nice job on this gun. And now here comes the "BUT".....
it has a tendency to jam a lot, and in different situations. For example, the first time I fired it in semi-auto mode, the bolt slid forward into battery, but the round did not discharge. After poking around various things with my grab tool, it finally fired after I put forward pressure on the bolt. In full-auto mode, it jammed again after firing a couple of rounds. Occasionally, the ejected cases would fall back down onto the open bolt, and will cause the gun to jam when the bolt closes onto the case.
When the gun is behaving itself, it works quite well. And so it probably just needs a little TLC or "fine tuning".
Just so you know, we currently have around 5 or 6 people listed as Admins, but there are only 2 or 3 of them, including me, who are still active. I'm not sure about the exact number because one of them is in college, and because of his study schedule, he no longer has time to handle the duties of an Admin.
All of the Admins are "technical" people. In other words, they do not make and post childish scenes like marbles and "camp' scenes. They usually post complex mechanical scenes that demonstrate the capabilities of Algodoo. We also use a lot of Thyme scripting in or scenes. Unfortunately for you, I look at your scene history, and the only scenes that you've made were childish camp scenes. So, if you want to gain respect from me and other Admins, I suggest that you start making and posting dynamic technical scenes. You can see many examples of technical scenes by looking through the Algobox archives. There are tens of thousands of scenes in the archives. Some are very good and some are really pretty bad. But it will give you a good idea of the kinds of scenes besides childish camp scenes that people can make.
You have same IP address as "pen ben". You do know that we do not allow more than one user name per person, right? If pen ben belongs to you, then we will have to ban that name or your other name kirill#1. So, please explain why you have two user names.
No problem. I figured you deleted it because you wanted to make a change to it or maybe it wasn't working as you intended it to. Anyhow, my comment stated that I am very impressed by how strong the track is. It's no doubt the strongest and most robust track on Algobox.
I also said that I did some experimenting with it, and found that I was able to delete both gears and the supporting beam, and the track still ran just fine all by itself! I did need to increase its mass quite a lot, and I made the friction infinite on all of the track segments. It was brilliant of you to use "materialVelocity" to propel the track, and the "textureMatrix" to give the image the appearance of motion. I can't recall if anyone has done that before. Good job!
It sounds like you don't really want to be an Admin. If you were truly serious about it, then you would immediately stop making camp scenes and color voting scenes, and you would focus on whatever you needed to do to prepare yourself for the position. But since those children's scenes are more important to you, then I hope that you will continue to enjoy making and posting them.
Yes, and unfortunately it happens a lot. It usually happens after I warn someone about their bad behavior (such as, if they post profanity) and then they ignore my warning and they do the same bad behavior again. So, I always give people at least one chance to correct their behavior before banning them. Most bans are only a few days.
s_noonan,
I did everything as instructed in the scene, but no sound.
I'm running Windows-7 64 bit OS.
UPDATE: Now it works! Here's why it did not work the first time I tried it. After I executed the .bat file in the sounds directory, the Command window opened as it should. But then I closed the Command window, because I thought that it was not necessary to leave it open. THAT was my mistake. Now I have someone else to listen to besides my wife.
s_noonan,
Please explain how this is any better (it certainly is more complex) than just using keysIsDown() by itself in each of the three control boxes? I don't get it.
s_noonan,
I think JakubKubo was asking how to lock out the shortcut keys in order to prevent them from being active. And of course the answer to that would be, by placing: app.gui.playMode = sim.running in any update event.
1. Instead of placing script in each laser, you only need one simple line of script in the circle which will achieve the same result:
onHitByLaser = (e)=>{Color = e.laser.Color}
A rule of thumb: The fewer lines of code needed to complete a task, the faster and more efficiently the program will run, and the easier it will be to maintain (find and fix bugs).
2. Disable the Algodoo clouds. If clouds are not necessary, or if it simply makes no sense to display clouds, then it's better to disable them. When clouds float by in a scene which is demonstrating a mechanical device, they only create confusion or cause distraction.
I hope you find these suggestions helpful and I hope they are a learning experience for you!
There is one thing that confused me at first until I realized what it was. You say, "Press INTRO to lift up the mirror", but most keyboards (at least here in the U.S.) do not have an INTRO key. They all have either an ENTER key or a RETURN key which does the same thing as the INTRO key.