Algodoo polygon-ghost bug

[faytree]

I make a polygon that has a very thin surface at the middle(it is invisible) and put some water on it.Some of water go trough the thin polygon and others stuck.When i put an object, the object stuck too.
the scene: http://www.algodoo.com/algobox/details.php?id=66217

[jon_joy_1999]

this answer is covered in the FAQ:

The time step in Algodoo is fixed to 1/100 second (100 Hz), so any modeling of real-world physics happening at shorter time scales will be hard to reproduce. Typically this also means that the physics occuring on very short length scales is hard to resolve with this timestep, so we don't recommend sub-centimeter physics at all. This scale limitation also holds for fluids.

[faytree]

this answer is covered in the FAQ:

The time step in Algodoo is fixed to 1/100 second (100 Hz), so any modeling of real-world physics happening at shorter time scales will be hard to reproduce. Typically this also means that the physics occuring on very short length scales is hard to resolve with this timestep, so we don't recommend sub-centimeter physics at all. This scale limitation also holds for fluids.

i don't get it.

[jon_joy_1999]

which parts need explanation?

[Xray]

faytree -- Think of it like an old style film movie projector. Imagine if the frames get displayed at a rate of 100 frames per second (in reality they do not, but this is just for this example). If something happens in the movie at a very fast time period, for example, a bullet fired from a gun. The bullet will leave the muzzle of the gun, fly across the room, and hit its target, but that action happens so fast that it might occur at a time period in between two of the film frames, and therefore would not be seen. So, that FAQ is warning users that any physical action that you create in your scene which is faster than the 100 FPS rate, the action may not actually happen! The limitation of the frame rate is also why when you make a very high speed geometry, it will sometimes fly right through another geometry that would otherwise collide with it if it were going slower. The fast geometry will move past the collision point before the Algodoo software can detect that a collision had occurred!

Algodoo can reproduce some fairly fast actions, but it cannot reproduce VERY fast actions. And it's mainly due to the limitations of the frame rate.

I hope this explanation helps you to understand the problem.

[faytree]

Thanks, .One question , so the thicker the object, the more the frame rate.I mean when the object is thick, it's impossible when a 25m/s circle trying to go trough the object.

[Xray]

Thanks, .One question , so the thicker the object, the more the frame rate.

No. The thickness of objects does not affect the frame rate, The frame rate is constant, and the default is 100 frames per second.

I mean when the object is thick, it's impossible when a 25m/s circle trying to go trough the object.

I'm not sure what you are asking. But if you are asking about a specific object at a specific speed and thckness, I cannot answer that for you because I don't know how to calculate it. Your best bet is to simply TRY it, and if it performs as you expected it to, then you need not worry about the frame rate. If your high speed oject flies right through the other object, then it might be going too fast, and you'll need to slow it down, mke it thicker, or increase its density. Changing those things should help.

[faytree]

now i understand .