search

Ultimaker / Cura

3D printer / slicing GUI built on top of the Uranium framework
GNU Lesser General Public License v3.0
6.08k stars 2.06k forks source link

[4.4] Object not printed if "Print as Support" selected with Tree Supports enabled #6819

Closed Silver-Streak closed 4 years ago

Silver-Streak commented 4 years ago

Application version 4.4

Platform Windows 10

Printer Anycubic i3 Mega

Reproduction steps

  1. Loaded this STL https://www.thingiverse.com/thing:1475453
  2. Selected Tree Supports
  3. Tried adding a square box to add more support to the knife area.
  4. Clicked the box model.
  5. Clicked Per Model Settings.
  6. Selected Print as Support

Screenshot(s)

Square box model from Tinkercad, added to print area, then per model setting set to "Print as Support" image

What it looks like with Tree Supports disabled: image

What it looks like with Tree Supports enabled: image

What it looks like with Normal Supports enabled: image

Actual results Only the first layer of the support is printed, then it is ignored.

Expected results The custom support to be printed along with the Tree Support. I had used this a ton of times before in the past (4.2 I believe) with no issue.

Project file Project file:

AI3M_Pyramid_head_V1.zip

Log file cura.log

Ghostkeeper commented 4 years ago

Yup, this reproduces.

The problem seems to be that the Tree Support Wall Line Count setting is not being applied to these shapes. The reason for that is that this is only applied when drawing the circular branches of the trees. These support areas are generated separately from the model outline, so they are not generated with that circle routine, and so they don't get the outline.

For now I have a workaround for you:

As a fix, I think we should merge the Support Wall Line Count setting with the Tree Support Wall Line Count.

Silver-Streak commented 4 years ago

Just wanting to chime in that your workaround fixes the issue for me (although it seems like Support X/Y distance acts odd bit odd with that enabled, I didn't have enough time to test more to see the specifics or if it was just me overanalyzing).

Glad to hear I'm not crazy, and thanks for looking into this.

Ghostkeeper commented 4 years ago

Fixed this for the next release.