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

Skirt Problem when basic shape consists of more than one part #181

Closed
powtac opened this issue Jan 29, 2012 · 7 comments
Closed

Skirt Problem when basic shape consists of more than one part #181

powtac opened this issue Jan 29, 2012 · 7 comments

Comments

@powtac
Copy link

powtac commented Jan 29, 2012

I do have a model which consists of two shapes in the very first layer. Slic3r throws an error when starting to slice this model. But when I set the number of Skirt Loops to 0 it works.

@alranel
Copy link
Member

alranel commented Jan 29, 2012

Can we know what error is it? or is it a secret?

:-)

@triffid
Copy link
Contributor

triffid commented Jan 29, 2012

http://catb.org/esr/faqs/smart-questions.html#intro

I print plates of multiple parts with skirt all the time

@powtac
Copy link
Author

powtac commented Jan 29, 2012

Screenshot of error
The errorous file

@powtac
Copy link
Author

powtac commented Jan 29, 2012

@triffid It's one single part but it is divided at the very first layers...

@powtac powtac closed this as completed Jan 29, 2012
@powtac powtac reopened this Jan 29, 2012
@triffid
Copy link
Contributor

triffid commented Jan 29, 2012

that STL is extremely non-manifold. See http://www.shapeways.com/tutorials/fixing-non-manifold-models for a few types of non-manifoldness

slic3r is only expected to work correctly with manifold STLs

http://cloud.netfabb.com might be able to sort it out

@powtac
Copy link
Author

powtac commented Jan 29, 2012

Thanks for the answer @triffid! I will check this out.

@powtac powtac closed this as completed Jan 29, 2012
@alranel
Copy link
Member

alranel commented Jan 29, 2012

@triffid's answer is definitely correct, however Slic3r shouldn't be exposing that internal error and it should provide the usual user-friendly one. I'll leave this issue closed and I'll link it to #180 which already covers the issue.

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