Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Random deretractions (E.00001) with Arachne engine #8455

Closed
2 tasks done
kolba opened this issue Jul 3, 2022 · 2 comments
Closed
2 tasks done

Random deretractions (E.00001) with Arachne engine #8455

kolba opened this issue Jul 3, 2022 · 2 comments

Comments

@kolba
Copy link

kolba commented Jul 3, 2022

Description of the bug

Some models seem to have random deretractions when sliced with arachne engine in 2.5.0-alpha2. When sliced with classic perimeter generator these micro extrusions do not happen.

retractions seem to happen correctly, but for some reason there are derectractions on the long walls

2

upon further inspection, it seems that the slicer tries to compensate extrusion with E.00001?

3

Project file & How to reproduce

  1. Open attached project in 2.5.0-alpha2
  2. Slice with 0.2mm profile for PETG/PLA with standard Prusa mini/mk3s profile
  3. Make sure that (de)retractions are shown

3dpnfilholdguidev2-2.zip

Checklist of files included above

  • Project file
  • Screenshot

Version of PrusaSlicer

2.5.0-alpha2

Operating system

Windows11

Printer model

prusa mini

@lukasmatena
Copy link
Collaborator

Thanks. It seems to be a very short segment, so short that after rounding, the x and y position is the same as the previous move, which is then interpreted as a deretraction by GCodeProcessor. We will look into it.

hejllukas added a commit that referenced this issue Jul 14, 2022
…rouping ExtrusionPaths with the same extrusion width in thick_polyline_to_extrusion_paths() that was affecting Arachne and gap fill.

The previous behavior didn't merge two ExtrusionPaths with the same extrusion width, and it also could merge two ExtrusionPaths with different widths, which was unintentional, and it could also possibly create visible artifacts in some cases.
Because simplification of ExtrusionLoop in GCode::extrude_loop is working on ExtrusionPath and not on whole ExtrusionLoop, so previous incorrect behavior was preventing simplification and removing small extrusions like in #8455.
hejllukas added a commit that referenced this issue Jul 14, 2022
… removing vertices between collinear and nearly collinear lines.
@hejllukas
Copy link
Collaborator

Thank you for noticing and reporting this issue. It was fixed with e2e1272 and b4ff9b7 in master_250, and it will be part of the next alpha.

Godrak pushed a commit that referenced this issue Jul 29, 2022
…rouping ExtrusionPaths with the same extrusion width in thick_polyline_to_extrusion_paths() that was affecting Arachne and gap fill.

The previous behavior didn't merge two ExtrusionPaths with the same extrusion width, and it also could merge two ExtrusionPaths with different widths, which was unintentional, and it could also possibly create visible artifacts in some cases.
Because simplification of ExtrusionLoop in GCode::extrude_loop is working on ExtrusionPath and not on whole ExtrusionLoop, so previous incorrect behavior was preventing simplification and removing small extrusions like in #8455.
Godrak pushed a commit that referenced this issue Jul 29, 2022
… removing vertices between collinear and nearly collinear lines.
supermerill pushed a commit to supermerill/SuperSlicer that referenced this issue Jul 30, 2022
…evented removing vertices between collinear and nearly collinear lines.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants