See the difference between my unoptimised & optimised vector objects/paths? Saved approximately 8.1m of travel time.
I manually adjusted the original files to organise the cut order to minimise all the ridiculous zigzag moves.
Bottom most path/object in the layer cuts first, top most cuts last.
What’s generating all the zigzag?
There are approaches that can generate reasonable results for many (not all) cases. The easiest is a greedy algorithm that jscut and lw4’s mill cam use.
The greedy code lives here: https://github.com/LaserWeb/LaserWeb4/blob/81b8abaa2fdc7ca9fcddeae6e0a88329f58b1920/src/lib/cam.js#L73
It is always fascinating to me to see how various CAM programs order the cutting. I’m sure there are many ways to skin this cat because there are so many variables.
For this cut I did Parallel scanlines first then what Fusion calls a Pencil line to define the outline. The Pencil line does some odd jumping around for no apparent reason. This is TinyG and Chilipeppr.
I would really like to see “Inside” first… where all objects inside another object are cut first this really helps with the drop out pieces…
@Ariel_Yahni_UniKpty The original zigzags were caused by bad object “ordering” setup in AI. I reordered the objects to be based on a path that seemed to be “closer” visibly to me. So I moved some objects up, some objects down in the list.
Just thought I’d share to let people know that some manual optimisation for the time being could assist in improving timeframes for cut jobs. Managed to improve my cut time significantly by adjusting the object order.
@Alex_Krause allready it’s possible if you ordered as @Yuusuf_Sallahuddin_Y said. But yes have it Donde automatically would be best
