ArcWelder ignores travel paths?

[CyberFlexie]

Prusaslicer has this option called "Avoid crossing perimeters". When checked the travel paths stay inside the object. But after uploading gcode to octopi and having it processed by the ArcWelder plugin, travel moves are back out of the object.

gcode files.zip

I am using Arc Welder v1.1.0rc2 These are the files I am printing: https://www.thingiverse.com/thing:4791610

[FormerLurker]

Sorry it's taken me so long to respond! I had to change gears the last few months, but am back at it.

I JUST implemented this improvement! It's been requested for a while, mostly for plotters and CNC machines, but I just recently became aware that the 'Avoid crossing perimeters' setting (and wipe, and a few others) could generate travel moves that could be encoded. The perimeter travels seem to be lower in resolution compared to extrusions, so not as much will be converted, but I was still surprised how many moves were encoded!

Anyway, the devel branch contains the new code as well as some patches, bug fixes, and other important new features. I've been working on this for a long time trying to clear up issues with various firmwares, interpolation algorithms, and to improve general compatibility. Hopefully someday soon I'll be satisfied to push a stable release. Any testing you could do would be very welcome!

FYI, there are now separate statistics recorded if any travel moves are encoded:

The default setting for Allow Travel Arcs is True:

so you shouldn't have to change anything. I have NOT implemented settings upgrades, but the only default setting that changed was the Maximum Arc Radius, which you should set to 9999mm for the time being (it was set to 1KM) due to an extremely subtle bug I found in Marlin's arc interpolation algorithm. It's off by enough on arcs with a large radius to produce visible artifacts. Also, some firmware doesn't like large gcode commands, and reducing that setting helps.

Let me know if you have any questions!