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

Soluble interface generation issues #1386

Closed
Kolous opened this issue Nov 4, 2018 · 4 comments
Closed

Soluble interface generation issues #1386

Kolous opened this issue Nov 4, 2018 · 4 comments
Labels

Comments

@Kolous
Copy link

Kolous commented Nov 4, 2018

Version

1.41.1+win64

Operating system type + version

Windows 7 x64

Behavior

  1. Couple floating lines of the wipe tower:
    1

  2. Extra soluable layers in center hexagon.
    Should be:

  • soluable
  • solid

Instead is generated:

  • soluable
  • solid
  • soluable
  • solid

2
3
4
5

STL/Config (.ZIP) where problem occurs

a.zip

@bubnikv
Copy link
Collaborator

bubnikv commented Nov 5, 2018 via email

@Kolous
Copy link
Author

Kolous commented Nov 5, 2018

Ok, line clarified. The second issue remains ;-)

@bubnikv
Copy link
Collaborator

bubnikv commented Jan 29, 2019

I suppose the inner wall is not completely straight, there is a kink, which slic3r evaluates as in a need of support, so it puts the support there.

It is an unusually difficult job to filter out such tiny spots that seem to require a support while not missing tips of sharp objects, which do require supports.

@bubnikv
Copy link
Collaborator

bubnikv commented Feb 24, 2021

The second issue is fixed with 6bdd42b and it is a duplicate of #4570

Disabled a suspicious piece of legacy code inherited from Slic3r,
which tries to fill in spots inside support interfaces. The code was
too aggressive and it was doing more harm than good.

@bubnikv bubnikv closed this as completed Feb 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants