Algodoo

Hi daniel123cat -- Why is it so important that I see your work? I am the Algodoo admin, which means that I make sure that people follow the rules. I do not judge people's work. Think of me like a police officer for Algobox!

Show me a sample scene that doesn't work and I will try to figure out WHY it doesn't work. I cannot give you an answer simply by what you said in your comment.

Hi by me -- It's really difficult for me to determine why certain scripts don't work simply by you explaining what you did. Nothing jumps right out at me. It would be much better if you could post the actual scene that does not work. That way I can test certain variables to determine WHY they fail. After I figure out why it doesn't work, either you or I can delete the scene so that you can post the working version of it.

MORE: I did notice one error in your "rectangles" script. You show: oncollide = (e)=>{scene.my.motor = true
scene.my.motorSpeed = 26}

You MUST have a semicolon after the word "true" which should separate the two commands. So, it should look like this: oncollide = (e)=>{scene.my.motor = true;
scene.my.motorSpeed = 26}

I don't know if that will fix your problem, but if it doesn't, then I will need to see the entire scene in order to troubleshoot it.

You probably use the Algodoo built-in browser which is very limited. You would see it if you would use a regular Internet browser like FireFox or Chrome, etc.

Oh, that explains it! But in your information header it says: Algodoo v2.1.0 So, was the bridge made with Phun and then transferred to Algodoo?

Sorry, I cannot go by your description. I need to see the actual script in order to troubleshoot it because you are probably leaving out some details that I would need to know. You cannot simply call a dentist on the phone and tell him you have a toothache and expect him to know exactly why. He would tell you to come in so he could examine it. Same thing here.

The brown fox was much quicker than the lazy dog!

Again, without me having the actual script to test I can only guess what might be happening. Obviously there's a problem with "scene.my.polygon". It might contain invalid data. For example, collideSet must be an integer value. It cannot be a bool (true/false) and it cannot be text ("This is text"). For collideSet, A=1, B=2, A and B = 3, etc. So, I suggest that you run your scene until it fails, then look at the data in scene.my.polygon to see what it is. You can do that simply by typing the variable by itself in that data entry area in the upper-left corner of any object. If it shows anything other than an integer, then you will need to figure out WHY the variable is getting stuffed with invalid data.

Good start to a game of some sort!

So now just figure out the rules.

Great! I'm glad that I was able to help you.

Maximum thanks acquired!

Wouldn't it make more sense to use Maxwell's equations for calculating magnetic forces?

Either way, great job on the scene. It's both interesting and educational.

Q: I don't understand Maxwell's equations well enough to apply them to this scene.

A: Well that makes two of us! LOL The last time I had to use Mr. Maxwell's amazing equations was about 20 years ago when I was designing a magnetic translation stage which was used for steering a beam deflection mirror for a high power laser engraving system. Fortunately for me, I had a mathematician on our development team who did all the difficult math for us! I'll just leave it as-is and let someone else smarter than me figure it out.

s_noonan -- How did you make the large circles remain at a fixed radius from the small circles?

Never mind, I figured it out!

Rain? What rain?

I'll answer your second question first: "why does edit mode turn off when I play your scenes?" I force Algodoo to go into PLAY mode while my scene is running so that the cursor remains a DRAG TOOL. If I don't do that, then the cursor might accidentally put boxes or circles in the scene when the left mouse button is pressed. Forcing play mode prevents that from happening. Then it automatically goes back to EDIT mode when the scene is paused. In most of my scenes, the script that makes that happen is: "app.gui.playMode = sim.running". You can delete that script if you don't like the automatic playmode feature.

Concerning your first question: I'm sorry but I have no idea what causes that. If you use the Algodoo built-in browser for uploading and downloading scenes, then that could be causing the problem. I always suggest to people to use a standard Internet browser like Chrome or FireFox instead of that limited Algodoo browser.

I like this upgraded version. GOOD JOB!

Overall, good job on the scene!

Suggestion: Put up and down limits on the gun because when I hold up or down too long, the gun comes around and starts pushing on the ground and lifts the entire tank upside down!

It works perfectly.

I'm curious why you call it a "trunk". Is it because the gun looks like an elephant trunk? Here in the U.S. we call it either a gun or a cannon (a cannon is a very large gun).

No problem, but I don't believe it's deliberate. Google sometimes does a poor job of translating other languages too!

I especially like your barrel stabilization. It works very well.

Suggestion: Not everyone understands what a Nonogram puzzle is (including me), so it would be helpful if you were to print the rules either in the scene or in the scene description.

@by me --- I watched a YT video that I think you will want to watch because you seem to like fans so much.

video on youtube

Możesz napisać po angielsku? (Can you write in English?)

How do you play the game? What must you do to win? What must we avoid? What are the control keys?

Instructions are really necessary for a new game that no one has ever played before!

So, I made this comment becuz I'm still bored.

Thanks, I rely on Google Translate for any other language besides English.

Did you have a chance to watch the video I sent you a link to?

video on youtube

He was explaining why most fan speed control switches are in this order: OFF-HIGH-MEDIUM-LOW rather than OFF-LOW-MEDIUM-HIGH. There is actually an important reason why they designed it that way. The motor that's used in nearly all standard household fans is a brush-less AC synchronous type. It's called synchronous because at normal running speed, the magnetic field synchronizes with the 60 Hertz AC line frequency (50 Hertz in Europe). While the motor is running at full speed it produces maximum mechanical power, but until it reaches that speed, the starting torque is very low and needs some help getting it started, either with an added capacitor or by adding a special winding on the motor field coil. That motor design worked great until someone decided that the fan should have a speed control because no one wants a fan that runs at full speed all the time. So they tried using an incremental switch that went from OFF to LOW-MED-HIGH. The problem they found was the motor would sometimes not start turning when it was switched from OFF to LOW! The user would have to switch to HIGH in order to get the fan to start turning, and then they would turn it down to LOW or MEDIUM. So, some brainy engineer came up with the idea of modifying the switch so that it wen directly to HIGH when switched from OFF. That's why most fan switches are like that! But as the guy stated in the video, modern motors are much better quality than they were 50 years ago, and so that special switch arrangement is no longer necessary but old habits are hard to break!

Sorry for my long-winded answer! LOL

@by me -- See my latest comment in your "Finger Chopper" fan scene.