1. The score is not consistent. For example, the score updates when the first square of a pair is selected (is it supposed to do that?). Also, when the score is showing 0, it will deduct 6 points the first time a wrong pair is selected, then 5 points, then 4 points.... etc. I think it stops decrementing when the score goes down to 2. It's also inconsistent when a winning pair is selected.
2. When the HINT button is clicked more than once, the game freezes with all squares exposed and it will not recover until the Shuffle button is clicked.
Algodoo is a sophisticated physics simulation program (app) that must calculate position, velocity, and rotation of many objects in a scene. When motions occur rapidly (as they do in your scene) your computer cannot calculate those parameters fast enough, which sometimes causes weird motions or collisions, as what happens in your recent scene. It's not really a "glitch". It's simply due to your computer not being able to keep up with the rapid calculations that Algodoo requires.
Suggestion: Do not create scenes that have rapidly moving objects.
Yes, I was planning on making some of my own enhancements too, but my time is limited until after the holiday. My wife doesn't see the importance of Algodoo like I do!
The shape that the black dot is on should turn green when the shape is outside of the puzzle. When the shape is in its correct position inside the puzzle (the heart) then it will no longer turn green when you click on it. Also, none of the shapes will turn green if Algodoo isn't running, so make sure you click the RUN button (or your keyboard space-bar) before trying to play the game. Hope this helps!
No need to promise! When I make suggestions to improve scenes, I leave it totally up to the scene creators to decide if they want to make the changes or to leave the scenes as they are.
Wow! I felt like I was sitting at a real train crossing when the train came wizzing by! Good job on the scene!
Just a suggestion: It would make it even more realistic if you were to include crossing arms that lower just before the train comes, and then raise when the track is clear and it's safe to drive over them.
1. Please define m, g, and k in the Lspring formula.
2. I found that increasing the Simulation Speed to about 1.75 or 2.0 in both my scene and in yours, makes the scenes a bit more interesting to watch because then I didn't have to wait so long for things to happen and for behaviors to change.
3. In Steve Mould's video he states: "If you get this mass just right and the length of this string just right something weird happens." I'm not certain but I think he actually meant to say: "If you get this mass just right and the length of this spring just right something weird happens." In the first iteration of my scene I did not use a string between the spring and the weight, but I wanted to replicate his scene as accurately as possible in Algodoo and so I put it back in. After experimenting with and without a string ("rope" in Algodoo), it made no difference in the behavior of the spring/weight oscillator (as long as the spring doesn't reach its compressed limit, allowing the rope to go slack for a brief instant).
4. I wasn't able to find anything on the Web that explains WHY a spring/weight combo behaves in the manner described. I think it might have something to do with Chaos Theory, but not sure. Any ideas?
That's close to my highest too. As a matter of fact, I don't believe that it's possible to get much higher than that (without cheating). I didn't design it that way, it just turned out that way.
If you care to enhance or in any other way modify this scene, please be my guest. It has plenty of room for improvement.
materialVelocity in the rope. Also I increased adhesion and attraction in the train so that it sticks to the track. It took a lot of "fiddling" to make it work.
Quote: WHAT. ON. EARTH. IS. THAT. THING. WHERE ARE ITS CLOTHES?!?
Answer: Today, people don't need to be male or female like they did in the olden days. So, the stick-person (I assume that's the "Thing" you were referring to) considers itself as "non-binary". It doesn't need clothes to hide anything because it doesn't have anything to hide!
Nicely done overall, but the game has a behavior (maybe unintended?) that makes the game play slightly odd. That is, I could use one or both of the already played cards to form a match. When I do that, then the last correct pair of cards don't display properly. I checked your original single player game and it allows the same behavior.