Algodoo

I THINK IM ASENDING

for what reason?

Seems to me that you are crediting me for a scene that doesn't work correctly. On my PC, I'm getting many old blocks that aren't dying as expected. Looks like the script can't keep up at 1200 Hz.

it could be because i am using algodoo 2.1.0

things are working fine for me.

The reason it works on your PC may be:
  1. You are not using the latest version of Algodoo.
  2. The scene that you are running on your PC is not the same as the one in Algobox.
  3. Your PC is able to process the scene faster than my PC.
The scene that I just downloaded from Algobox doesn't make sense. In the cutting wheel onCollide event you have:
  sim.tick > _tick + 2 && e.other.materialName == "stone" ? {...
yet you are trying to cut wood.
The custom code in the wood is the same as in the cutting wheel. There is no need for any custom code in the wood.
Upon checking the scene at 120 Hz, I see it works a expected so I'm thinking #3 above.
I am able to run Milling Cutter at 1200 Hz, so I'm confused why your scene won't run much faster than 120 Hz for me.

I found a way to fix the issue of the scene making multiple living copies of the board on my PC:
  otherCollideSet := e.other.collideSet;
  e.other.collideSet = 0;
  Scene.addPolygon({
    ...
  ­  collideSet := otherCollideSet;
    ...
  e.other.tim­eToLive = 0.0
was:
  Scene.addPolygon({
    ...
­    collideSet := e.other.collideSet;
    ...
  e.other.­timeToLive = 0.0

It seems that the old and new poly were colliding even though the old poly is deleted in the same onCollide event that the new poly is created in.
I made a jointer in order to troubleshoot the issue an added it as a response scene. Feel free to use any or all of the scene in your design.