Ultimaker community

~ultimaker/ultimaker/+git/CuraEngine:CURA-11696-spiral-z-hop

  1. Git
  2. lp:~ultimaker/ultimaker/+git/CuraEngine
  3. CURA-11696-spiral-z-hop
Last commit made on 2024-04-30
Get this branch:
git clone -b CURA-11696-spiral-z-hop https://git.launchpad.net/~ultimaker/ultimaker/+git/CuraEngine

Branch merges

Branch information

Name:
CURA-11696-spiral-z-hop
Repository:
lp:~ultimaker/ultimaker/+git/CuraEngine

Recent commits

89f08b2... by saumyaj3 <email address hidden>

Applied clang-format.

9fba093... by Saumya Jain <email address hidden>

Merge branch 'main' into feature_issue-15583_spiral_z-hop

fb484b8... by Saumya Jain <email address hidden>

merge 5.7

fe02797... by Jelle Spijker <email address hidden>

pin version 5.7.1

6d89383... by HellAholic <email address hidden>

[CURA-11597] fix duplicate support extrusions (#2062)

5139274... by Erwan MATHIEU <email address hidden>

Minor code cleaning and optimization

CURA-11597

eeec963... by Remco Burema <email address hidden>

Morphologic opening operation was causing floating areas.

Introduced earlier in this PR to solve some edge cases, but more trouble than it's worth it seems, at the very least when it's for support.

part of CURA-11597

6592e50... by rburema <email address hidden>

Applied clang-format.

449c209... by Remco Burema <email address hidden>

Only split up densities _completely_ when we zig-zaggify infill.

Only do the new split-up in the rare cases where stuff goes wrong for now (= gradual fills + connected fill lines). We're not adjusting the percentages for not doubling/tripling/etc over an area anymore, since that would change too much at this juncture, make it less predicatble which lines in the layer below match up, and we have more walls anyway because of the zig-zagging.

part of CURA-11597

f05f538... by Remco Burema <email address hidden>

Make line-overlap detection more conservative.

(Tried a lot of other things as well, which makes it less predictable.) Clean up experiments, bring it back to basics, be quite conservative as this is only a patch and solving the whole 'scan-segments can be too close to the connector paths' probably requires properly rewriting the zig-zag algorithm -- which is way more like a feature.

part of CURA-11597