Lazer cutter should be abled to cut an object more than once

[pixartist]

It's pretty irritating, that a reflected laser, passing through an object a second time, won't cut it this time. It will only cut the first time it passes through, no matter how often it's being reflected through the object

[Cyanide Cloud]

I agree 100%

[Torn]

I agree it's annoying, but I'm fairly sure it's because if a laser could cut an object multiple times, then an object falling through a laser would generate an incredible amount of lag as each individual frame was sliced... try dropping an object through several flickering lasers.

[Conundrumer]

The laser cutter USED to be able to cut through an object more than once, but after I made a simple demonstration with laser cutting and reflection/refraction, it quickly got incredibly laggy.

[gradyfitz]

The laser cutter USED to be able to cut through an object more than once, but after I made a simple demonstration with laser cutting and reflection/refraction, it quickly got incredibly laggy.

You still can, by stacking two lasers, but, it will quickly get incredibly laggy .

Paradigm worked this out (I think) .

[pixartist]

does the fact that something CAN get laggy when being abused justify removing said feature ?

[gradyfitz]

does the fact that something CAN get laggy when being abused justify removing said feature ?

Try what I said, it works, you'll see how laggy it gets quickly (it may turn 1 object into one thousand, and, if you used a few hundred objects, that would be more than phun can handle (in my experience, phun doesn't like using more than 1.8GB of RAM, which is worth about 64k geometries)). I think it's quite logical to replace a feature (which I don't think ever actually existed, I think this was just Paradigm's work around, but, I may have remembered wrongly ), that would possibly cause any phun running computer to have phun crash (some sort of programming limitation of RAM causes it to crash), with one that still works, but only when the laser loses contact with the object.

It can be fun to put negative materialVelocity on an object, then place a box on it, and run it through two cutter lasers stacked on top of each other, but, it's not really practical .

[Chronos]

maybe algoryx can find a work-around? this seems like it would be useful