Algodoo

Hello!

In case you are curious, the reason this happens is because of something called Floating Point Precision. Computers have limited precision with decimal numbers -- think of it like having a number that's limited to 10 digits.

Each digit can be any digit from 0 to 9 and you can place a decimal point wherever -- but 10 digits is all you get!

Of course, that would work for small numbers, such as 2.500000000.

But what about larger numbers?

Let's try 999999999.0. We only have 1 digit for fractions.

Worse yet, if we add 1, we can't fit *any* fractions! Only whole numbers can be represented above 999999999.9 with this method.

Of course, this is a dramatic oversimplification -- I don't actually know that much about how floating point numbers work, but I'm fairly certain its something similar to this. Another important note is that computers use Base 2 for floating point numbers rather than Base 10, but that's a whole other can of worms!


So, what you are seeing is Algodoo facing a similar issue, which is what results in the choppy movement!

Pretty fun, huh?

This weird glitch happens because YOU JPgamersmines150 made it happen! I looked at the pos value for one of those boxes and it is sitting at
[99998616.0, 3.9998999] which is nearly one hundred million meters outside the normal Algodoo "world" in the X axis direction. I've told probably 5 or 6 other users in just the last few days "Algodoo will glitch if you force it to do things that it was not designed to do". What you and those other guys did would be like running a lawn mower over a large pile of nuts, bolts, and rocks. Guess what will happen to the lawn mower!

Instead of finding ways to make Algodoo glitch, wouldn't it be better to work on sensible scenes that you can be proud of? Scenes like this one serve no valuable purpose and they just waste people's time.

Thanks for understanding.