Has anyone done any Mill V-carve with laserweb? Besides taking a long time to generate the gcode, I find that It does lots of un-necessary Z plunge moves that does nothing. Ones example is this
This gcode snippet just goes from Zclearance (+3mm) to Z0 and back up. It does this thousands of times as seen from this screen capture. it makes Mill vcarve unusable for even very simple svg images.
There’s an issue with the old SVG import method which sometimes throws off the CAM functions; it hits v-carve the worst. We’re about to publish a new release which fixes problems with the new SVG import method.
@Todd_Fleming oh ok Thanks! I’ve “laser raster merged” this file and has come out great on the k40. Wanted to test out lw4 vcarving capability on my CNC. It’s what I do most with that machine. It would be great if lw4 can do vcarving better than freeware f-engrave.
New release available if you’re on Win-64. Try reimporting the SVG. V-carving will still choke on some files; I’d need to replace it with a better algorithm to fix those cases.
@Todd_Fleming It didn’t make much difference with this svg file. Still hundreds/thousands of extra Z moves. A much simpler SVG file came out OK though. Thanks anyway. Ill keep playing around with it.
V carve does have the setting to retract when moving, perhaps you want to find this setting and set it to zero? It’s designed to prevent you hitting stuff as you move.
