Using Luban 4.0.3. When importing DXFs (single layer, single line type) to cut as vectors, the pathfinding for the laser pattern is very strange - it almost appears as if Luban tries to MAXIMISE travel times, never cutting lines close to each other, but almost always proceeding with a line far away from the last cut. Circular paths are separate into singular strokes leading to the head spending a lot of time moving around instead of cutting path by path.
If this was intentional so that the laser assembly would get longer “off” times to cool between line cuts, I would somewhat understand, however that doesn’t seem to be the case for other cutting and engraving modes.
It looks almost like a bad implementation; wonder if it’s possible to get back the “path optimizer” option we had in earlier Luban versions?
Surely, there must be some way for the slicer to determine which line to tackle next, now it feels like random (likely based on vector object ID’s because order it doesn’t change on each slice run), surely proximity wouldn’t be that hard to implement?