1.2.9 Spiral vase unexpected extrusion in place of travel move

[motorb]

Silc3r version 1.2.9
Windows 7, repetier host 1.6.2

Using spiral vase to make a part with a bottom layer, the travel move between the last infill track and the start of the spiral vase is an extruded move. This leaves a visible track of extrudate across the part. Issue repeats with alternate layer heights, part dimensions etc.

Screenshot included highlighting the offending command in repetier preview pane and gcode editor
spiral vase issue zip.gz

thanks

[lordofhyphens]

@motorb
Please read and edit your issue to provide the requested information:
https://github.com/alexrj/Slic3r/blob/master/.github/CONTRIBUTING.md

I can't tell what's going on with what you provided.

Then try again with https://bintray.com/lordofhyphens/Slic3r/slic3r_dev/1.3.0-dev-a193297#files to ensure that it's still happening with current master (you should be using current master anyway).

[motorb]

Apologies, for some reason github isn't accepting the .zip file with the stl and configuration files.

[motorb]

OK, so if I rename my zip file to gz it will upload. great. I'll edit the issue now.

[lordofhyphens]

Don't forget to add a screenshot from Slic3r's plater too and check with 1.3.0-dev (linked above).

[lordofhyphens]

That white line in your screenshot looks like a travel move to me, so I really don't know what you are seeing that is an issue.

[motorb]

It's an extrusion move, highlighted as I've highlighted the Gcode line in the pane on the right. Further confirmed when I printed the part....

[alranel]

Yeah please, test with 1.3.0-dev.

[alranel]

@motorb, can you confirm this is fixed using a fresh build? You can download it at http://dl.slic3r.org/dev/

[ruevs]

Version 1.3.1-dev
Build commit: d17659b

Occasionally moves that should be travel moves are generated with extrusions.
Models similar to the attached one with "three spokes" show this on layers other than the first one as well.

Slic3rBug.zip
config.zip

This is not in spiral vase mode, but since it seems related I decided to add it here.

[ruevs]

By the way this is a regression of sorts. For example Slic3r-master.2018.04.26.1669.8a93fbb.32bit.zip (which I had laying around) does NOT have this problem when slicing the exact same object running on the same machine (so the exact same configuration as above).

Slic3r-master.2018.04.26.1669.8a93fbb.32bit.gcode.zip